zhangshuyan0 opened a new pull request, #5743:
URL: https://github.com/apache/hadoop/pull/5743
…kGroupIdGenerator.
<!--
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
When I used multiple clients to write EC files concurrently, I found that
NameNode generated the same block group ID for different files:
> 2023-06-13 20:09:59,514 INFO org.apache.hadoop.hdfs.StateChange: BLOCK*
allocate blk_-9223372036854697568_14389 for /ec-test/10/4068034329705654124
2023-06-13 20:09:59,514 INFO org.apache.hadoop.hdfs.StateChange: BLOCK*
allocate blk_-9223372036854697568_14390 for /ec-test/19/7042966144171770731
After diving into `SequentialBlockGroupIdGenerator`, I found that the
current implementation of `nextValue` is not thread safety.
This problem must be fixed.
### How was this patch tested?
Add a new unit test.
--
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
