Hi,
We have a cluster set up already for indexing customer documents (bigger
documents, medium traffic). We want to add event logging (small documents,
lots of traffic).
*Should we do this on a new cluster?*
- When do you typically create a separate cluster vs. add indexes to a
cluster?
- Is it straightforward to move indices to a new cluster at a later date?
Reasons I can think of for using the same cluster:
- Fewer servers to administer
- ES is already well equipped to handle multiple indices with various
mappings
- Simple searching across event & document indices, if needed
- If we were planning to add new servers for an events cluster, why not
have them in the same cluster for more redundancy
Reasons I can think of for a new, separate, cluster:
- The cluster can be tuned to the relevant performance needs
- Don't have to worry about the flood of events using up all the disk
space
- Separation of responsibility / "single responsibility" design pattern
- If one cluster goes down / hits performance problems, the other can
continue along fine
I couldn't see any blog posts or documentation around best practice for
this, so your insight would be most welcome!
Cheers,
Nick
--
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/ebb7afb0-9efb-45b1-b6e7-dba67bb52d1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
