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

Jdbc importer not working to transfer to cloud elastic #883

Open
pkyt opened this issue Sep 2, 2016 · 1 comment
Open

Jdbc importer not working to transfer to cloud elastic #883

pkyt opened this issue Sep 2, 2016 · 1 comment

Comments

@pkyt
Copy link

pkyt commented Sep 2, 2016

We are experiencing an issue with communication between our program and elastic-search cloud server.

We are unable to establish connection to cloud system. This is due to a failed request of getting a node info, which disconnecting our program from server. (Exception #1). This results in an error that causes our program to fail. This error is due to availability of nodes. (Exception #2)

Exception #1: NodeDisconnectedException

[INFO][org.elasticsearch.org.xbib.elasticsearch.helper.client.TransportClient][pool-3-thread-1] [importer] failed to get node info for {#transport#-1}{50.16.191.15}{49a470021ebdb61e456ccae825b9adcd.us-east-1.aws.found.io/50.16.191.15:9343}, disconnecting...
org.elasticsearch.transport.NodeDisconnectedException: [][49a470021ebdb61e456ccae825b9adcd.us-east-1.aws.found.io/50.16.191.15:9343][cluster:monitor/nodes/liveness] disconnected

Exception #2: NoNodeAvailableException

[ERROR][importer.jdbc ][pool-3-thread-1] error while processing request: no cluster nodes available, check settings {autodiscover=false, client.transport.ignore_cluster_name=false, client.transport.nodes_sampler_interval=5s, client.transport.ping_timeout=5s, cluster.name=49a470021ebdb61e456ccae825b9adcd, flush_interval=5s, host.0=49a470021ebdb61e456ccae825b9adcd.us-east-1.aws.found.io, max_actions_per_request=10000, max_concurrent_requests=16, max_volume_per_request=10mb, name=importer, port=9343, sniff=false}
org.elasticsearch.client.transport.NoNodeAvailableException: no cluster nodes available, check settings {autodiscover=false, client.transport.ignore_cluster_name=false, client.transport.nodes_sampler_interval=5s, client.transport.ping_timeout=5s, cluster.name=49a470021ebdb61e456ccae825b9adcd, flush_interval=5s, host.0=49a470021ebdb61e456ccae825b9adcd.us-east-1.aws.found.io, max_actions_per_request=10000, max_concurrent_requests=16, max_volume_per_request=10mb, name=importer, port=9343, sniff=false}

We are wondering how to fix the problem, how to establish a valid connection to the cloud server through using jdbc importer?

@jprante
Copy link
Owner

jprante commented Sep 2, 2016

Did it work before? Or is it the first try?

If you get "failed to get node info", you are using probably Elasticsearch versions that do not match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants