Major Description
Block incorrectly detected as bad in the following scenario:
Running multi threaded client program which performs write and read operation on a set of files
One block detected as bad by DN
Multiple recoveries where triggered from the NN side(It was happening every 1 hr)
After around 6 hrs the recovery was successful(Commitblocksynchronization successful at NN side)
At the DN side around the same time when Commitblocksynchronization happened one more NN recovery call has come and this was subsequently failig as already the block was recovered and the generation timestamp is updated.
At the DN side block verification failed and the block was reported as bad.
FSCk report is indicating that the block is corrupt