David Before I started migration I checked many records counter - 1000, 2000, 5000, 100 000, etc. Im my configuration 200 000 is optimal value. Problem with timeout is not directly conected with quantity of records because now I stoped all load (indexing) processes and I can't update mapping for new indexes. Cluster now is during shards allocation process after restart. I'm trying create new one and update appropriate mapping for it. I do it by pure curl request and by perl Search::Elasticsearch with all option for cxn (NetCurl, LWP, etc.) but cluster still answare that after 30s with exception that update mapping isn't possible. I think that this problem is conected with some parameters for buffers, queues (?), but I don't know what.
Regards -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/dbaa9cd3-65fa-4117-8c3b-bfd6096611f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
