Re: Slow Commands with 1.2.4 to 1.4.2 Upgrade

[pskieu]

Lowered to 16g and verified with top--same behavior. I've also tried 1.3 
with the same results.

1.2 is the latest version that's working properly for me.

On Saturday, January 17, 2015 at 5:02:03 AM UTC-8, Arie wrote:
>
> With 32GB of memory this should be around 16GB (50%), and check if this 
> actually is the case with top for example.
>
>
> On Friday, January 16, 2015 at 6:52:02 PM UTC+1, psk...@gmail.com wrote:
>>
>> My ES_HEAP_SIZE is already set to 24g per node
>>
>> On Friday, January 16, 2015 at 4:25:00 AM UTC-8, Arie wrote:
>>>
>>> Check your memory usage on ES. In my case I had to specifically put 
>>> ES_HEAP_SIZE in /etc/init.d/elasticsearch
>>> to get it working the right way.
>>>
>>> On Monday, January 5, 2015 at 7:45:12 PM UTC+1, psk...@gmail.com wrote:

 It takes upwards an average of 10 to 30 seconds. This is a test 
 instance, so there's no additional load other than what I'm doing.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/65e8ea85-f9fb-4315-a90c-7f14c17385b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slow Commands with 1.2.4 to 1.4.2 Upgrade

[pskieu]

My ES_HEAP_SIZE is already set to 24g per node

On Friday, January 16, 2015 at 4:25:00 AM UTC-8, Arie wrote:
>
> Check your memory usage on ES. In my case I had to specifically put 
> ES_HEAP_SIZE in /etc/init.d/elasticsearch
> to get it working the right way.
>
> On Monday, January 5, 2015 at 7:45:12 PM UTC+1, psk...@gmail.com wrote:
>>
>> It takes upwards an average of 10 to 30 seconds. This is a test instance, 
>> so there's no additional load other than what I'm doing.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/c163ad96-23df-435f-a2a0-ae82687039a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slow Commands with 1.2.4 to 1.4.2 Upgrade

[pskieu]

Just added 2 more nodes with the same specs, and still seeing the same 
slowness. These commands no longer return anything, because it's taking too 
long to return.


On Tuesday, December 30, 2014 at 3:54:34 PM UTC-8, Mark Walkom wrote:
>
> How slow?
> Is the load on your system high?
>
> On 31 December 2014 at 05:04, > wrote:
>
>> I have about 50 GB of data (1 mil docs) in a single node--8 cores with 32 
>> GB (24 GB heap). I just upgraded from 1.2.4 to 1.4.2, and I noticed that a 
>> few commands take a long time to return, and marvel doesn't work as well as 
>> it used to.
>>
>> Some of the commands that are slow for me are _cat/indices and _nodes.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/9e3f7c4b-0705-4063-a591-8c5359ff8254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slow Commands with 1.2.4 to 1.4.2 Upgrade

[pskieu]

It takes upwards an average of 10 to 30 seconds. This is a test instance, so 
there's no additional load other than what I'm doing.

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/1286f276-e20c-4ff2-acc0-90a5a3d57b0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Slow Commands with 1.2.4 to 1.4.2 Upgrade

[pskieu]

I have about 50 GB of data (1 mil docs) in a single node--8 cores with 32 
GB (24 GB heap). I just upgraded from 1.2.4 to 1.4.2, and I noticed that a 
few commands take a long time to return, and marvel doesn't work as well as 
it used to.

Some of the commands that are slow for me are _cat/indices and _nodes.

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ES trying to connect to itself

[pskieu]

I'm running a docker container with ES in it. The cluster works fine but I 
keep getting warning messages about it trying to connect to itself.

[2014-06-30 18:26:21,105][WARN ][cluster.service  ] [ES01] failed 
to reconnect to node 
[ES01][miTCM9-BQwmhlL4mk7EX1w][fb06cbd6bd18][inet[es-host1/137.78.110.131:9300]]
org.elasticsearch.transport.ConnectTransportException: 
[ES01][inet[es-host1/137.78.110.131:9300]] connect_timeout[30s]
at 
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:727)
at 
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:656)
at 
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:624)
at 
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:146)
at 
org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:518)
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:744)
Caused by: java.net.ConnectException: Connection refused: 
es-host1/137.78.110.131:9300
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
at 
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)
at 
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
at 
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
at 
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)
at 
org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
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

Settings are:

network.bind_host to default
network.publish_host: 137.78.110.131

I'm not setting network.host to the IP since there's some NAT happening.

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/4f2444b9-e810-4d62-8b0c-070717ec7495%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.