If you use index.store.type set to memory (which has some problems in the
implementation that I have not tracked yet), then using local gateway (the
default) will not work. Once you create an index with settings, they are set
to those settings, so if you kill elasticsearch and start it again (with
local gateway), you will get failures. If you want a clean elasticsearch
instance, delete teh data dir.
I suggest you use the file system based one, and if you want extra guice,
use the mmapfs option.
On Wed, Aug 31, 2011 at 2:57 PM, Ridvan Gyundogan email@example.com:
I forgot to mention that I restart ES by first kill'ing it. Probably
not the best way?
On Aug 31, 2:33 pm, Ridvan Gyundogan ridva...@gmail.com wrote:
Hm now I have this exception even after removing the
"index.store.type: memory" setting.
This is how I did it:
- load 600k small documents - worked fine at the end.
- Add filter.cache(true) to each filter. - worked fine
- add index.store.type: memory - exceptions in the elasticsearch log
- remove index.store.type: memory - still exceptions in the
elasticsearch log file. The ES doesn't start anymore.
On Aug 31, 2:22 pm, Ridvan Gyundogan ridva...@gmail.com wrote:
I run on a single local machine.
This is the elasticsearch.yml:
When I start I get the followin exception, probably I miss something
in my configuration?
[2011-08-31 14:18:03,212][WARN ][indices.cluster ] [Jaren]
[giftsplusindex] failed to start shard
[giftsplusindex] shard allocated for local recovery (post api),
should exists, but doesn't
Without the index.store.type: memory setting the ES 17.4 works fine.