we would like to maintain an index of documents in memory
we don't want to keep the index persisted in a storage.
Practically, our index works as temporary index in memory where we add new
documents and delete the obsoleted ones.
Under these circumstances, if a node fails, the indexed data contained in it
will be available on the cluster? Meaning, is the in-memory index replicated
over the cluster?
we would like to maintain an index of documents in memory
we don't want to keep the index persisted in a storage.
Practically, our index works as temporary index in memory where we add new
documents and delete the obsoleted ones.
Under these circumstances, if a node fails, the indexed data contained in
it will be available on the cluster? Meaning, is the in-memory index
replicated over the cluster?
Well, if you don't need persistence then either Hazelcast or ElasticSearch
will work fine as is. If you want to query by something other than key, then
you would want to include ElasticSearch.
Using ElasticSearch, your data is replicated (if you configure your index
such) whether you use a memory store or file-based storage.
we would like to maintain an index of documents in memory
we don't want to keep the index persisted in a storage.
Practically, our index works as temporary index in memory where we add new
documents and delete the obsoleted ones.
Under these circumstances, if a node fails, the indexed data contained in
it will be available on the cluster? Meaning, is the in-memory index
replicated over the cluster?
By "front-ending" he was referring to the option of using Hazelcast as your
memcache layer, and having it use ES for persistence. Hazelcast has a simple
MapStore interface you can implement to read/write objects from ES. Since
you don't need persistence, there is little need for that set up.
Yes, an in memory index is replicated across the cluster, and if one node
fails, then you have a replica. Note, the internal transaction log used in
elasticsearch is always file based one. I highly suggest just using the file
system based one, its simpler, and you can use the mmapfs one for better
perf. why do you want it to be in memory one?
we would like to maintain an index of documents in memory
we don't want to keep the index persisted in a storage.
Practically, our index works as temporary index in memory where we add new
documents and delete the obsoleted ones.
Under these circumstances, if a node fails, the indexed data contained in
it will be available on the cluster? Meaning, is the in-memory index
replicated over the cluster?
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.