I have a 40-shard index, currently its size is 39 GB. There's only one type
in the index, and one of the fields is of nested type that holds complex
documents.
When I start to populate the index further, after adding about 3000
documents server becomes unavailable for some time. Then it becomes
available again, but one of the shards is left unallocated.
After I restart ES, all shards load just fine, but the story repeats itself.
this is very hard to tell without further debugging/information. Can you
check your logfiles, if there are any exceptions popping up? Can you check
the logfile of your master node, if node joins/leaves or even master
elections happen? Also you should add monitoring to your infrastructure
(like Marvel) in order to find out more about your running system...
I have a 40-shard index, currently its size is 39 GB. There's only one
type in the index, and one of the fields is of nested type that holds
complex documents.
When I start to populate the index further, after adding about 3000
documents server becomes unavailable for some time. Then it becomes
available again, but one of the shards is left unallocated.
After I restart ES, all shards load just fine, but the story repeats
itself.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.