Force merge request does nothing (ES 5.1.2)


#1

Hi!

Elastic 5.1.2

I have talked with @untergeek in https://github.com/elastic/curator/issues/881 because I thought that I had a problem with force merge and curator.

It seems that there is a problem in other part which is not curator, and looks like ES is doing something strange.

I'm trying to _forcemerge in our current cluster: 50 nodes, hot-warm architecture, big and small indexes, and big indexes with 42 primary shards and 1 replication.

We are testing it on small indexes first (30k documents, 30MB disk size, 5 shards), and _forcemerge does nothing. There is no output, and there is no process running behind. Nothing shown on the logs (neither on the host where the command is issued, nor in the master) It should not take more than a few seconds to merge segments for a 30MB index, right?

Can you guys help me about what can be going on?

command: curl -XPOST 'localhost:9200/wormhole_2017-02-03/_forcemerge?max_num_segments=1'

Thanks!


#2

Is it possible that if I trigger another POST request, it does not return if there are pending _forcemerge requests?


#3

It may be:

This call will block until the merge is complete. If the http connection is lost, the request will continue in the background, and any new requests will block until the previous force merge is complete.

Is it possible to see those pending forcemerge?


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.