Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:  Switch to Threaded View
Zookeeper, mail # dev - Possible failure scenarios with
deserialization + multi?  Copy link to this message Possible
failure scenarios with deserialization + multi? Thomas Koch
2011-10-28, 15:04  continuing with my refactorings, I think I
might have found additional failure scenarios that could happen
with deserialization + multi transactions.  first failure
scenario:  MultiTxn creates two nodes, serialization sees only
the first node but not the second. The zxid of the deserialized
DataTree however is set to the MultiTxn, because deserialization
saw the first created node and its zxid.  second failure
scenario:  FileTxnSnapLog.restore contains a code block handling
a NODEEXISTS failure during deserialization. The problem is
explained there in a code comment. The code block however is
only executed for a CREATE txn, not for a multiTxn containing a
CREATE.  second failure scenario extend