dannytbecker opened a new pull request, #6708:
URL: https://github.com/apache/hadoop/pull/6708
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
# Description of PR
## Summary
There is a race condition between IncrementalBlockReports (IBR) and
EditLogTailer in Standby NameNode (SNN) which can lead to leaked IBRs and false
corrupt blocks after HA Failover. The race condition occurs when the SNN loads
the edit logs before it receives the block reports from DataNode (DN).
## Example
In the following example there is a block (b1) with 3 generation stamps
(gs1, gs2, gs3).
1. SNN1 loads edit logs for b1gs1 and b1gs2.
1. DN1 sends the IBR for b1gs1 to SNN1.
1. SNN1 will determine that the reported block b1gs1 from DN1 is corrupt
and it will be queued for later.
[BlockManager.java](https://github.com/apache/hadoop/blob/6ed73896f6e8b4b7c720eff64193cb30b3e77fb2/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java#L3447C1-L3464C6)
``` java
BlockToMarkCorrupt c = checkReplicaCorrupt(
block, reportedState, storedBlock, ucState, dn);
if (c != null) {
if (shouldPostponeBlocksFromFuture) {
// If the block is an out-of-date generation stamp or state,
// but we're the standby, we shouldn't treat it as corrupt,
// but instead just queue it for later processing.
// Storing the reported block for later processing, as that is what
// comes from the IBR / FBR and hence what we should use to compare
// against the memory state.
// See HDFS-6289 and HDFS-15422 for more context.
queueReportedBlock(storageInfo, block, reportedState,
QUEUE_REASON_CORRUPT_STATE);
} else {
toCorrupt.add(c);
}
return storedBlock;
}
```
1. DN1 sends IBR for b1gs2 and b1gs3 to SNN1.
1. SNN1 processes b1sg2 and updates the blocks map.
1. SNN1 queues b1gs3 for later because it determines that b1gs3 is a future
genstamp.
1. SNN1 loads b1gs3 edit logs and processes the queued reports for b1.
1. SNN1 processes b1gs1 first and puts it back in the queue.
1. SNN1 processes b1gs3 next and updates the blocks map.
1. Later, SNN1 becomes the Active NameNode (ANN) during an HA Failover.
1. SNN1 will catch to the latest edit logs, then process all queued block
reports to become the ANN.
1. ANN1 will process b1gs1 and mark it as corrupt.
If the example above happens for every DN which stores b1, then when the HA
failover happens, b1 will be incorrectly marked as corrupt. This will be fixed
when the first DN sends a FullBlockReport or an IBR for b1.
## Logs from Active Cluster
I added the following logs to confirm this issue in an active cluster:
``` java
BlockToMarkCorrupt c = checkReplicaCorrupt(
block, reportedState, storedBlock, ucState, dn);
if (c != null) {
DatanodeStorageInfo storedStorageInfo = storedBlock.findStorageInfo(dn);
LOG.info("Found corrupt block {} [{}, {}] from DN {}. Stored block {} from
DN {}",
block, reportedState.name(), ucState.name(), storageInfo, storedBlock,
storedStorageInfo);
if (storageInfo.equals(storedStorageInfo) &&
storedBlock.getGenerationStamp() > block.getGenerationStamp()) {
LOG.info("Stored Block {} from the same DN {} has a newer GenStamp." +
storedBlock, storedStorageInfo);
}
if (shouldPostponeBlocksFromFuture) {
// If the block is an out-of-date generation stamp or state,
// but we're the standby, we shouldn't treat it as corrupt,
// but instead just queue it for later processing.
// Storing the reported block for later processing, as that is what
// comes from the IBR / FBR and hence what we should use to compare
// against the memory state.
// See HDFS-6289 and HDFS-15422 for more context.
queueReportedBlock(storageInfo, block, reportedState,
QUEUE_REASON_CORRUPT_STATE);
LOG.info("Queueing the block {} for later processing", block);
} else {
toCorrupt.add(c);
LOG.info("Marking the block {} as corrupt", block);
}
return storedBlock;
}
```
Logs from nn1 (Active):
``` java
2024-04-03T03:00:52.524-0700,INFO,[IPC Server handler 6 on default port
443],org.apache.hadoop.hdfs.server.namenode.FSNamesystem,"updatePipeline(blk_66092666802_65700910634,
newGS=65700925027, newLength=10485760, newNodes=[[DN1]:10010, [DN2]:10010,
[DN3]:10010, client=client1)"
2024-04-03T03:00:52.539-0700,INFO,[IPC Server handler 6 on default port
443],org.apache.hadoop.hdfs.server.namenode.FSNamesystem,"updatePipeline(blk_66092666802_65700910634
=> blk_66092666802_65700925027) success"
2024-04-03T03:01:07.413-0700,INFO,[IPC Server handler 6 on default port
443],org.apache.hadoop.hdfs.server.namenode.FSNamesystem,"updatePipeline(blk_66092666802_65700925027,
newGS=65700933553, newLength=20971520, newNodes=[[DN1]:10010, [DN2]:10010,
[DN3]:10010, client=client1)"
2024-04-03T03:01:07.413-0700,INFO,[IPC Server handler 6 on default port
443],org.apache.hadoop.hdfs.server.namenode.FSNamesystem,"updatePipeline(blk_66092666802_65700925027
=> blk_66092666802_65700933553) success"
```
Logs from nn2 (Standby):
``` java
2024-04-03T03:01:23.067-0700,INFO,[Block report
processor],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Found
corrupt block blk_66092666802_65700925027 [FINALIZED, COMPLETE] from DN
[DISK]DS-1:NORMAL:[DN1]:10010. Stored block blk_66092666802_65700933553 from DN
null"
2024-04-03T03:01:23.067-0700,INFO,[Block report
processor],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Queueing
the block blk_66092666802_65700925027 for later processing"
2024-04-03T03:01:24.159-0700,INFO,[Block report
processor],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Found
corrupt block blk_66092666802_65700925027 [FINALIZED, COMPLETE] from DN
[DISK]DS-3:NORMAL:[DN3]:10010. Stored block blk_66092666802_65700933553 from DN
null"
2024-04-03T03:01:24.159-0700,INFO,[Block report
processor],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Queueing
the block blk_66092666802_65700925027 for later processing"
2024-04-03T03:01:24.159-0700,INFO,[Block report
processor],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Found
corrupt block blk_66092666802_65700925027 [FINALIZED, COMPLETE] from DN
[DISK]DS-2:NORMAL:[DN2]:10010. Stored block blk_66092666802_65700933553 from DN
null"
2024-04-03T03:01:24.159-0700,INFO,[Block report
processor],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Queueing
the block blk_66092666802_65700925027 for later processing"
```
Logs from nn2 when it transitions to Active:
``` java
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Found corrupt
block blk_66092666802_65700925027 [FINALIZED, COMPLETE] from DN
[DISK]DS-1:NORMAL:[DN1]:10010. Stored block blk_66092666802_65700933553 from DN
[DISK]DS-1:NORMAL:[DN1]:10010"
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Stored Block
blk_66092666802_65700933553 from the same DN [DISK]DS-1:NORMAL:[DN1]:10010 has
a newer GenStamp."
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Marking the
block blk_66092666802_65700925027 as corrupt"
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Found corrupt
block blk_66092666802_65700925027 [FINALIZED, COMPLETE] from DN
[DISK]DS-2:NORMAL:[DN2]:10010. Stored block blk_66092666802_65700933553 from DN
[DISK]DS-2:NORMAL:[DN2]:10010"
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Stored Block
blk_66092666802_65700933553 from the same DN [DISK]DS-2:NORMAL:[DN2]:10010 has
a newer GenStamp."
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Marking the
block blk_66092666802_65700925027 as corrupt"
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Found corrupt
block blk_66092666802_65700925027 [FINALIZED, COMPLETE] from DN
[DISK]DS-3:NORMAL:[DN3]:10010. Stored block blk_66092666802_65700933553 from DN
[DISK]DS-3:NORMAL:[DN3]:10010"
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Stored Block
blk_66092666802_65700933553 from the same DN [DISK]DS-3:NORMAL:[DN3]:10010 has
a newer GenStamp."
2024-04-03T15:39:09.050-0700,INFO,[IPC Server handler 8 on default port
8020],org.apache.hadoop.hdfs.server.blockmanagement.BlockManager,"Marking the
block blk_66092666802_65700925027 as corrupt"
```
## How was this patch tested?
## For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
