Hi there, We're using ODB for production uses on Amazon EC2. Our DB is over 100 GB.
Very often, when not perfectly shutting down the database, or even occasionally somewhat randomly, the database starts reindexing. We cannot use the DB while it is reindexing. This is a _huge_ problem. In a cluster, theoretically, if a DB shuts down and needs reindexing, I'm guessing we can remove that node from the cluster. Practically, that is an impossible situation for many reasons. First, whatever caused issues on the first DB will likely affect other systems. Especially since with 1 node removed, the others will be under a strain. I've had some experience with situations like this and it can get very ugly very very quickly. It also takes a very long time... Often, in test, we don't even allow it to reindex because it takes hours upon hours. I've never seen this sort of behaviour with other DBs I've used. They've all seemed extremely durable when it comes to things like random shutdowns. While I cannot speak for the type of recovery-based rebuilding, even reindexing on OrientDB seems to cause major slowdowns that are inappropriate for production. -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
