# ECE availability zone for tiebreaker only

**URL:** <https://discuss.elastic.co/t/ece-availability-zone-for-tiebreaker-only/291332>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [December 9, 2021, 1:21pm UTC](https://discuss.elastic.co/t/ece-availability-zone-for-tiebreaker-only/291332 "2021-12-09T13:21:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zerobot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zerobot/32/48977_2.png) [@Zerobot](https://discuss.elastic.co/u/Zerobot)\
**Post date:** [December 9, 2021, 1:21pm UTC](https://discuss.elastic.co/t/ece-availability-zone-for-tiebreaker-only/291332/1 "2021-12-09T13:21:04Z")

</div>

Hello!

Due to upcoming changes in my company's DC structure we will have 2 separate "big" sites, and 1 "smaller" site, mainly for all the quorum things. It would be easiest for us to delegate quorum / tiebreaker nodes to our third site.  
I understand that ECE itself would work best if we use a total of 3 zones for example for built-in ELK clusters - no problem with that. Our smaller site would have a hard time with data.nodes of not-built-in clusters though so I'd like to limit having data.nodes in that site as much as I can.

I've been wondering - is it possible to delegate 1 of the 3 ECE zones as a smaller, tiebreaker only, zone?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 23, 2021, 1:21pm UTC](https://discuss.elastic.co/t/ece-availability-zone-for-tiebreaker-only/291332/2 "2021-12-23T13:21:37Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.