-
Notifications
You must be signed in to change notification settings - Fork 77
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
no_node_available_exception - Version 2.3.1 (push indices from one cluster to another) #101
Comments
same issue still existent in 2.3.3 |
same issue in 2.3.0, in debug model , i found the error below: |
Thanks. There are limitations in Elasticsearch, I can only think of fixing this by disabling Netty dead lock checking. Will be in next release #110 |
Hi,
I've tried to push indices from one cluster to another and got the following error.
I already checked my firewall settings and all firewalls deactivated and I checkt the transport ports and they are also available. The file export is working fine.
Could you please have a look into that issue?
Request
http://10.00.00.00:9200/products/_push?&host=10.00.00.13&port=9300&cluster=TEST
Response
Configuration
CLUSTER 1
CLUSTER 2
Elastic Version 2.3.1
Here is the log file:
The text was updated successfully, but these errors were encountered: