Thank you for sharing Venkat. One question: the article mentioned “SSD and Flash storage” storage several times. Does this mean that Couchbase 5.0 will be more tolerate of the non-persistent local SSD drives in Azure and EC2?
Both cloud platforms offer extremely fast (100,000 IOPS) local SSD storage, but the storage is non-persistent if your VM gets moved to another host. Ideally we could our index storage on these volumes, and in the unlikely event that we’re moved to a new host, Couchbase would rebuild the indexes on that node.
I submitted a forum post on this a few years back with 4.0 went GA, and the answer was that storing indexing on non-persistent storage was “loosely supported” - Storing indexes on temporary storage
We’re really hoping that support for rebuilding missing index files is formally supported within 5.0, do you know if that’s true?