Issues

NamenodeFsck.getCorruptReplicas uses objects from other transaction

NamenodeFsck.getNumReplicas uses objects from other transaction

BlockManager.addStoredBlockImmediateTx uses objects from other transaction

BlockManager.addStoredBlockUnderConstructionImmediateTx uses objects from other transaction

BlockManager.markBlockAsCorruptTx uses objects from other transaction

BlockManager.addStoredBlockUnderConstructionTx uses objects from other transaction

BlockManager.addStoredBlockTx uses object from other transaction

BlockManager.computeReplicationWorkForBlock uses object from other transaction

BlockManager.removeStoredBlocksTx uses objects from other transaction

BlockManager.processOverReplicatedBlocksOnReCommission uses objects from other transaction

BlockManager.processIncrementalBlockReport uses objects from other transaction

BlockManager.addBlocks uses objects from other transaction

LeaseManager.getNumUnderConstructionBlocks uses object from other transaction

FSNamesystem.listCorruptFileBlocks uses objects from other transaction

FSNamesystem.commitBlockSynchronization uses object from other transaction

DecommissionManager.handleInsufficientlyReplicated uses object from other transaction

DecommissionManager.pruneSufficientlyReplicated uses object from other transaction

Transactions should not use object comming from other transactions

Create lease lock rows,

Namenode dies when InodeId does not match in ReplicationMonitor

fix block count in the block report

Fix hash bucket locking order

Fix lease manager for rename operation

Do not reuse id in proto definition.