Customer Feedback
We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
Now we have the same solution but instead of creating a new index just for reading, we create a queue for the write operation. It is the service queue system. We were running service queue on USEA05 for most of the Inte and Prep indexes but there were a lot of complaints from customers about latency when indexing data. If we create a failover index and pause indexing operations when the cluster is down, we may experience this same complaint.
In additional, it's really hard to automatically determine when there's a service outage. Sometime a cluster only have problem with several indexes and with several kind of requests.
From my point of view, we should try to improve the service queue to make it work as expected instead of create a new failover index.