Decommission ES cluster and sidekiq nodes
This is an action item of https://gitlab.com/gitlab-com/infrastructure/issues/2877 and part of https://gitlab.com/gitlab-com/infrastructure/issues/1597
We have determined that the infrastructure costs to maintain this feature are too high now (mostly on the storage side of things), so we need to re-evaluate.
One option would be gradually enabling the feature for public projects, which will result in a better evaluation of the feature, in terms of development, operations and costs. See https://gitlab.com/gitlab-org/gitlab-ee/issues/3492 for more details.
In the meantime, we are going to decommission the following nodes:
elasticsearch-01.db.prd.gitlab.com
elasticsearch-02.db.prd.gitlab.com
elasticsearch-03.db.prd.gitlab.com
elasticsearch-04.db.prd.gitlab.com
elasticsearch-05.db.prd.gitlab.com
elasticsearch-06.db.prd.gitlab.com
elasticsearch-07.db.prd.gitlab.com
elasticsearch-08.db.prd.gitlab.com
elasticsearch-09.db.prd.gitlab.com
elasticsearch-10.db.prd.gitlab.com
elasticsearch-11.db.prd.gitlab.com
elasticsearch-12.db.prd.gitlab.com
elasticsearch-13.db.prd.gitlab.com
elasticsearch-14.db.prd.gitlab.com
elasticsearch-15.db.prd.gitlab.com
elasticsearch-16.db.prd.gitlab.com
sidekiq-elasticsearch-01.sv.prd.gitlab.com
sidekiq-elasticsearch-02.sv.prd.gitlab.com
sidekiq-elasticsearch-03.sv.prd.gitlab.com
sidekiq-elasticsearch-04.sv.prd.gitlab.com
sidekiq-elasticsearch-05.sv.prd.gitlab.com
sidekiq-elasticsearch-06.sv.prd.gitlab.com
sidekiq-elasticsearch-07.sv.prd.gitlab.com
sidekiq-elasticsearch-08.sv.prd.gitlab.comActivity
@victorcete can we include a summary about why from #2877 ?
@nick.thomas thanks for the reminder, I forgot the previous issue was confidential
mentioned in merge request gitlab-com-infrastructure!166 (merged)
Terraform plan for the sidekiq nodes:
------------------------------------------------------------------------ An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: - destroy Terraform will perform the following actions: - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch[1] - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch[2] - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch[3] - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch[4] - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch[5] - module.virtual-machines-sidekiq.aws_route53_record.sidekiq-elasticsearch[6] - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch[1] - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch[2] - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch[3] - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch[4] - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch[5] - module.virtual-machines-sidekiq.azurerm_network_interface.sidekiq-elasticsearch[6] - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch[1] - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch[2] - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch[3] - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch[4] - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch[5] - module.virtual-machines-sidekiq.azurerm_virtual_machine.sidekiq-elasticsearch[6] Plan: 0 to add, 0 to change, 21 to destroy.Terraform plan for the ES nodes:
------------------------------------------------------------------------ An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: - destroy Terraform will perform the following actions: - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[1] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[2] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[3] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[4] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[5] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[6] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[7] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[8] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[9] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[10] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[11] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[12] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[13] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[14] - module.virtual-machines-elasticsearch.aws_route53_record.elasticsearch[15] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0 - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[1] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[2] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[3] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[4] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[5] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[6] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[7] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[8] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[9] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[10] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[11] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[12] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[13] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[14] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-0[15] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1 - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[1] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[2] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[3] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[4] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[5] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[6] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[7] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[8] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[9] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[10] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[11] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[12] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[13] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[14] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-1[15] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2 - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[1] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[2] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[3] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[4] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[5] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[6] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[7] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[8] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[9] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[10] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[11] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[12] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[13] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[14] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-2[15] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3 - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[1] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[2] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[3] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[4] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[5] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[6] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[7] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[8] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[9] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[10] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[11] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[12] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[13] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[14] - module.virtual-machines-elasticsearch.azurerm_managed_disk.elasticsearch-datadisk-3[15] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[1] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[2] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[3] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[4] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[5] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[6] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[7] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[8] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[9] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[10] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[11] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[12] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[13] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[14] - module.virtual-machines-elasticsearch.azurerm_network_interface.elasticsearch[15] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[1] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[2] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[3] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[4] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[5] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[6] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[7] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[8] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[9] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[10] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[11] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[12] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[13] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[14] - module.virtual-machines-elasticsearch.azurerm_virtual_machine.elasticsearch[15] Plan: 0 to add, 0 to change, 112 to destroy.mentioned in issue #2600 (closed)
Please register or sign in to reply