[
https://issues.apache.org/jira/browse/HDFS-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-17434:
Description:
In our cluster, the SendDataPacketBlockedOnNetworkNanosAvgTime metric ranges
from 5ms to
[
https://issues.apache.org/jira/browse/HDFS-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-17434:
Issue Type: Wish (was: Task)
> Selector.select in SocketIOWithTimeout.java has significant overhead
>
[
https://issues.apache.org/jira/browse/HDFS-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828925#comment-17828925
]
qinyuren commented on HDFS-17434:
-
[~hexiaoqiao] [~tasanuma] [~zanderxu]
Please take a look.
>
[
https://issues.apache.org/jira/browse/HDFS-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-17434:
Attachment: image-2024-03-20-19-55-18-378.png
> Selector.select in SocketIOWithTimeout.java has
[
https://issues.apache.org/jira/browse/HDFS-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-17434:
Issue Type: Test (was: Wish)
> Selector.select in SocketIOWithTimeout.java has significant overhead
>
[
https://issues.apache.org/jira/browse/HDFS-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-17434:
Description:
In our cluster, the SendDataPacketBlockedOnNetworkNanosAvgTime metric ranges
from 5ms to
qinyuren created HDFS-17434:
---
Summary: Selector.select in SocketIOWithTimeout.java has
significant overhead
Key: HDFS-17434
URL: https://issues.apache.org/jira/browse/HDFS-17434
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783445#comment-17783445
]
qinyuren edited comment on HDFS-15413 at 11/7/23 1:46 AM:
--
We also encountered
[
https://issues.apache.org/jira/browse/HDFS-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783445#comment-17783445
]
qinyuren edited comment on HDFS-15413 at 11/7/23 1:45 AM:
--
We also encountered
[
https://issues.apache.org/jira/browse/HDFS-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783445#comment-17783445
]
qinyuren commented on HDFS-15413:
-
We also encountered datanode socket timeout problems in the process of
[
https://issues.apache.org/jira/browse/HDFS-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764141#comment-17764141
]
qinyuren commented on HDFS-17187:
-
*hdfs fsck -blockId * can get the hdfs file path.
> add the tool that
[
https://issues.apache.org/jira/browse/HDFS-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16784:
Summary: replace readLock with writeLock in
#DatanodeAdminBackoffMonitor.scanDatanodeStorage (was: use
[
https://issues.apache.org/jira/browse/HDFS-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16784:
Description:
In #DatanodeAdminBackoffMonitor.scanDatanodeStorage, it uses a read lock to
protect the
[
https://issues.apache.org/jira/browse/HDFS-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16784:
Attachment: image-2022-09-28-15-37-24-622.png
> use write lock in
[
https://issues.apache.org/jira/browse/HDFS-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16784:
Description: In
> use write lock in #DatanodeAdminBackoffMonitor.scanDatanodeStorage
>
qinyuren created HDFS-16784:
---
Summary: use write lock in
#DatanodeAdminBackoffMonitor.scanDatanodeStorage
Key: HDFS-16784
URL: https://issues.apache.org/jira/browse/HDFS-16784
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-16575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16575:
Description:
The SPS may have misjudged in the following scenario:
# Create a file with one block and
[
https://issues.apache.org/jira/browse/HDFS-16575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16575:
Description:
# create a file with one block and this block have 3 replication with
[
https://issues.apache.org/jira/browse/HDFS-16575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16575:
Attachment: image-2022-05-10-11-21-31-987.png
> [SPS]: Should use real replication num instead
[
https://issues.apache.org/jira/browse/HDFS-16575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16575:
Attachment: image-2022-05-10-11-21-13-627.png
> [SPS]: Should use real replication num instead
qinyuren created HDFS-16575:
---
Summary: [SPS]: Should use real replication num instead
getReplication from namenode
Key: HDFS-16575
URL: https://issues.apache.org/jira/browse/HDFS-16575
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https//issues.apache.org/jira/browse/HDFS-16538] , we
found an EC file
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https//issues.apache.org/jira/browse/HDFS-16538] , we
found an EC file
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https//issues.apache.org/jira/browse/HDFS-16538] , we
found an EC file
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https//issues.apache.org/jira/browse/HDFS-16538] , we
found a ec
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https://issues.apache.org/jira/browse/HDFS-16538] , we
found a ec
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https//issues.apache.org/jira/browse/HDFS-16538]
{code:java}
[
https://issues.apache.org/jira/browse/HDFS-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16544:
Description:
In [HDFS-16538|http://https://issues.apache.org/jira/browse/HDFS-16538]
{code:java}
qinyuren created HDFS-16544:
---
Summary: EC decoding failed due to invalid buffer
Key: HDFS-16544
URL: https://issues.apache.org/jira/browse/HDFS-16544
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16538:
Description:
Currently, we found this error if the #StripeReader.readStripe() have more than
one block
[
https://issues.apache.org/jira/browse/HDFS-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16538:
Description:
Currently, we found this error if the #StripeReader.readStripe() have more than
one block
[
https://issues.apache.org/jira/browse/HDFS-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16538:
Description:
Currently, we found this error if the #StripeReader.readStripe() have more than
one block
[
https://issues.apache.org/jira/browse/HDFS-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16538:
Description:
We found this error if the #StripeReader.readStripe() have more than one block
read failed.
[
https://issues.apache.org/jira/browse/HDFS-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16538:
Description:
We found this error if the #StripeReader.readStripe() have more than one block
read failed.
[
https://issues.apache.org/jira/browse/HDFS-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16538:
Description:
We found this error if the #StripeReader.readStripe() have more than one block
read failed.
qinyuren created HDFS-16538:
---
Summary: EC decoding failed due to not enough valid inputs
Key: HDFS-16538
URL: https://issues.apache.org/jira/browse/HDFS-16538
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Description:
Currently, we ran SPS in our cluster and found this log. The SPSPathIdProcessor
thread
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode as
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode as
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode as
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode:
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode:
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode:
[
https://issues.apache.org/jira/browse/HDFS-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16514:
Description:
Recently, we used the [Standby Read] feature in our test cluster, and deployed
4 namenode:
qinyuren created HDFS-16514:
---
Summary: Reduce the failover sleep time if multiple namenode are
configured
Key: HDFS-16514
URL: https://issues.apache.org/jira/browse/HDFS-16514
Project: Hadoop HDFS
qinyuren created HDFS-16501:
---
Summary: Print the exception when reporting a bad block
Key: HDFS-16501
URL: https://issues.apache.org/jira/browse/HDFS-16501
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-16485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16485:
Description:
When SPSPathIdProcessor thread call getNextSPSPath(), it get the pathId from
namenode and
[
https://issues.apache.org/jira/browse/HDFS-16485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16485:
Description:
When SPSPathIdProcessor thread call getNextSPSPath(), it get the pathId from
namenode and
[
https://issues.apache.org/jira/browse/HDFS-16485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16485:
Description:
{code:java}
public Long getNextPathId() {
synchronized (pathsToBeTraveresed) {
return
qinyuren created HDFS-16485:
---
Summary: [SPS]: allow re-satisfy path after restarting sps process
Key: HDFS-16485
URL: https://issues.apache.org/jira/browse/HDFS-16485
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren reassigned HDFS-16484:
---
Assignee: qinyuren
> [SPS]: Fix an infinite loop bug in SPSPathIdProcessor thread
>
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Description:
In SPSPathIdProcessor thread, if it get a inodeId which path does not exist,
then the
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Description:
In SPSPathIdProcessor thread, if sps get a inodeId which path does not exist,
then the
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Description: !image-2022-02-25-14-35-42-255.png|width=682,height=195!
> [SPS]: Fix an infinite loop bug in
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Attachment: image-2022-02-25-14-35-42-255.png
> [SPS]: Fix an infinite loop bug in SPSPathIdProcessor
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Summary: [SPS]: Fix an infinite loop bug in SPSPathIdProcessor thread
(was: [SPS]: fix an infinite loop
qinyuren created HDFS-16484:
---
Summary: fix an infinite loop bug in SPSPathIdProcessor thread
Key: HDFS-16484
URL: https://issues.apache.org/jira/browse/HDFS-16484
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16484:
Summary: [SPS]: fix an infinite loop bug in SPSPathIdProcessor thread
(was: fix an infinite loop bug in
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16432:
Attachment: 20220209-120613.html
> Namenode block report add yield to avoid holding write lock too long
>
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16432:
Attachment: (was: 20220209-120613.html)
> Namenode block report add yield to avoid holding write lock
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16432:
Attachment: 20220209-120613.html
> Namenode block report add yield to avoid holding write lock too long
>
[
https://issues.apache.org/jira/browse/HDFS-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17482862#comment-17482862
]
qinyuren commented on HDFS-16423:
-
Thanks [~sodonnell] for the advices. I will add a PR to indicate why
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479811#comment-17479811
]
qinyuren edited comment on HDFS-16432 at 1/25/22, 6:29 AM:
---
[~hexiaoqiao],
[
https://issues.apache.org/jira/browse/HDFS-16433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480786#comment-17480786
]
qinyuren commented on HDFS-16433:
-
I think that object.wait() will release the lock.
> The synchronized
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479811#comment-17479811
]
qinyuren commented on HDFS-16432:
-
[~hexiaoqiao] [~tasanuma] Please take a look.
> Namenode block report
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16432:
Description:
!image-2022-01-20-15-19-28-384.png|width=683,height=132!
In our cluster, namenode block
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16432:
Description:
!image-2022-01-20-15-19-28-384.png|width=683,height=132!
In our cluster, namenode block
[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16432:
Description:
!image-2022-01-20-15-19-28-384.png|width=652,height=126!
In our cluster, namenode block
qinyuren created HDFS-16432:
---
Summary: Namenode block report add yield to avoid holding write
lock too long
Key: HDFS-16432
URL: https://issues.apache.org/jira/browse/HDFS-16432
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478312#comment-17478312
]
qinyuren commented on HDFS-16423:
-
Hi [~weichiu] , the problem we described in HDFS-16420 was not related
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472419#comment-17472419
]
qinyuren commented on HDFS-16420:
-
Hi [~tasanuma] , we've merged these two PR into our code. It seems
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472401#comment-17472401
]
qinyuren commented on HDFS-16420:
-
Hi [~ayushtkn] , we cherry-pick most of EC fixes which merged before
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471966#comment-17471966
]
qinyuren edited comment on HDFS-16420 at 1/10/22, 12:49 PM:
Hi [~sodonnell],
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471966#comment-17471966
]
qinyuren commented on HDFS-16420:
-
[~sodonnell] We cherry-pick most of EC fixes, especially those PR with
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471822#comment-17471822
]
qinyuren edited comment on HDFS-16420 at 1/10/22, 10:01 AM:
[~hexiaoqiao] ,
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471822#comment-17471822
]
qinyuren commented on HDFS-16420:
-
[~hexiaoqiao] [~ayushtkn] Please take a look at this problem.
> ec +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16420:
Description:
We have a similar problem as HDFS-16297 described.
In our cluster, we used ec(6+3) +
qinyuren created HDFS-16420:
---
Summary: ec + balancer may cause missing block
Key: HDFS-16420
URL: https://issues.apache.org/jira/browse/HDFS-16420
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren reassigned HDFS-16352:
---
Assignee: qinyuren
> return the real datanode numBlocks in #getDatanodeStorageReport
>
[
https://issues.apache.org/jira/browse/HDFS-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16352:
Summary: return the real datanode numBlocks in #getDatanodeStorageReport
(was: return the real datanode
[
https://issues.apache.org/jira/browse/HDFS-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16352:
Summary: return the real datanode blocknums in #getDatanodeStorageReport
(was: fill the real datanode
[
https://issues.apache.org/jira/browse/HDFS-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qinyuren updated HDFS-16352:
Description:
#getDatanodeStorageReport will return the array of DatanodeStorageReport which
contains the
qinyuren created HDFS-16352:
---
Summary: fill the real datanode blocknums in
#getDatanodeStorageReport
Key: HDFS-16352
URL: https://issues.apache.org/jira/browse/HDFS-16352
Project: Hadoop HDFS
1 - 100 of 106 matches
Mail list logo
