[
https://issues.apache.org/jira/browse/HDFS-17592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17592:
---
Description:
FastCopy is a faster data copy tools. In federation cluster or a single
cluster ,
[
https://issues.apache.org/jira/browse/HDFS-17592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17592:
---
Attachment: FastCopy via Transfer.jpg
> FastCopy support data copy in different nameservices without
[
https://issues.apache.org/jira/browse/HDFS-17592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17592:
--
Assignee: liuguanghua
> FastCopy support data copy in different nameservices without
liuguanghua created HDFS-17592:
--
Summary: FastCopy support data copy in different nameservices
without federation
Key: HDFS-17592
URL: https://issues.apache.org/jira/browse/HDFS-17592
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDFS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867676#comment-17867676
]
liuguanghua commented on HDFS-2139:
---
-- We already has hadoop distcp, Why do we need hdfs dfs -distcp?
[
https://issues.apache.org/jira/browse/HDFS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867636#comment-17867636
]
liuguanghua edited comment on HDFS-2139 at 7/22/24 2:52 AM:
[~hexiaoqiao] ,
[
https://issues.apache.org/jira/browse/HDFS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867636#comment-17867636
]
liuguanghua commented on HDFS-2139:
---
[~hexiaoqiao] , thanks for reply.
For 3 : fastcopy can use in a
[
https://issues.apache.org/jira/browse/HDFS-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17581:
---
Description:
Add FastCopy Tool ：
（1） support data replication with replication files
（2） support
liuguanghua created HDFS-17582:
--
Summary: Distcp support fastcopy
Key: HDFS-17582
URL: https://issues.apache.org/jira/browse/HDFS-17582
Project: Hadoop HDFS
Issue Type: Sub-task
liuguanghua created HDFS-17581:
--
Summary: Add FastCopy tool and support dfs -fastcp command
Key: HDFS-17581
URL: https://issues.apache.org/jira/browse/HDFS-17581
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847165#comment-17847165
]
liuguanghua commented on HDFS-17509:
Thanks [~xuzq_zander]
> RBF: Fix ClientProtocol.concat will
[
https://issues.apache.org/jira/browse/HDFS-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17509:
--
Assignee: liuguanghua
> RBF: Fix ClientProtocol.concat will throw NPE if tgr is a empty
[
https://issues.apache.org/jira/browse/HDFS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846574#comment-17846574
]
liuguanghua commented on HDFS-2139:
---
[~haiyang Hu] Hello sir. Are you still working on this now ? I am
[
https://issues.apache.org/jira/browse/HDFS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844497#comment-17844497
]
liuguanghua commented on HDFS-2139:
---
[~xuzq_zander] Hello,sir. The design doc can not be viewd
[
https://issues.apache.org/jira/browse/HDFS-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17509:
---
Summary: RBF: Fix ClientProtocol.concat will throw NPE if tgr is a empty
file. (was: RBF:
[
https://issues.apache.org/jira/browse/HDFS-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17509:
---
Description:
hdfs dfs -concat /tmp/merge /tmp/t1 /tmp/t2
When /tmp/merge is a empty file, this
liuguanghua created HDFS-17509:
--
Summary: RBF: ClientProtocol.concat will throw NPE if tgr is a
empty file.
Key: HDFS-17509
URL: https://issues.apache.org/jira/browse/HDFS-17509
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829445#comment-17829445
]
liuguanghua edited comment on HDFS-16016 at 3/21/24 9:13 AM:
-
Thank for
[
https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829445#comment-17829445
]
liuguanghua commented on HDFS-16016:
Thank for reply.
IBR contains DELETED_BLOCK,
[
https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829403#comment-17829403
]
liuguanghua commented on HDFS-16016:
In step4, It is according to the following way？
(1) In a loop,
[
https://issues.apache.org/jira/browse/HDFS-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17357:
---
Summary: NioInetPeer.close() should close socket connection. (was: EC:
NioInetPeer.close() should
[
https://issues.apache.org/jira/browse/HDFS-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17357:
---
Description:
NioInetPeer.close() now do not close socket connection.
And I found 3w+ connections
[
https://issues.apache.org/jira/browse/HDFS-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17357:
---
Description:
NioInetPeer.close() now do not close socket connection.
In my environment，all
[
https://issues.apache.org/jira/browse/HDFS-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17357:
---
Description:
NioInetPeer.close() now do not close socket connection.
In my environment，all
liuguanghua created HDFS-17357:
--
Summary: NioInetPeer.close() should close socket connection.
Key: HDFS-17357
URL: https://issues.apache.org/jira/browse/HDFS-17357
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17357:
--
Assignee: liuguanghua
> NioInetPeer.close() should close socket connection.
>
[
https://issues.apache.org/jira/browse/HDFS-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17311:
---
Description:
In the Router, find blow log
2023-12-29 15:18:54,799 ERROR
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17300:
--
Assignee: liuguanghua
> [SBN READ] A rpc call in Observer should throw
>
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17300:
---
Summary: [SBN READ] A rpc call in Observer should throw
ObserverRetryOnActiveException if its
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17300:
---
Description:
Now when Observer is enable, Observer will update its stateid through that
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17300:
---
Summary: [SBN READ] A rcp call in Observer should throw
ObserverRetryOnActiveException if its
[ https://issues.apache.org/jira/browse/HDFS-17309 ]
liuguanghua deleted comment on HDFS-17309:
was (Author: liuguanghua):
[~slfan1989] Ok, I will submit new PR according to this format in the future.
Thank you.
> RBF: Fix Router Safemode
[
https://issues.apache.org/jira/browse/HDFS-17309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803508#comment-17803508
]
liuguanghua commented on HDFS-17309:
[~slfan1989] Ok, I will submit new PR according to this format
[
https://issues.apache.org/jira/browse/HDFS-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17325:
--
Assignee: liuguanghua
> Doc: Fix the documentation of fs expunge command in
[
https://issues.apache.org/jira/browse/HDFS-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17325:
---
Description:
Fix doc in FileSystemShell.md.
hadoop fs -expunge --immediate should be hadoop fs
liuguanghua created HDFS-17325:
--
Summary: Doc: Fix the documentation of fs expunge command in
FileSystemShell.md
Key: HDFS-17325
URL: https://issues.apache.org/jira/browse/HDFS-17325
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDFS-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17324:
--
Assignee: liuguanghua
> RBF: Router should not return nameservices that not enable observer
[
https://issues.apache.org/jira/browse/HDFS-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17324:
---
Description:
{color:#172b4d}Router Observer Read is controled by
[
https://issues.apache.org/jira/browse/HDFS-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17324:
---
Description:
{color:#172b4d}Router Observer Read is controled by
liuguanghua created HDFS-17324:
--
Summary: RBF: Router should not return nameservices that not
enable observer read in RpcResponseHeaderProto
Key: HDFS-17324
URL: https://issues.apache.org/jira/browse/HDFS-17324
[
https://issues.apache.org/jira/browse/HDFS-17321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17321:
---
Description:
Router should have the ability to to auto msync to a nameservice. And it can
ensure
liuguanghua created HDFS-17321:
--
Summary: RBF: Add RouterAutoMsyncService for auto msync in Router
Key: HDFS-17321
URL: https://issues.apache.org/jira/browse/HDFS-17321
Project: Hadoop HDFS
liuguanghua created HDFS-17311:
--
Summary: RBF: ConnectionManager creatorQueue should offer a pool
that is not already in creatorQueue.
Key: HDFS-17311
URL: https://issues.apache.org/jira/browse/HDFS-17311
liuguanghua created HDFS-17309:
--
Summary: Fix Router Safemode check contidition error
Key: HDFS-17309
URL: https://issues.apache.org/jira/browse/HDFS-17309
Project: Hadoop HDFS
Issue Type: Bug
liuguanghua created HDFS-17306:
--
Summary: RBF:Router should not return nameservices that does not
enable observer nodes in RpcResponseHeaderProto
Key: HDFS-17306
URL: https://issues.apache.org/jira/browse/HDFS-17306
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17300:
---
Description:
Now when Observer NN is used, if the stateid is delayed , the
rpcServer
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17300:
---
Summary: [SBN READ] Observer should throw ObserverRetryOnActiveException if
stateid is always
[
https://issues.apache.org/jira/browse/HDFS-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17300:
---
Description:
Now when Observer NN is used, if the stateid is delayed , the rpcServer will
be
liuguanghua created HDFS-17300:
--
Summary: [SBN READ] Observer should throw
ObserverRetryOnActiveException if stateid is always delayed with Active
Namenode for a period of time
Key: HDFS-17300
URL:
[
https://issues.apache.org/jira/browse/HDFS-17170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua resolved HDFS-17170.
Resolution: Not A Problem
> add metris for datanode in function processQueueMessages and reportTo
[
https://issues.apache.org/jira/browse/HDFS-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17285:
---
Summary: RBF: Add a safe mode check period configuration (was: [RBF]
Decrease dfsrouter safe mode
[
https://issues.apache.org/jira/browse/HDFS-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17285:
---
Description:
When dfsrouter start, it enters safe mode. And it will cost 1min to leave.
The log is
liuguanghua created HDFS-17285:
--
Summary: [RBF] Decrease dfsrouter safe mode check period.
Key: HDFS-17285
URL: https://issues.apache.org/jira/browse/HDFS-17285
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-17269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17269:
--
Assignee: liuguanghua
> [RBF] Make listStatus user root trash dir will return all subclusters
liuguanghua created HDFS-17269:
--
Summary: [RBF] Make listStatus user root trash dir will return all
subclusters trash subdirs if user has any mount points in nameservice.
Key: HDFS-17269
URL:
[
https://issues.apache.org/jira/browse/HDFS-17263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17263:
--
Assignee: liuguanghua
> RBF: Fix client ls trash path cannot get except default nameservices
liuguanghua created HDFS-17263:
--
Summary: [RBF] Fix client ls trash path cannot get except default
nameservices trash path
Key: HDFS-17263
URL: https://issues.apache.org/jira/browse/HDFS-17263
Project:
[
https://issues.apache.org/jira/browse/HDFS-17261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17261:
---
Description:
With DFSRouter, Suppose there are two nameservices ： ns0，ns1
# Add mountTable
liuguanghua created HDFS-17261:
--
Summary: Fix getFileInfo return wrong path when get mountTable
path which multi-level
Key: HDFS-17261
URL: https://issues.apache.org/jira/browse/HDFS-17261
Project:
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Labels: (was: pull-request-available)
> invalid
> ---
>
> Key: HDFS-17248
>
[
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17249:
--
Assignee: liuguanghua
> TestDFSUtil.testIsValidName() run failure
>
[
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17249:
---
Summary: TestDFSUtil.testIsValidName() run failure (was: Add test case for
DFSUtil.isValidName)
>
[
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17249:
---
Description:
TestDFSUtil.testIsValidName runs failed when
[
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17249:
---
Description:
TestDFSUtil.testIsValidName runs failed when
[
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17249:
---
Description:
TestDFSUtil.testIsValidName runs failed when
[
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17249:
---
Summary: Add test case for DFSUtil.isValidName (was: Fix test case for
HDFS-17246)
> Add test case
liuguanghua created HDFS-17249:
--
Summary: Fix test case for HDFS-17246
Key: HDFS-17249
URL: https://issues.apache.org/jira/browse/HDFS-17249
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Description:
was:
Add test case for HDFS-17246 and
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Summary: invalid (was: Fix )
> invalid
> ---
>
> Key: HDFS-17248
>
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Summary: Fix (was: Add Test case for for building Hadoop on Windows and )
> Fix
>
>
>
[
https://issues.apache.org/jira/browse/HDFS-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17246:
---
Summary: Fix shaded client for building Hadoop on Windows (was: Fix
DFSUtilClient.ValidName ERROR)
[
https://issues.apache.org/jira/browse/HDFS-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17246:
---
Summary: Fix DFSUtilClient.ValidName ERROR (was: Fix shaded client for
building Hadoop on Windows)
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Description:
Add test case for HDFS-17246 and
assertFalse(DFSUtil.isValidName("/foo/:/bar"));
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua resolved HDFS-17248.
Resolution: Invalid
> Add Test case for for building Hadoop on Windows and
>
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Summary: Add Test case for for building Hadoop on Windows and (was: Add
Test for for building
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Summary: Add Test for for building Hadoop on Windows (was: Fix
DFSUtilClient.ValidName ERROR)
>
liuguanghua created HDFS-17248:
--
Summary: Fix DFSUtilClient.ValidName ERROR
Key: HDFS-17248
URL: https://issues.apache.org/jira/browse/HDFS-17248
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17248:
---
Priority: Minor (was: Major)
> Fix DFSUtilClient.ValidName ERROR
>
[
https://issues.apache.org/jira/browse/HDFS-14500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-14500:
---
Description:
When testing out a cluster with the edit log tailing fast path feature enabled
liuguanghua created HDFS-17186:
--
Summary: NamenodeProtocol.versionRequest() threw null in DFSRouter
service.
Key: HDFS-17186
URL: https://issues.apache.org/jira/browse/HDFS-17186
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17182:
---
Summary: DataSetLockManager.lockLeakCheck() is not thread-safe. (was:
[
https://issues.apache.org/jira/browse/HDFS-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17182:
---
Summary: DataSetLockManager.threadCountMap is not thread-safe. (was:
threadCountMap is not
[
https://issues.apache.org/jira/browse/HDFS-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17182:
--
Assignee: liuguanghua
> threadCountMap is not thread-safe.
>
liuguanghua created HDFS-17182:
--
Summary: threadCountMap is not thread-safe.
Key: HDFS-17182
URL: https://issues.apache.org/jira/browse/HDFS-17182
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reassigned HDFS-17129:
--
Assignee: liuguanghua
> mis-order of ibr and fbr on datanode
>
[ https://issues.apache.org/jira/browse/HDFS-17129 ]
liuguanghua deleted comment on HDFS-17129:
was (Author: liuguanghua):
merge into HDFS-17121
> mis-order of ibr and fbr on datanode
> -
>
>
[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua reopened HDFS-17129:
> mis-order of ibr and fbr on datanode
> -
>
>
liuguanghua created HDFS-17170:
--
Summary: add metris for datanode in function processQueueMessages
and reportTo
Key: HDFS-17170
URL: https://issues.apache.org/jira/browse/HDFS-17170
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua resolved HDFS-17129.
Resolution: Abandoned
merge into HDFS-17121
> mis-order of ibr and fbr on datanode
>
[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747716#comment-17747716
]
liuguanghua commented on HDFS-17129:
Yes , the fbr should acquire the lock all the time. And
liuguanghua created HDFS-17129:
--
Summary: mis-order of ibr and fbr on datanode
Key: HDFS-17129
URL: https://issues.apache.org/jira/browse/HDFS-17129
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17121:
---
Description:
After HDFS-16016 , it makes ibr in a thread to avoid heartbeat blocking with
ibr when
liuguanghua created HDFS-17121:
--
Summary: BPServiceActor to provide new thread to handle FBR
Key: HDFS-17121
URL: https://issues.apache.org/jira/browse/HDFS-17121
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732506#comment-17732506
]
liuguanghua commented on HDFS-17048:
[~hexiaoqiao] , I know the reason because my datanode config
[
https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732462#comment-17732462
]
liuguanghua commented on HDFS-17048:
Yes, it will be cleaned when re-full block report from DataNode.
[
https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua resolved HDFS-17048.
Resolution: Not A Problem
> FSNamesystem.delete() maybe cause data residue when active namenode
[
https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17048:
---
Component/s: hdfs
> FSNamesystem.delete() maybe cause data residue when active namenode crash or
>
[
https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17048:
---
Environment: hdfs3.3 (was:
)
> FSNamesystem.delete() maybe cause data residue when active
[
https://issues.apache.org/jira/browse/HDFS-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuguanghua updated HDFS-17048:
---
Description:
Consider the following scenario：
(1) User delete a hdfs dir with many blocks.
(2)
liuguanghua created HDFS-17048:
--
Summary: FSNamesystem.delete() maybe cause data residue when
active namenode crash or shutdown
Key: HDFS-17048
URL: https://issues.apache.org/jira/browse/HDFS-17048
1 - 100 of 122 matches
Mail list logo
