From: Vladimir S. <vst...@gm...> - 2012-07-31 09:19:34
|
On Tue, Jul 31, 2012 at 05:35:45PM +0900, Michael Paquier wrote: > The main problem that I see here is that replicating data > asynchronously breaks MVCC. May I cite myself? When read request come in, it should go to replicated node if and only if requested data exists there, otherwise such request should go to distributed node where those data in question exists in any case. > So you are never sure that the data will be here or not on your > background nodes. If we control where the data stored in distributed nodes, why not to control the state of replicated nodes? In both cases we should know what data is where. > Ideas are of course always welcome, but if you want to add some new > features you will need to be more specific. I don't think what we discussing here is simply feature that may be added with an patch. The idea to move storage control on cluster level touches the basics and concept of XC. -- *************************** ## Vladimir Stavrinov ## vst...@gm... *************************** |