Depends on what your definition of "ok for production" is. For me, that
means sharding and replicas for appropriate failover when a node goes down.
I guess you're okay if you run a single server, have a backup / restore
process in place and searching be unavailable doesn't impact your
application heavily.
You could also ask yourself: is it ok for production to have one single database?
If for your usecase the answer is yes, then you could use elasticsearch as well with only one node.
As long as you can read again your data from the source and reindex....
Depends on what your definition of "ok for production" is. For me, that means sharding and replicas for appropriate failover when a node goes down. I guess you're okay if you run a single server, have a backup / restore process in place and searching be unavailable doesn't impact your application heavily.
On Fri, Dec 26, 2014 at 8:54 PM, cordyceps agus.santoso@gmail.com wrote:
Hi, i'm wondering if running ES in non-cluster is ok for production, i have only < 1 million docs
Please give me advice thanks.
Can't he just use two nodes as a bare minimum setup with number of replica
as one so that the search is available even if one node goes down. He can
add another node as soon as he observe any one node failure to avoid any
data loss.
...my 2 cents.
Gaurav
On Dec 27, 2014 12:16 PM, "David Pilato" david@pilato.fr wrote:
You could also ask yourself: is it ok for production to have one single
database?
If for your usecase the answer is yes, then you could use elasticsearch as
well with only one node.
As long as you can read again your data from the source and reindex....
Depends on what your definition of "ok for production" is. For me, that
means sharding and replicas for appropriate failover when a node goes down.
I guess you're okay if you run a single server, have a backup / restore
process in place and searching be unavailable doesn't impact your
application heavily.
Can't he just use two nodes as a bare minimum setup with number of replica as one so that the search is available even if one node goes down. He can add another node as soon as he observe any one node failure to avoid any data loss.
...my 2 cents.
Gaurav
On Dec 27, 2014 12:16 PM, "David Pilato" david@pilato.fr wrote:
You could also ask yourself: is it ok for production to have one single database?
If for your usecase the answer is yes, then you could use elasticsearch as well with only one node.
As long as you can read again your data from the source and reindex....
Depends on what your definition of "ok for production" is. For me, that means sharding and replicas for appropriate failover when a node goes down. I guess you're okay if you run a single server, have a backup / restore process in place and searching be unavailable doesn't impact your application heavily.
On Fri, Dec 26, 2014 at 8:54 PM, cordyceps agus.santoso@gmail.com wrote:
Hi, i'm wondering if running ES in non-cluster is ok for production, i have only < 1 million docs
Please give me advice thanks.
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.
