|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Issue Links:
|
Blocker
|
|
|
|
Reference
|
|
|
|
This issue is related to:
|
|
HADOOP-4257
TestLeaseRecovery2.testBlockSynchronization failing.
|
|
|
|
|
|
|
| Hadoop Flags: |
Reviewed
|
| Resolution Date: |
06/Jun/08 05:18 PM
|
|
When a client detects a error while writing to a block, it starts the generation-stamp-protocol to remove stale replicas. At the same time, if the namenode experiences a lease expiry event for that file, the namenode starts the generation-stamp-protocol for the same block. Now, the client and thr namenode ping-pongs trying to stamp the block replicas. This ping-pong can continue for a long time.
|
|
Description
|
When a client detects a error while writing to a block, it starts the generation-stamp-protocol to remove stale replicas. At the same time, if the namenode experiences a lease expiry event for that file, the namenode starts the generation-stamp-protocol for the same block. Now, the client and thr namenode ping-pongs trying to stamp the block replicas. This ping-pong can continue for a long time. |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Major
Race condition when client and namenode start block recovery simultaneously
