# Multi-datacenter and issue 2448 **URL:** \ **Category:** Elasticsearch\ **Created:** [January 6, 2014, 2:43pm UTC](https://discuss.elastic.co/t/multi-datacenter-and-issue-2448/15115 "2014-01-06T14:43:34Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![bitsofinfo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitsofinfo/32/459_2.png) [@bitsofinfo](https://discuss.elastic.co/u/bitsofinfo)\ **Post date:** [January 6, 2014, 2:43pm UTC](https://discuss.elastic.co/t/multi-datacenter-and-issue-2448/15115/1 "2014-01-06T14:43:34Z")
Hi - we are trying to get elastic search to work in a multi-datacenter deployment, and our desired setup is pretty much what the OP describes (and we get the same split brain behavior) in this outstanding issue at > Whats the roadmap for resolving this? My use case is w/ logstash, would prefer admins only have to go to one place to see log data across all of our DC's rather than having to have separate indices/cluster for each DC's logstash data due to this slit brain issue. thanks -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0654be12-c090-4457-9ca1-a9d9babce65c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0654be12-c090-4457-9ca1-a9d9babce65c%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:58am UTC](https://discuss.elastic.co/t/multi-datacenter-and-issue-2448/15115/2 "2017-07-06T01:58:13Z")