[jira] [Assigned] (HDFS-16789) Update FileSystem class to read disk usage from actual usage value instead of file's length
[ https://issues.apache.org/jira/browse/HDFS-16789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang reassigned HDFS-16789: -- Assignee: Dave Teng > Update FileSystem class to read disk usage from actual usage value instead of > file's length > --- > > Key: HDFS-16789 > URL: https://issues.apache.org/jira/browse/HDFS-16789 > Project: Hadoop HDFS > Issue Type: Improvement > Components: dfs >Reporter: Dave Teng >Assignee: Dave Teng >Priority: Major > > Currently FileSystem class retrieve the disk usage value directly from > [file's > length|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java#L1895] > instead of actual usage value. > We need to update FileSystem & related classes to read disk usage from actual > usage value. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-16789) Update FileSystem class to read disk usage from actual usage value instead of file's length
Dave Teng created HDFS-16789: Summary: Update FileSystem class to read disk usage from actual usage value instead of file's length Key: HDFS-16789 URL: https://issues.apache.org/jira/browse/HDFS-16789 Project: Hadoop HDFS Issue Type: Improvement Components: dfs Reporter: Dave Teng Currently FileSystem class retrieve the disk usage value directly from [file's length|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java#L1895] instead of actual usage value. Update FileSystem & related classes to read disk usage from actual usage value. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-16789) Update FileSystem class to read disk usage from actual usage value instead of file's length
[ https://issues.apache.org/jira/browse/HDFS-16789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Teng updated HDFS-16789: - Description: Currently FileSystem class retrieve the disk usage value directly from [file's length|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java#L1895] instead of actual usage value. We need to update FileSystem & related classes to read disk usage from actual usage value. was: Currently FileSystem class retrieve the disk usage value directly from [file's length|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java#L1895] instead of actual usage value. Update FileSystem & related classes to read disk usage from actual usage value. > Update FileSystem class to read disk usage from actual usage value instead of > file's length > --- > > Key: HDFS-16789 > URL: https://issues.apache.org/jira/browse/HDFS-16789 > Project: Hadoop HDFS > Issue Type: Improvement > Components: dfs >Reporter: Dave Teng >Priority: Major > > Currently FileSystem class retrieve the disk usage value directly from > [file's > length|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java#L1895] > instead of actual usage value. > We need to update FileSystem & related classes to read disk usage from actual > usage value. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13369) FSCK Report broken with RequestHedgingProxyProvider
[
https://issues.apache.org/jira/browse/HDFS-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17611650#comment-17611650
]
ASF GitHub Bot commented on HDFS-13369:
---
ChenSammi merged PR #4917:
URL: https://github.com/apache/hadoop/pull/4917
> FSCK Report broken with RequestHedgingProxyProvider
>
>
> Key: HDFS-13369
> URL: https://issues.apache.org/jira/browse/HDFS-13369
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 2.8.3, 3.0.0, 3.1.0
>Reporter: Harshakiran Reddy
>Assignee: Ranith Sardar
>Priority: Major
> Labels: pull-request-available
> Attachments: HDFS-13369.001.patch, HDFS-13369.002.patch,
> HDFS-13369.003.patch, HDFS-13369.004.patch, HDFS-13369.005.patch,
> HDFS-13369.006.patch, HDFS-13369.007.patch
>
>
> Scenario:-
> 1.Configure the RequestHedgingProxy
> 2. write some files in file system
> 3. Take FSCK report for the above files
>
> {noformat}
> bin> hdfs fsck /file1 -locations -files -blocks
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.hadoop.hdfs.server.namenode.ha.RequestHedgingProxyProvider$RequestHedgingInvocationHandler
> cannot be cast to org.apache.hadoop.ipc.RpcInvocationHandler
> at org.apache.hadoop.ipc.RPC.getConnectionIdForProxy(RPC.java:626)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.getConnectionId(RetryInvocationHandler.java:438)
> at org.apache.hadoop.ipc.RPC.getConnectionIdForProxy(RPC.java:628)
> at org.apache.hadoop.ipc.RPC.getServerAddress(RPC.java:611)
> at org.apache.hadoop.hdfs.HAUtil.getAddressOfActive(HAUtil.java:263)
> at
> org.apache.hadoop.hdfs.tools.DFSck.getCurrentNamenodeAddress(DFSck.java:257)
> at org.apache.hadoop.hdfs.tools.DFSck.doWork(DFSck.java:319)
> at org.apache.hadoop.hdfs.tools.DFSck.access$000(DFSck.java:72)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:156)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1836)
> at org.apache.hadoop.hdfs.tools.DFSck.run(DFSck.java:152)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hadoop.hdfs.tools.DFSck.main(DFSck.java:385){noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13369) FSCK Report broken with RequestHedgingProxyProvider
[
https://issues.apache.org/jira/browse/HDFS-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17611649#comment-17611649
]
ASF GitHub Bot commented on HDFS-13369:
---
ChenSammi commented on PR #4917:
URL: https://github.com/apache/hadoop/pull/4917#issuecomment-1263717827
+1. Thanks @navinko for the contribution.
> FSCK Report broken with RequestHedgingProxyProvider
>
>
> Key: HDFS-13369
> URL: https://issues.apache.org/jira/browse/HDFS-13369
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 2.8.3, 3.0.0, 3.1.0
>Reporter: Harshakiran Reddy
>Assignee: Ranith Sardar
>Priority: Major
> Labels: pull-request-available
> Attachments: HDFS-13369.001.patch, HDFS-13369.002.patch,
> HDFS-13369.003.patch, HDFS-13369.004.patch, HDFS-13369.005.patch,
> HDFS-13369.006.patch, HDFS-13369.007.patch
>
>
> Scenario:-
> 1.Configure the RequestHedgingProxy
> 2. write some files in file system
> 3. Take FSCK report for the above files
>
> {noformat}
> bin> hdfs fsck /file1 -locations -files -blocks
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.hadoop.hdfs.server.namenode.ha.RequestHedgingProxyProvider$RequestHedgingInvocationHandler
> cannot be cast to org.apache.hadoop.ipc.RpcInvocationHandler
> at org.apache.hadoop.ipc.RPC.getConnectionIdForProxy(RPC.java:626)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.getConnectionId(RetryInvocationHandler.java:438)
> at org.apache.hadoop.ipc.RPC.getConnectionIdForProxy(RPC.java:628)
> at org.apache.hadoop.ipc.RPC.getServerAddress(RPC.java:611)
> at org.apache.hadoop.hdfs.HAUtil.getAddressOfActive(HAUtil.java:263)
> at
> org.apache.hadoop.hdfs.tools.DFSck.getCurrentNamenodeAddress(DFSck.java:257)
> at org.apache.hadoop.hdfs.tools.DFSck.doWork(DFSck.java:319)
> at org.apache.hadoop.hdfs.tools.DFSck.access$000(DFSck.java:72)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:156)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1836)
> at org.apache.hadoop.hdfs.tools.DFSck.run(DFSck.java:152)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hadoop.hdfs.tools.DFSck.main(DFSck.java:385){noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-16785) DataNode hold BP write lock to scan disk
[
https://issues.apache.org/jira/browse/HDFS-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17611503#comment-17611503
]
ASF GitHub Bot commented on HDFS-16785:
---
ZanderXu commented on PR #4945:
URL: https://github.com/apache/hadoop/pull/4945#issuecomment-1263411206
@MingXiangLi Sir, thanks for your review.
> Case2: It's wrong, but not caused by this lock.
About this case, I will create one new PR to fix it.
> And can avoid conflict cause by volume/block pool remove or add.
We can add one synchronized lock to `addBlockPool` and `shutdownBlockPool`
as before to avoid the conflict caused by volume/blockPool remove or add. And
this synchronized just lock volume/blockPool remove or add, so it will not
block other operations, such as read or write from client. If ok, I will fix it
in a new ticket with Case2 together.
@Hexiaoqiao looking forward your good ideas.
> DataNode hold BP write lock to scan disk
>
>
> Key: HDFS-16785
> URL: https://issues.apache.org/jira/browse/HDFS-16785
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: ZanderXu
>Assignee: ZanderXu
>Priority: Major
> Labels: pull-request-available
>
> When patching the fine-grained locking of datanode, I found that `addVolume`
> will hold the write block of the BP lock to scan the new volume to get the
> blocks. If we try to add one full volume that was fixed offline before, i
> will hold the write lock for a long time.
> The related code as bellows:
> {code:java}
> for (final NamespaceInfo nsInfo : nsInfos) {
> String bpid = nsInfo.getBlockPoolID();
> try (AutoCloseDataSetLock l = lockManager.writeLock(LockLevel.BLOCK_POOl,
> bpid)) {
> fsVolume.addBlockPool(bpid, this.conf, this.timer);
> fsVolume.getVolumeMap(bpid, tempVolumeMap, ramDiskReplicaTracker);
> } catch (IOException e) {
> LOG.warn("Caught exception when adding " + fsVolume +
> ". Will throw later.", e);
> exceptions.add(e);
> }
> } {code}
> And I noticed that this lock is added by HDFS-15382, means that this logic is
> not in lock before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HDFS-16788.
-
Resolution: Not A Bug
Reach out to the user mailing list, Jira is for tracking bugs not for user
queries
https://hadoop.apache.org/mailing_lists.html
> could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There
> are 50 datanode(s) running and no node(s) are excluded in this operation
> ---
>
> Key: HDFS-16788
> URL: https://issues.apache.org/jira/browse/HDFS-16788
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.1.0
>Reporter: ruiliang
>Priority: Major
> Attachments: image-2022-09-30-14-14-29-963.png,
> image-2022-09-30-14-14-44-164.png
>
>
>
> !image-2022-09-30-14-14-44-164.png!
> ||Configured Capacity:|3.02 PB|
> ||Configured Remote Capacity:|0 B|
> ||DFS Used:|1.39 PB (45.96%)|
> ||Non DFS Used:|0 B|
> ||DFS Remaining:|1.62 PB (53.67%)|
> ||Block Pool Used:|1.39 PB (45.96%)|
> ||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
> ||[Live
> Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
> (Decommissioned: 0, In Maintenance: 0)
> |
> I've been working hard in the background to balance the data,
> but before I discp when
> {code:java}
> hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
> -Ddfs.balancer.moverThreads=1200
> -Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
> -threshold 50
> {code}
> {code:java}
> hadoop distcp -Dmapreduce.task.timeout=60 -skipcrccheck -update hdfs://01
> hdfs://02xx
> syslog
> ...
> 2022-09-30 14:22:50,724 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream:
> Cannot allocate parity block(index=4, policy=RS-3-2-1024k). Not enough
> datanodes? Exclude nodes=[] 2022-09-30 14:22:58,389 INFO [main]
> org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
> #3: failed, blk_-9223372036808890525_3095130 2022-09-30 14:22:58,389 INFO
> [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed
> streamer #4: failed, block==null 2022-09-30 14:23:21,547 WARN [main]
> org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
> policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
> 14:23:29,319 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
> previously failed streamer #4: failed, blk_-9223372036808889612_3095200
> 2022-09-30 14:23:36,950 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream:
> Cannot allocate parity block(index=4, policy=RS-3-2-1024k). Not enough
> datanodes? Exclude nodes=[] 2022-09-30 14:23:44,822 INFO [main]
> org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
> #4: failed, blk_-922337203680572_3095307 2022-09-30 14:23:44,837 WARN
> [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity
> block(index=4, policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[]
> 2022-09-30 14:23:52,306 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
> replacing previously failed streamer #4: failed, block==null 2022-09-30
> 14:23:52,321 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
> allocate parity block(index=4, policy=RS-3-2-1024k). Not enough datanodes?
> Exclude nodes=[] 2022-09-30 14:23:59,822 INFO [main]
> org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
> #4: failed, block==null 2022-09-30 14:23:59,836 WARN [main]
> org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=3,
> policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
> 14:23:59,836 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
> allocate parity block(index=4, policy=RS-3-2-1024k). Not enough datanodes?
> Exclude nodes=[] 2022-09-30 14:24:07,302 INFO [main]
> org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
> #3: failed, blk_-9223372036808887853_3095387 2022-09-30 14:24:07,303 INFO
> [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed
> streamer #4: failed, block==null 2022-09-30 14:24:07,317 WARN [main]
> org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
> policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
> 14:24:15,383 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
> previously failed streamer #4: failed, block==null 2022-09-30 14:24:15,395
> WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity
> block(index=4, policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[]
>
[jira] [Updated] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruiliang updated HDFS-16788:
Description:
!image-2022-09-30-14-14-44-164.png!
||Configured Capacity:|3.02 PB|
||Configured Remote Capacity:|0 B|
||DFS Used:|1.39 PB (45.96%)|
||Non DFS Used:|0 B|
||DFS Remaining:|1.62 PB (53.67%)|
||Block Pool Used:|1.39 PB (45.96%)|
||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
||[Live
Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
(Decommissioned: 0, In Maintenance: 0)
|
I've been working hard in the background to balance the data,
but before I discp when
{code:java}
hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
-Ddfs.balancer.moverThreads=1200
-Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
-threshold 50
{code}
{code:java}
hadoop distcp -Dmapreduce.task.timeout=60 -skipcrccheck -update hdfs://01
hdfs://02xx
syslog
...
2022-09-30 14:22:50,724 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream:
Cannot allocate parity block(index=4, policy=RS-3-2-1024k). Not enough
datanodes? Exclude nodes=[] 2022-09-30 14:22:58,389 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#3: failed, blk_-9223372036808890525_3095130 2022-09-30 14:22:58,389 INFO
[main] org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed
streamer #4: failed, block==null 2022-09-30 14:23:21,547 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:23:29,319 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
previously failed streamer #4: failed, blk_-9223372036808889612_3095200
2022-09-30 14:23:36,950 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream:
Cannot allocate parity block(index=4, policy=RS-3-2-1024k). Not enough
datanodes? Exclude nodes=[] 2022-09-30 14:23:44,822 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#4: failed, blk_-922337203680572_3095307 2022-09-30 14:23:44,837 WARN
[main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity
block(index=4, policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[]
2022-09-30 14:23:52,306 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
replacing previously failed streamer #4: failed, block==null 2022-09-30
14:23:52,321 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
allocate parity block(index=4, policy=RS-3-2-1024k). Not enough datanodes?
Exclude nodes=[] 2022-09-30 14:23:59,822 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#4: failed, block==null 2022-09-30 14:23:59,836 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=3,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:23:59,836 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
allocate parity block(index=4, policy=RS-3-2-1024k). Not enough datanodes?
Exclude nodes=[] 2022-09-30 14:24:07,302 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#3: failed, blk_-9223372036808887853_3095387 2022-09-30 14:24:07,303 INFO
[main] org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed
streamer #4: failed, block==null 2022-09-30 14:24:07,317 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:24:15,383 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
previously failed streamer #4: failed, block==null 2022-09-30 14:24:15,395 WARN
[main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity
block(index=4, policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[]
2022-09-30 14:24:22,795 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
replacing previously failed streamer #4: failed, block==null 2022-09-30
14:24:22,812 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
allocate parity block(index=3, policy=RS-3-2-1024k). Not enough datanodes?
Exclude nodes=[] 2022-09-30 14:24:22,812 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:24:31,352 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
previously failed streamer #3: failed, blk_-9223372036808887133_3095476
2022-09-30 14:24:31,352 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
replacing previously failed streamer #4: failed, block==null
discp out
.
Error: java.io.IOException: File copy failed:
Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
[jira] [Updated] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruiliang updated HDFS-16788:
Description:
!image-2022-09-30-14-14-44-164.png!
||Configured Capacity:|3.02 PB|
||Configured Remote Capacity:|0 B|
||DFS Used:|1.39 PB (45.96%)|
||Non DFS Used:|0 B|
||DFS Remaining:|1.62 PB (53.67%)|
||Block Pool Used:|1.39 PB (45.96%)|
||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
||[Live
Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
(Decommissioned: 0, In Maintenance: 0)
|
I've been working hard in the background to balance the data,
but before I discp when
{code:java}
hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
-Ddfs.balancer.moverThreads=1200
-Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
-threshold 50
{code}
{code:java}
hadoop distcp -Dmapreduce.task.timeout=60 -skipcrccheck -update hdfs://01
hdfs://02xx
...
2022-09-30 14:22:50,724 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream:
Cannot allocate parity block(index=4, policy=RS-3-2-1024k). Not enough
datanodes? Exclude nodes=[] 2022-09-30 14:22:58,389 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#3: failed, blk_-9223372036808890525_3095130 2022-09-30 14:22:58,389 INFO
[main] org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed
streamer #4: failed, block==null 2022-09-30 14:23:21,547 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:23:29,319 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
previously failed streamer #4: failed, blk_-9223372036808889612_3095200
2022-09-30 14:23:36,950 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream:
Cannot allocate parity block(index=4, policy=RS-3-2-1024k). Not enough
datanodes? Exclude nodes=[] 2022-09-30 14:23:44,822 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#4: failed, blk_-922337203680572_3095307 2022-09-30 14:23:44,837 WARN
[main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity
block(index=4, policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[]
2022-09-30 14:23:52,306 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
replacing previously failed streamer #4: failed, block==null 2022-09-30
14:23:52,321 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
allocate parity block(index=4, policy=RS-3-2-1024k). Not enough datanodes?
Exclude nodes=[] 2022-09-30 14:23:59,822 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#4: failed, block==null 2022-09-30 14:23:59,836 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=3,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:23:59,836 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
allocate parity block(index=4, policy=RS-3-2-1024k). Not enough datanodes?
Exclude nodes=[] 2022-09-30 14:24:07,302 INFO [main]
org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed streamer
#3: failed, blk_-9223372036808887853_3095387 2022-09-30 14:24:07,303 INFO
[main] org.apache.hadoop.hdfs.DFSOutputStream: replacing previously failed
streamer #4: failed, block==null 2022-09-30 14:24:07,317 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:24:15,383 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
previously failed streamer #4: failed, block==null 2022-09-30 14:24:15,395 WARN
[main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity
block(index=4, policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[]
2022-09-30 14:24:22,795 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
replacing previously failed streamer #4: failed, block==null 2022-09-30
14:24:22,812 WARN [main] org.apache.hadoop.hdfs.DFSOutputStream: Cannot
allocate parity block(index=3, policy=RS-3-2-1024k). Not enough datanodes?
Exclude nodes=[] 2022-09-30 14:24:22,812 WARN [main]
org.apache.hadoop.hdfs.DFSOutputStream: Cannot allocate parity block(index=4,
policy=RS-3-2-1024k). Not enough datanodes? Exclude nodes=[] 2022-09-30
14:24:31,352 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream: replacing
previously failed streamer #3: failed, blk_-9223372036808887133_3095476
2022-09-30 14:24:31,352 INFO [main] org.apache.hadoop.hdfs.DFSOutputStream:
replacing previously failed streamer #4: failed, block==null
---
//
Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
/hive_warehouse/warehouse_old_snapshots/credit/.distcp.tmp.attempt_166383067_314191_m_08_2
could only be
[jira] [Updated] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruiliang updated HDFS-16788:
Description:
!image-2022-09-30-14-14-44-164.png!
||Configured Capacity:|3.02 PB|
||Configured Remote Capacity:|0 B|
||DFS Used:|1.39 PB (45.96%)|
||Non DFS Used:|0 B|
||DFS Remaining:|1.62 PB (53.67%)|
||Block Pool Used:|1.39 PB (45.96%)|
||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
||[Live
Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
(Decommissioned: 0, In Maintenance: 0)
|
I've been working hard in the background to balance the data, but before I
discp when
{code:java}
hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
-Ddfs.balancer.moverThreads=1200
-Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
-threshold 50{code}
{code:java}
//
Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
/hive_warehouse/warehouse_old_snapshots/credit/.distcp.tmp.attempt_166383067_314191_m_08_2
could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are
50 datanode(s) running and no node(s) are excluded in this operation.
at
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:2128)
at
org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.chooseTargetForNewBlock(FSDirWriteFileOp.java:286)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2706)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:875)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:561)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:524)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1025)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:876)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:822)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2682) at
org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1497)
at org.apache.hadoop.ipc.Client.call(Client.java:1443)
at org.apache.hadoop.ipc.Client.call(Client.java:1353)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
at com.sun.proxy.$Proxy13.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:510)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
at com.sun.proxy.$Proxy14.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.DFSOutputStream.addBlock(DFSOutputStream.java:1078)
at
org.apache.hadoop.hdfs.DFSStripedOutputStream.allocateNewBlock(DFSStripedOutputStream.java:479)
at
org.apache.hadoop.hdfs.DFSStripedOutputStream.writeChunk(DFSStripedOutputStream.java:525)
at
org.apache.hadoop.fs.FSOutputSummer.writeChecksumChunks(FSOutputSummer.java:217)
at org.apache.hadoop.fs.FSOutputSummer.write1(FSOutputSummer.java:125)
at org.apache.hadoop.fs.FSOutputSummer.write(FSOutputSummer.java:111)
at
org.apache.hadoop.fs.FSDataOutputStream$PositionCache.write(FSDataOutputStream.java:57)
at java.io.DataOutputStream.write(DataOutputStream.java:107)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122)
at
org.apache.hadoop.tools.mapred.RetriableFileCopyCommand.copyBytes(RetriableFileCopyCommand.java:290)
[jira] [Updated] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruiliang updated HDFS-16788:
Description:
!image-2022-09-30-14-14-44-164.png!
||Configured Capacity:|3.02 PB|
||Configured Remote Capacity:|0 B|
||DFS Used:|1.39 PB (45.96%)|
||Non DFS Used:|0 B|
||DFS Remaining:|1.62 PB (53.67%)|
||Block Pool Used:|1.39 PB (45.96%)|
||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
||[Live
Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
(Decommissioned: 0, In Maintenance: 0)
|
I've been working hard in the background to balance the data, but before I
discp when
{code:java}
hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
-Ddfs.balancer.moverThreads=1200
-Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
-threshold 50{code}
{code:java}
//
Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
/hive_warehouse/warehouse_old_snapshots/credit/.distcp.tmp.attempt_166383067_314191_m_08_2
could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are
50 datanode(s) running and no node(s) are excluded in this operation.
at
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:2128)
at
org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.chooseTargetForNewBlock(FSDirWriteFileOp.java:286)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2706)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:875)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:561)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:524)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1025)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:876)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:822)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2682) at
org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1497)
at org.apache.hadoop.ipc.Client.call(Client.java:1443)
at org.apache.hadoop.ipc.Client.call(Client.java:1353)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
at com.sun.proxy.$Proxy13.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:510)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
at com.sun.proxy.$Proxy14.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.DFSOutputStream.addBlock(DFSOutputStream.java:1078)
at
org.apache.hadoop.hdfs.DFSStripedOutputStream.allocateNewBlock(DFSStripedOutputStream.java:479)
at
org.apache.hadoop.hdfs.DFSStripedOutputStream.writeChunk(DFSStripedOutputStream.java:525)
at
org.apache.hadoop.fs.FSOutputSummer.writeChecksumChunks(FSOutputSummer.java:217)
at org.apache.hadoop.fs.FSOutputSummer.write1(FSOutputSummer.java:125)
at org.apache.hadoop.fs.FSOutputSummer.write(FSOutputSummer.java:111)
at
org.apache.hadoop.fs.FSDataOutputStream$PositionCache.write(FSDataOutputStream.java:57)
at java.io.DataOutputStream.write(DataOutputStream.java:107)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122)
at
org.apache.hadoop.tools.mapred.RetriableFileCopyCommand.copyBytes(RetriableFileCopyCommand.java:290)
[jira] [Created] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
ruiliang created HDFS-16788:
---
Summary: could only be written to 2 of the 3 required nodes for
RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in
this operation
Key: HDFS-16788
URL: https://issues.apache.org/jira/browse/HDFS-16788
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: ruiliang
Attachments: image-2022-09-30-14-14-29-963.png,
image-2022-09-30-14-14-44-164.png
!image-2022-09-30-14-14-44-164.png!
||Configured Capacity:|3.02 PB|
||Configured Remote Capacity:|0 B|
||DFS Used:|1.39 PB (45.96%)|
||Non DFS Used:|0 B|
||DFS Remaining:|1.62 PB (53.67%)|
||Block Pool Used:|1.39 PB (45.96%)|
||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
||[Live
Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
(Decommissioned: 0, In Maintenance: 0)
|
I've been working hard in the background to balance the data, but before I
discp when
{code:java}
hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
-Ddfs.balancer.moverThreads=1200
-Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
-threshold 50{code}
{code:java}
//
Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
/hive_warehouse/warehouse_old_snapshots/credit/.distcp.tmp.attempt_166383067_314191_m_08_2
could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are
50 datanode(s) running and no node(s) are excluded in this operation.
at
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:2128)
at
org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.chooseTargetForNewBlock(FSDirWriteFileOp.java:286)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2706)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:875)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:561)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:524)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1025)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:876)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:822)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2682) at
org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1497)
at org.apache.hadoop.ipc.Client.call(Client.java:1443)
at org.apache.hadoop.ipc.Client.call(Client.java:1353)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
at com.sun.proxy.$Proxy13.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:510)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
at
org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
at com.sun.proxy.$Proxy14.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.DFSOutputStream.addBlock(DFSOutputStream.java:1078)
at
org.apache.hadoop.hdfs.DFSStripedOutputStream.allocateNewBlock(DFSStripedOutputStream.java:479)
at
org.apache.hadoop.hdfs.DFSStripedOutputStream.writeChunk(DFSStripedOutputStream.java:525)
at
org.apache.hadoop.fs.FSOutputSummer.writeChecksumChunks(FSOutputSummer.java:217)
at org.apache.hadoop.fs.FSOutputSummer.write1(FSOutputSummer.java:125)
at org.apache.hadoop.fs.FSOutputSummer.write(FSOutputSummer.java:111)
at
[jira] [Updated] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruiliang updated HDFS-16788:
Component/s: hdfs
> could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There
> are 50 datanode(s) running and no node(s) are excluded in this operation
> ---
>
> Key: HDFS-16788
> URL: https://issues.apache.org/jira/browse/HDFS-16788
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.1.0
>Reporter: ruiliang
>Priority: Major
> Attachments: image-2022-09-30-14-14-29-963.png,
> image-2022-09-30-14-14-44-164.png
>
>
> !image-2022-09-30-14-14-44-164.png!
> ||Configured Capacity:|3.02 PB|
> ||Configured Remote Capacity:|0 B|
> ||DFS Used:|1.39 PB (45.96%)|
> ||Non DFS Used:|0 B|
> ||DFS Remaining:|1.62 PB (53.67%)|
> ||Block Pool Used:|1.39 PB (45.96%)|
> ||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
> ||[Live
> Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
> (Decommissioned: 0, In Maintenance: 0)
>
> |
> I've been working hard in the background to balance the data, but before I
> discp when
> {code:java}
> hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
> -Ddfs.balancer.moverThreads=1200
> -Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
> -threshold 50{code}
> {code:java}
> //
> Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
> /hive_warehouse/warehouse_old_snapshots/credit/.distcp.tmp.attempt_166383067_314191_m_08_2
> could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There
> are 50 datanode(s) running and no node(s) are excluded in this operation.
> at
> org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:2128)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.chooseTargetForNewBlock(FSDirWriteFileOp.java:286)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2706)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:875)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:561)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:524)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1025)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:876)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:822)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2682)
> at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1497)
> at org.apache.hadoop.ipc.Client.call(Client.java:1443)
> at org.apache.hadoop.ipc.Client.call(Client.java:1353)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
> at com.sun.proxy.$Proxy13.addBlock(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:510)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
> at com.sun.proxy.$Proxy14.addBlock(Unknown Source)
> at
>
[jira] [Updated] (HDFS-16788) could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There are 50 datanode(s) running and no node(s) are excluded in this operation
[
https://issues.apache.org/jira/browse/HDFS-16788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruiliang updated HDFS-16788:
Affects Version/s: 3.1.0
> could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There
> are 50 datanode(s) running and no node(s) are excluded in this operation
> ---
>
> Key: HDFS-16788
> URL: https://issues.apache.org/jira/browse/HDFS-16788
> Project: Hadoop HDFS
> Issue Type: Improvement
>Affects Versions: 3.1.0
>Reporter: ruiliang
>Priority: Major
> Attachments: image-2022-09-30-14-14-29-963.png,
> image-2022-09-30-14-14-44-164.png
>
>
> !image-2022-09-30-14-14-44-164.png!
> ||Configured Capacity:|3.02 PB|
> ||Configured Remote Capacity:|0 B|
> ||DFS Used:|1.39 PB (45.96%)|
> ||Non DFS Used:|0 B|
> ||DFS Remaining:|1.62 PB (53.67%)|
> ||Block Pool Used:|1.39 PB (45.96%)|
> ||DataNodes usages% (Min/Median/Max/stdDev):|8.20% / 32.44% / 98.85% / 37.30%|
> ||[Live
> Nodes|http://fs-hiido-yycluster06-yynn1.hiido.host.yydevops.com:50070/dfshealth.html#tab-datanode]|50
> (Decommissioned: 0, In Maintenance: 0)
>
> |
> I've been working hard in the background to balance the data, but before I
> discp when
> {code:java}
> hdfs balancer -Ddfs.datanode.balance.max.concurrent.moves=300
> -Ddfs.balancer.moverThreads=1200
> -Ddfs.datanode.balance.bandwidthPerSec=1073741824 -fs hdfs://yycluster06
> -threshold 50{code}
> {code:java}
> //
> Caused by: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File
> /hive_warehouse/warehouse_old_snapshots/credit/.distcp.tmp.attempt_166383067_314191_m_08_2
> could only be written to 2 of the 3 required nodes for RS-3-2-1024k. There
> are 50 datanode(s) running and no node(s) are excluded in this operation.
> at
> org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:2128)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.chooseTargetForNewBlock(FSDirWriteFileOp.java:286)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2706)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:875)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:561)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:524)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1025)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:876)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:822)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2682)
> at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1497)
> at org.apache.hadoop.ipc.Client.call(Client.java:1443)
> at org.apache.hadoop.ipc.Client.call(Client.java:1353)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
> at com.sun.proxy.$Proxy13.addBlock(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:510)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
> at com.sun.proxy.$Proxy14.addBlock(Unknown Source)
> at
>
