Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CCR] Remote cluster connection status #37799

Closed
sebelga opened this issue Jan 24, 2019 · 1 comment · Fixed by #43379

Comments

@sebelga
Copy link
Contributor

commented Jan 24, 2019

Currently, the _remote/info does not update the "connected" property when the seed node change and point to a wrong host: port.

Steps to reproduce:

  1. Create a remote cluster ("new-york") with a correct seed (localhost:9400)
  2. Create an auto-follow pattern and use that cluster
  3. Edit the remote cluster "new-york" and change the seed with a port that does not point to any cluster ---> localhost:9500
    ---> In the Elasticsearch terminal outputs an error "failed org.elasticsearch.transport.ConnectTransportException: [][127.0.0.1:9500] connect_exception"
  4. But the /_remote/info still shows the cluster as "connected"
{
  "new-york": {
      "seeds": [
          "localhost:9500"
      ],
      "connected": true,
      "num_nodes_connected": 1,
      "max_connections_per_cluster": 3,
      "initial_connect_timeout": "30s",
      "skip_unavailable": false
  }
}
  1. I edit the auto-follow pattern and I am allowed to save (even though the remote cluster is not connected)

Now if we repeat the steps and instead of creating a connected cluster we add a disconnected remote cluster first

  1. Create a remote cluster ("paris") with a wrong seed (localhost:9500) ---> Shows as "disconnected" in /_remote/info
  2. Create an auto-follow pattern and use that cluster
  3. Receive a 400 error: "[connect_transport_exception] [][127.0.0.1:9500] connect_exception"
  4. Edit the remote cluster ---> localhost:9400
  5. It does shows as "connected" (/_remote/info updated the status)
  6. I edit the remote cluster ---> localhost:9500
  7. It still shows as "connected" (/_remote/info did not update the status)
  8. I am able to create an auto-follow pattern with that not connected remote cluster.
@elasticmachine

This comment has been minimized.

Copy link
Collaborator

commented Jan 24, 2019

@tlrx tlrx added the >bug label Jun 19, 2019
@tlrx tlrx closed this in #43379 Jun 20, 2019
tlrx added a commit that referenced this issue Jun 20, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes #37799
tlrx added a commit that referenced this issue Jun 20, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes #37799
tlrx added a commit that referenced this issue Jun 20, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes #37799
tlrx added a commit that referenced this issue Jun 20, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes #37799
tlrx added a commit that referenced this issue Jun 20, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes #37799
tlrx added a commit that referenced this issue Jun 20, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes #37799
jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Jun 27, 2019
The RemoteClusterService should close the current 
RemoteClusterConnection and should build it again if 
the seeds are changed, similarly to what is done when 
the ping interval or the compression settings are changed.

Closes elastic#37799
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.