Serious issues with Membase 1.7.0
Last night we received an alert from our monitoring service that our Membase server is grinding CPU and RAM at almost full quota.
We've restarted the service and were horrified to find out that all our data has reverted somewhere to the dates between August 8th and the 16th.
Looking at the server it seems that around that date for some reason Membase stopped writing data into it's permanent database and simply worked from Cache all that time.
Attached are screenshots of the Membase logs:
Is it possible to somehow fix this issue?
What can we do to prevent this in the future?
Why did this happen in the first place?
Would a replication server prevent this kind of issues in the future?
Please reply as soon as you can,