Databases
StackOverflow2013
Postsdbo
POES timeout after upgrade on a single cluster
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POES timeout after upgrade on a single cluster
    primarykey
    data
    text
    <p>So I've had ES version 0.19.4 and wanted to upgrade to 0.20.6 as my clusters didn't have any information that I couldn't easily recover I deleted the indices's and completely cleared down my es data folder, removed the 0.19.4 version and as I start up I somehow cannot use my original cluster name, the ES starts fine with any other cluster name but not with "aggr" the one I used before, as I wanted to make sure nothing else is using old Elastic Search I even rebooted the computer (don't have any on startup software on this test system) so essentially everything is clear but I can't use the old cluster name... The stack:</p> <pre><code>[2013-04-03 13:37:59,902][WARN ][discovery.zen.ping.multicast] [Orchid] failed to connect to requesting node [Kaur, Benazir][by0TZFhXR1mUxBd9T6bi9w][inet[/xxx.xxx.xx.xxx.xxxx]]{client=true, data=false} org.elasticsearch.transport.ConnectTransportException: [Kaur, Benazir][inet[/xxx.xxx.xx.xxx.xxxx]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:671) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:610) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:580) at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:127) at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver$1.run(MulticastZenPing.java:536) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.net.ConnectException: connection timed out at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:136) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:82) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:41) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more </code></pre> <p>All of the elasticsearch.yml settings are commented out apart from:</p> <pre><code>cluster.name: aggr </code></pre> <p>Also when Elastic Search starts on my testing machine which is connected on internal network I see in the logs:</p> <pre><code>[2013-04-03 13:37:27,281][INFO ][node ] [Orchid] {0.20.6}[4484]: initializing ... [2013-04-03 13:37:27,287][INFO ][plugins ] [Orchid] loaded [], sites [] [2013-04-03 13:37:29,633][INFO ][node ] [Orchid] {0.20.6}[4484]: initialized [2013-04-03 13:37:29,633][INFO ][node ] [Orchid] {0.20.6}[4484]: starting ... [2013-04-03 13:37:29,710][INFO ][transport ] [Orchid] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/**My internal IP**:9300]} [2013-04-03 13:37:32,739][INFO ][cluster.service ] [Orchid] new_master [Orchid][MzSRtsCfR2W3S_QyG_QLQg][inet[/**My internal IP**:9300]], reason: zen-disco-join (elected_as_master) [2013-04-03 13:37:32,818][INFO ][discovery ] [Orchid] aggr/MzSRtsCfR2W3S_QyG_QLQg [2013-04-03 13:37:32,857][INFO ][http ] [Orchid] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/**My internal IP**:9200]} [2013-04-03 13:37:32,857][INFO ][node ] [Orchid] {0.20.6}[4484]: started [2013-04-03 13:37:32,945][INFO ][gateway ] [Orchid] recovered [0] indices into cluster_state </code></pre> <p>And in the error log right afterwards I see the log for my server machine which is connected with and external IP:</p> <pre><code>[2013-04-03 13:37:59,902][WARN ][discovery.zen.ping.multicast] [Orchid] failed to connect to requesting node [Kaur, Benazir][by0TZFhXR1mUxBd9T6bi9w][inet[/**My external IP**:9301]]{client=true, data=false} org.elasticsearch.transport.ConnectTransportException: [Kaur, Benazir][inet[/**My external IP**:9301]] connect_timeout[30s] </code></pre> <p>How can this be? How can my system start on my internal machine and throw an error linking to my external machine? Again the only setting set in the ES.yml is the cluster name..</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMantas
    1. USMantas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload