Issues

NamenodeFsck.getStorages uses objects from other transaction
HOPS-1613
NamenodeFsck.getCorruptReplicas uses objects from other transaction
HOPS-1612
NamenodeFsck.getNumReplicas uses objects from other transaction
HOPS-1611
BlockManager.addStoredBlockImmediateTx uses objects from other transaction
HOPS-1610
BlockManager.addStoredBlockUnderConstructionImmediateTx uses objects from other transaction
HOPS-1609
BlockManager.markBlockAsCorruptTx uses objects from other transaction
HOPS-1608
BlockManager.addStoredBlockUnderConstructionTx uses objects from other transaction
HOPS-1607
BlockManager.addStoredBlockTx uses object from other transaction
HOPS-1606
BlockManager.computeReplicationWorkForBlock uses object from other transaction
HOPS-1605
BlockManager.removeStoredBlocksTx uses objects from other transaction
HOPS-1604
BlockManager.processOverReplicatedBlocksOnReCommission uses objects from other transaction
HOPS-1603
BlockManager.processIncrementalBlockReport uses objects from other transaction
HOPS-1602
BlockManager.addBlocks uses objects from other transaction
HOPS-1601
LeaseManager.getNumUnderConstructionBlocks uses object from other transaction
HOPS-1600
FSNamesystem.listCorruptFileBlocks uses objects from other transaction
HOPS-1599
FSNamesystem.commitBlockSynchronization uses object from other transaction
HOPS-1598
DecommissionManager.handleInsufficientlyReplicated uses object from other transaction
HOPS-1597
DecommissionManager.pruneSufficientlyReplicated uses object from other transaction
HOPS-1596
Transactions should not use object comming from other transactions
HOPS-1595
Create lease lock rows,
HOPS-1594
Namenode dies when InodeId does not match in ReplicationMonitor
HOPS-1593
fix block count in the block report
HOPS-1592
Fix hash bucket locking order
HOPS-1591
Fix lease manager for rename operation
HOPS-1590
Do not reuse id in proto definition.
HOPS-1589
1-25 of 1572