[jira] [Commented] (HDFS-16420) ec + balancer may cause missing block
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474335#comment-17474335
]
liuhongtong commented on HDFS-16420:
We have found the cause of the problem, which also exists in the latest code.
We'll fix this later.
> ec + balancer may cause missing block
> -
>
> Key: HDFS-16420
> URL: https://issues.apache.org/jira/browse/HDFS-16420
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: qinyuren
>Priority: Major
> Attachments: image-2022-01-10-17-31-35-910.png,
> image-2022-01-10-17-32-56-981.png
>
>
> We have a similar problem as HDFS-16297 described.
> In our cluster, we used {color:#de350b}ec(6+3) + balancer with version
> 3.1.0{color}, and the {color:#de350b}missing block{color} happened.
> We got the block(blk_-9223372036824119008) info from fsck, only 5 live
> replications and multiple redundant replications.
> {code:java}
> blk_-9223372036824119008_220037616 len=133370338 MISSING! Live_repl=5
> blk_-9223372036824119007:DatanodeInfoWithStorage,
> blk_-9223372036824119002:DatanodeInfoWithStorage,
> blk_-9223372036824119001:DatanodeInfoWithStorage,
> blk_-9223372036824119000:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage {code}
>
> We searched the log from all datanode, and found that the internal blocks of
> blk_-9223372036824119008 were deleted almost at the same time.
>
> {code:java}
> 08:15:58,550 INFO impl.FsDatasetAsyncDiskService
> (FsDatasetAsyncDiskService.java:run(333)) - Deleted
> BP-1606066499--1606188026755 blk_-9223372036824119008_220037616 URI
> file:/data15/hadoop/hdfs/data/current/BP-1606066499--1606188026755/current/finalized/subdir19/subdir9/blk_-9223372036824119008
> 08:16:21,214 INFO impl.FsDatasetAsyncDiskService
> (FsDatasetAsyncDiskService.java:run(333)) - Deleted
> BP-1606066499--1606188026755 blk_-9223372036824119006_220037616 URI
> file:/data4/hadoop/hdfs/data/current/BP-1606066499--1606188026755/current/finalized/subdir19/subdir9/blk_-9223372036824119006
> 08:16:55,737 INFO impl.FsDatasetAsyncDiskService
> (FsDatasetAsyncDiskService.java:run(333)) - Deleted
> BP-1606066499--1606188026755 blk_-9223372036824119005_220037616 URI
> file:/data2/hadoop/hdfs/data/current/BP-1606066499--1606188026755/current/finalized/subdir19/subdir9/blk_-9223372036824119005
> {code}
>
> The total number of internal blocks deleted during 08:15-08:17 are as follows
> ||internal block||index|| delete num||
> |blk_-9223372036824119008
> blk_-9223372036824119006
> blk_-9223372036824119005
> blk_-9223372036824119004
> blk_-9223372036824119003
> blk_-9223372036824119000 |0
> 2
> 3
> 4
> 5
> 8| 1
> 1
> 1
> 50
> 1
> 1|
>
> {color:#ff}During 08:15 to 08:17, we restarted 2 datanode and triggered
> full block report immediately.{color}
>
> There are 2 questions:
> 1. Why are there so many replicas of this block?
> 2. Why delete the internal block with only one copy?
> The reasons for the first problem may be as follows:
> 1. We set the full block report period of some datanode to 168 hours.
> 2. We have done a namenode HA operation.
> 3. After namenode HA, the state of storage became
> {color:#ff}stale{color}, and the state not change until next full block
> report.
> 4. The balancer copied the replica without deleting the replica from source
> node, because the source node have the stale storage, and the request was put
> into {color:#ff}postponedMisreplicatedBlocks{color}.
> 5. Balancer continues to copy the replica, eventually resulting in multiple
> copies of a replica
> !image-2022-01-10-17-31-35-910.png|width=642,height=269!
> The set of {color:#ff}rescannedMisreplicatedBlocks{color} have so many
> block to remove.
> !image-2022-01-10-17-32-56-981.png|width=745,height=124!
> As for the second question, we checked the code of
> {color:#de350b}processExtraRedundancyBlock{color}, but didn't find any
> problem.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-16420) ec + balancer may cause missing block
[
https://issues.apache.org/jira/browse/HDFS-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472621#comment-17472621
]
liuhongtong commented on HDFS-16420:
This issue resulted in massive data loss. We are very disappointed with the
stability of HDFS EC.
> ec + balancer may cause missing block
> -
>
> Key: HDFS-16420
> URL: https://issues.apache.org/jira/browse/HDFS-16420
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: qinyuren
>Priority: Major
> Attachments: image-2022-01-10-17-31-35-910.png,
> image-2022-01-10-17-32-56-981.png
>
>
> We have a similar problem as HDFS-16297 described.
> In our cluster, we used {color:#de350b}ec(6+3) + balancer with version
> 3.1.0{color}, and the {color:#de350b}missing block{color} happened.
> We got the block(blk_-9223372036824119008) info from fsck, only 5 live
> replications and multiple redundant replications.
> {code:java}
> blk_-9223372036824119008_220037616 len=133370338 MISSING! Live_repl=5
> blk_-9223372036824119007:DatanodeInfoWithStorage,
> blk_-9223372036824119002:DatanodeInfoWithStorage,
> blk_-9223372036824119001:DatanodeInfoWithStorage,
> blk_-9223372036824119000:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage,
> blk_-9223372036824119004:DatanodeInfoWithStorage {code}
>
> We searched the log from all datanode, and found that the internal blocks of
> blk_-9223372036824119008 were deleted almost at the same time.
>
> {code:java}
> 08:15:58,550 INFO impl.FsDatasetAsyncDiskService
> (FsDatasetAsyncDiskService.java:run(333)) - Deleted
> BP-1606066499--1606188026755 blk_-9223372036824119008_220037616 URI
> file:/data15/hadoop/hdfs/data/current/BP-1606066499--1606188026755/current/finalized/subdir19/subdir9/blk_-9223372036824119008
> 08:16:21,214 INFO impl.FsDatasetAsyncDiskService
> (FsDatasetAsyncDiskService.java:run(333)) - Deleted
> BP-1606066499--1606188026755 blk_-9223372036824119006_220037616 URI
> file:/data4/hadoop/hdfs/data/current/BP-1606066499--1606188026755/current/finalized/subdir19/subdir9/blk_-9223372036824119006
> 08:16:55,737 INFO impl.FsDatasetAsyncDiskService
> (FsDatasetAsyncDiskService.java:run(333)) - Deleted
> BP-1606066499--1606188026755 blk_-9223372036824119005_220037616 URI
> file:/data2/hadoop/hdfs/data/current/BP-1606066499--1606188026755/current/finalized/subdir19/subdir9/blk_-9223372036824119005
> {code}
>
> The total number of internal blocks deleted during 08:15-08:17 are as follows
> ||internal block||index|| delete num||
> |blk_-9223372036824119008
> blk_-9223372036824119006
> blk_-9223372036824119005
> blk_-9223372036824119004
> blk_-9223372036824119003
> blk_-9223372036824119000 |0
> 2
> 3
> 4
> 5
> 8| 1
> 1
> 1
> 50
> 1
> 1|
>
> {color:#ff}During 08:15 to 08:17, we restarted 2 datanode and triggered
> full block report immediately.{color}
>
> There are 2 questions:
> 1. Why are there so many replicas of this block?
> 2. Why delete the internal block with only one copy?
> The reasons for the first problem may be as follows:
> 1. We set the full block report period of some datanode to 168 hours.
> 2. We have done a namenode HA operation.
> 3. After namenode HA, the state of storage became
> {color:#ff}stale{color}, and the state not change until next full block
> report.
> 4. The balancer copied the replica without deleting the replica from source
> node, because the source node have the stale storage, and the request was put
> into {color:#ff}postponedMisreplicatedBlocks{color}.
> 5. Balancer continues to copy the replica, eventually resulting in multiple
> copies of a replica
> !image-2022-01-10-17-31-35-910.png|width=642,height=269!
> The set of {color:#ff}rescannedMisreplicatedBlocks{color} have so many
> block to remove.
> !image-2022-01-10-17-32-56-981.png|width=745,height=124!
> As for the second question, we checked the code of
> {color:#de350b}processExtraRedundancyBlock{color}, but didn't find any
> problem.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13900) NameNode: Unable to trigger a roll of the active NN
liuhongtong created HDFS-13900: -- Summary: NameNode: Unable to trigger a roll of the active NN Key: HDFS-13900 URL: https://issues.apache.org/jira/browse/HDFS-13900 Project: Hadoop HDFS Issue Type: Bug Reporter: liuhongtong I have backport Multi-standby NNs to our own hdfs version. I found an issue of EditLog roll. h2. Reproducible Steps： h3. 1.original state nn1 active nn2 standby nn3 standby h3. 2. stop nn1 h3. 3. new state nn1 stopped nn2 active nn3 standby h3. 4. nn3 unable to trigger a roll of the active NN [2018-08-22T10:33:38.025+08:00] [WARN] namenode.ha.EditLogTailer.triggerActiveLogRoll(EditLogTailer.java 307) [Edit log tailer] : Unable to trigger a roll of the active NN java.net.ConnectException: Call From to failed on connection exception: java.net.ConnectException: Connection refused; For more details see:[http://wiki.apache.org/hadoop/ConnectionRefused] at sun.reflect.GeneratedConstructorAccessor17.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:782) at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:722) at org.apache.hadoop.ipc.Client.call(Client.java:1536) at org.apache.hadoop.ipc.Client.call(Client.java:1463) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:237) at com.sun.proxy.$Proxy16.rollEditLog(Unknown Source) at org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolTranslatorPB.rollEditLog(NamenodeProtocolTranslatorPB.java:148) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$2.doWork(EditLogTailer.java:301) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$2.doWork(EditLogTailer.java:298) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$MultipleNameNodeProxy.call(EditLogTailer.java:414) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer.triggerActiveLogRoll(EditLogTailer.java:304) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer.access$800(EditLogTailer.java:69) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.doWork(EditLogTailer.java:346) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.access$400(EditLogTailer.java:315) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread$1.run(EditLogTailer.java:332) at org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:415) at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.run(EditLogTailer.java:328) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206) at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:521) at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:485) at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:658) at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:756) at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:419) at org.apache.hadoop.ipc.Client.getConnection(Client.java:1585) at org.apache.hadoop.ipc.Client.call(Client.java:1502) ... 14 more -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuhongtong reassigned HDFS-13346:
--
Assignee: Yiqun Lin (was: liuhongtong)
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: Yiqun Lin
>Priority: Major
> Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch,
> HDFS-13346.003.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465579#comment-16465579
]
liuhongtong commented on HDFS-13346:
[~linyiqun] I am encountering compiling issues in latest source code and
failure in unit test.
I will be pleased to transfer this issue to you. Thanks.
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch,
> HDFS-13346.003.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-13530) NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
[
https://issues.apache.org/jira/browse/HDFS-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465516#comment-16465516
]
liuhongtong edited comment on HDFS-13530 at 5/7/18 6:58 AM:
{code:java}
[ERROR] TestWebHdfsTimeouts.testTwoStepWriteConnectTimeout:245 expected timeout
[ERROR] TestWebHdfsTimeouts.testTwoStepWriteConnectTimeout:245 expected timeout
[ERROR] Errors: [ERROR]
TestDataNodeVolumeFailureReporting.testVolFailureStatsPreservedOnNNRestart:283
? Timeout [INFO] [ERROR] Tests run: 5557, Failures: 10, Errors: 1, Skipped: 21
{code}
I'm innocent, and this unit test failure is irrelevant with the modified code.
was (Author: liuhongtong):
{code:java}
[ERROR] TestWebHdfsTimeouts.testTwoStepWriteConnectTimeout:245 expected timeout
[ERROR] TestWebHdfsTimeouts.testTwoStepWriteConnectTimeout:245 expected timeout
[ERROR] Errors: [ERROR]
TestDataNodeVolumeFailureReporting.testVolFailureStatsPreservedOnNNRestart:283
? Timeout [INFO] [ERROR] Tests run: 5557, Failures: 10, Errors: 1, Skipped: 21
{code}
I'm innocent, and this unit test failure is irrelevant with the modified code.
> NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
> --
>
> Key: HDFS-13530
> URL: https://issues.apache.org/jira/browse/HDFS-13530
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, namenode
>Reporter: liuhongtong
>Priority: Major
> Attachments: HDFS-13530.001.patch
>
>
> If the directory is nonexistent, getQuotaUsage rpc call will run into
> NullPointerException throwed by
> FSDirStatAndListingOp.getQuotaUsageInt() .
> I think FSDirStatAndListingOp.getQuotaUsageInt() should throw
> FileNotFoundException when the directory is nonexistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13530) NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
[
https://issues.apache.org/jira/browse/HDFS-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465516#comment-16465516
]
liuhongtong commented on HDFS-13530:
{code:java}
[ERROR] TestWebHdfsTimeouts.testTwoStepWriteConnectTimeout:245 expected timeout
[ERROR] TestWebHdfsTimeouts.testTwoStepWriteConnectTimeout:245 expected timeout
[ERROR] Errors: [ERROR]
TestDataNodeVolumeFailureReporting.testVolFailureStatsPreservedOnNNRestart:283
? Timeout [INFO] [ERROR] Tests run: 5557, Failures: 10, Errors: 1, Skipped: 21
{code}
I'm innocent, and this unit test failure is irrelevant with the modified code.
> NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
> --
>
> Key: HDFS-13530
> URL: https://issues.apache.org/jira/browse/HDFS-13530
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, namenode
>Reporter: liuhongtong
>Priority: Major
> Attachments: HDFS-13530.001.patch
>
>
> If the directory is nonexistent, getQuotaUsage rpc call will run into
> NullPointerException throwed by
> FSDirStatAndListingOp.getQuotaUsageInt() .
> I think FSDirStatAndListingOp.getQuotaUsageInt() should throw
> FileNotFoundException when the directory is nonexistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13531) RBF: RouterAdmin supports to set mount table readonly/readwrite
[ https://issues.apache.org/jira/browse/HDFS-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13531: --- Attachment: HDFS-13531.001.patch > RBF: RouterAdmin supports to set mount table readonly/readwrite > --- > > Key: HDFS-13531 > URL: https://issues.apache.org/jira/browse/HDFS-13531 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13531.001.patch > > > RouterAdmin only supports to set mount point read only. > If we want to reset the mount point read write, there is no way. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13531) RBF: RouterAdmin supports to set mount table readonly/readwrite
[ https://issues.apache.org/jira/browse/HDFS-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13531: --- Status: Patch Available (was: Open) > RBF: RouterAdmin supports to set mount table readonly/readwrite > --- > > Key: HDFS-13531 > URL: https://issues.apache.org/jira/browse/HDFS-13531 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13531.001.patch > > > RouterAdmin only supports to set mount point read only. > If we want to reset the mount point read write, there is no way. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13531) RBF: RouterAdmin supports to set mount table readonly/readwrite
liuhongtong created HDFS-13531: -- Summary: RBF: RouterAdmin supports to set mount table readonly/readwrite Key: HDFS-13531 URL: https://issues.apache.org/jira/browse/HDFS-13531 Project: Hadoop HDFS Issue Type: Improvement Reporter: liuhongtong RouterAdmin only supports to set mount point read only. If we want to reset the mount point read write, there is no way. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13530) NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
[ https://issues.apache.org/jira/browse/HDFS-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13530: --- Status: Patch Available (was: Open) > NameNode: Fix NullPointerException when getQuotaUsageInt() invoked > -- > > Key: HDFS-13530 > URL: https://issues.apache.org/jira/browse/HDFS-13530 > Project: Hadoop HDFS > Issue Type: Bug > Components: federation, namenode >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13530.001.patch > > > If the directory is nonexistent, getQuotaUsage rpc call will run into > NullPointerException throwed by > FSDirStatAndListingOp.getQuotaUsageInt() . > I think FSDirStatAndListingOp.getQuotaUsageInt() should throw > FileNotFoundException when the directory is nonexistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13530) NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
[ https://issues.apache.org/jira/browse/HDFS-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13530: --- Attachment: HDFS-13530.001.patch > NameNode: Fix NullPointerException when getQuotaUsageInt() invoked > -- > > Key: HDFS-13530 > URL: https://issues.apache.org/jira/browse/HDFS-13530 > Project: Hadoop HDFS > Issue Type: Bug > Components: federation, namenode >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13530.001.patch > > > If the directory is nonexistent, getQuotaUsage rpc call will run into > NullPointerException throwed by > FSDirStatAndListingOp.getQuotaUsageInt() . > I think FSDirStatAndListingOp.getQuotaUsageInt() should throw > FileNotFoundException when the directory is nonexistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13530) NameNode: Fix NullPointerException when getQuotaUsageInt() invoked
liuhongtong created HDFS-13530: -- Summary: NameNode: Fix NullPointerException when getQuotaUsageInt() invoked Key: HDFS-13530 URL: https://issues.apache.org/jira/browse/HDFS-13530 Project: Hadoop HDFS Issue Type: Bug Components: federation, namenode Reporter: liuhongtong If the directory is nonexistent, getQuotaUsage rpc call will run into NullPointerException throwed by FSDirStatAndListingOp.getQuotaUsageInt() . I think FSDirStatAndListingOp.getQuotaUsageInt() should throw FileNotFoundException when the directory is nonexistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuhongtong updated HDFS-13346:
---
Attachment: HDFS-13346.003.patch
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch,
> HDFS-13346.003.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429960#comment-16429960
]
liuhongtong commented on HDFS-13346:
Hi [~linyiqun], I am working on this issue.
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415229#comment-16415229
]
liuhongtong commented on HDFS-13346:
[~linyiqun] Thanks for your recommendation.
RouterAdminServer invokes this.rpcServer.setQuota to set Quota of Name Service
and then updates or adds MountTableEntry to State Store.
But I am worried about how to ensure consistency and atomicity between
different Routers.
RouterAdmin A sets nsQuota 200 | RouterAdmin B sets
nsQuota 300
| |
|
RouterAdminServer A set NS nsQuota 200 | |
| |
RouterAdminServer B set NS nsQuota 300
| |
RouterAdminServer B update State Store
RouterAdminServer A update State Store | |
Now Router nsQuota is 200, but Name Service nsQuota is 300.
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415061#comment-16415061 ] liuhongtong commented on HDFS-13204: Thanks [~elgoiri] [~ywskycn] [~tartarus] [~striver.wang] [~maobaolong] for the review and better comments. > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Fix For: 2.10.0, 2.9.1, 3.0.2, 3.2.0, 3.1.1 > > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, HDFS-13204.007.patch, HDFS-13204.008.patch, > Routers.png, Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png, > image-2018-03-23-18-06-54-354.png, image-2018-03-26-10-10-10-930.png, > image-2018-03-26-10-21-24-171.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.008.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, HDFS-13204.007.patch, HDFS-13204.008.patch, > Routers.png, Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png, > image-2018-03-23-18-06-54-354.png, image-2018-03-26-10-10-10-930.png, > image-2018-03-26-10-21-24-171.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413289#comment-16413289 ] liuhongtong commented on HDFS-13204: [~elgoiri] Thanks for your comments. The last line of federationhealth.js is not a blank line, so git diff just reminds us. [^HDFS-13204.008.patch] is available. \e033 of glyphicon-lock and \e013 of glyphicon-ok look nice. !image-2018-03-26-10-21-24-171.png! > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, HDFS-13204.007.patch, HDFS-13204.008.patch, > Routers.png, Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png, > image-2018-03-23-18-06-54-354.png, image-2018-03-26-10-10-10-930.png, > image-2018-03-26-10-21-24-171.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: image-2018-03-26-10-21-24-171.png > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, HDFS-13204.007.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png, image-2018-03-23-18-06-54-354.png, > image-2018-03-26-10-10-10-930.png, image-2018-03-26-10-21-24-171.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: image-2018-03-26-10-10-10-930.png > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, HDFS-13204.007.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png, image-2018-03-23-18-06-54-354.png, > image-2018-03-26-10-10-10-930.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuhongtong updated HDFS-13346:
---
Attachment: HDFS-13346.002.patch
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch, HDFS-13346.002.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuhongtong updated HDFS-13346:
---
Status: Patch Available (was: Open)
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
[
https://issues.apache.org/jira/browse/HDFS-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuhongtong updated HDFS-13346:
---
Attachment: HDFS-13346.001.patch
> RBF: Fix synchronization of router quota and ns quota
> -
>
> Key: HDFS-13346
> URL: https://issues.apache.org/jira/browse/HDFS-13346
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: liuhongtong
>Priority: Major
> Attachments: HDFS-13346.001.patch
>
>
> Check Router Quota and ns Quota:
> {code}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 150/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Update Router Quota:
> {code:java}
> $ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
> Successfully set quota for mount point /ns10t
> {code}
> Check Router Quota and ns Quota:
> {code:java}
> $ hdfs dfsrouteradmin -ls /ns10t
> Mount Table Entries:
> SourceDestinations Owner
> Group Mode Quota/Usage
> /ns10tns10->/ns10t hadp
> hadp rwxr-xr-x [NsQuota: 400/319,
> SsQuota: -/-]
> /ns10t/ns1mountpoint ns1->/a/tthadp
> hadp rwxr-xr-x [NsQuota: -/-, SsQuota:
> -/-]
> $ hdfs dfs -count -q hdfs://ns10/ns10t
> 150-155none inf3
> 302 0 hdfs://ns10/ns10t
> {code}
> Now Router Quota has updated successfully, but ns Quota not.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13346) RBF: Fix synchronization of router quota and ns quota
liuhongtong created HDFS-13346:
--
Summary: RBF: Fix synchronization of router quota and ns quota
Key: HDFS-13346
URL: https://issues.apache.org/jira/browse/HDFS-13346
Project: Hadoop HDFS
Issue Type: Bug
Reporter: liuhongtong
Check Router Quota and ns Quota:
{code}
$ hdfs dfsrouteradmin -ls /ns10t
Mount Table Entries:
SourceDestinations Owner
Group Mode Quota/Usage
/ns10tns10->/ns10t hadp
hadp rwxr-xr-x [NsQuota: 150/319, SsQuota:
-/-]
/ns10t/ns1mountpoint ns1->/a/tthadp
hadp rwxr-xr-x [NsQuota: -/-, SsQuota: -/-]
$ hdfs dfs -count -q hdfs://ns10/ns10t
150-155none inf3
302 0 hdfs://ns10/ns10t
{code}
Update Router Quota:
{code:java}
$ hdfs dfsrouteradmin -setQuota /ns10t -nsQuota 400
Successfully set quota for mount point /ns10t
{code}
Check Router Quota and ns Quota:
{code:java}
$ hdfs dfsrouteradmin -ls /ns10t
Mount Table Entries:
SourceDestinations Owner
Group Mode Quota/Usage
/ns10tns10->/ns10t hadp
hadp rwxr-xr-x [NsQuota: 400/319, SsQuota:
-/-]
/ns10t/ns1mountpoint ns1->/a/tthadp
hadp rwxr-xr-x [NsQuota: -/-, SsQuota: -/-]
$ hdfs dfs -count -q hdfs://ns10/ns10t
150-155none inf3
302 0 hdfs://ns10/ns10t
{code}
Now Router Quota has updated successfully, but ns Quota not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.007.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, HDFS-13204.007.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png, image-2018-03-23-18-06-54-354.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412878#comment-16412878 ] liuhongtong commented on HDFS-13204: [~elgoiri] Thx. I have modified rbf.css. > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png, image-2018-03-23-18-06-54-354.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.006.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > HDFS-13204.006.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png, image-2018-03-23-18-06-54-354.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411140#comment-16411140 ] liuhongtong commented on HDFS-13204: [~ywskycn] I have added two new css icon, which may not be very appropriate. The following screenshot is available. [~elgoiri] rbf.css has been created. Please have a look. !image-2018-03-23-18-06-54-354.png! > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > Routers.png, Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png, > image-2018-03-23-18-06-54-354.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: image-2018-03-23-18-06-54-354.png > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > Routers.png, Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png, > image-2018-03-23-18-06-54-354.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.005.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, HDFS-13204.005.patch, > Routers.png, Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.004.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, HDFS-13204.004.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407581#comment-16407581 ] liuhongtong commented on HDFS-13204: Waiting for new comments, I will be pleased to make this commit perfect. > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13195) DataNode conf page cannot display the current value after reconfig
[
https://issues.apache.org/jira/browse/HDFS-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407574#comment-16407574
]
liuhongtong commented on HDFS-13195:
I have tried [^HDFS-13195-branch-2.7.002.patch] and it works well.
> DataNode conf page cannot display the current value after reconfig
> ---
>
> Key: HDFS-13195
> URL: https://issues.apache.org/jira/browse/HDFS-13195
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
>Affects Versions: 2.7.1
>Reporter: maobaolong
>Assignee: maobaolong
>Priority: Minor
> Fix For: 2.7.1
>
> Attachments: HDFS-13195-branch-2.7.001.patch,
> HDFS-13195-branch-2.7.002.patch, HDFS-13195.001.patch, HDFS-13195.002.patch
>
>
> Now the branch-2.7 support dfs.datanode.data.dir reconfig, but after i
> reconfig this key, the conf page's value is still the old config value.
> The reason is that:
> {code:java}
> public DatanodeHttpServer(final Configuration conf,
> final DataNode datanode,
> final ServerSocketChannel externalHttpChannel)
> throws IOException {
> this.conf = conf;
> Configuration confForInfoServer = new Configuration(conf);
> confForInfoServer.setInt(HttpServer2.HTTP_MAX_THREADS, 10);
> HttpServer2.Builder builder = new HttpServer2.Builder()
> .setName("datanode")
> .setConf(confForInfoServer)
> .setACL(new AccessControlList(conf.get(DFS_ADMIN, " ")))
> .hostName(getHostnameForSpnegoPrincipal(confForInfoServer))
> .addEndpoint(URI.create("http://localhost:0;))
> .setFindPort(true);
> this.infoServer = builder.build();
> {code}
> The confForInfoServer is a new configuration instance, while the dfsadmin
> reconfig the datanode's config, the config result cannot reflect to
> confForInfoServer, so we should use the datanode's conf.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.003.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > HDFS-13204.003.patch, Routers.png, Subclusters.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406059#comment-16406059 ] liuhongtong commented on HDFS-13307: [~linyiqun] Thx. Updated. > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch, > HDFS-13307.003.patch, HDFS-13307.004.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Attachment: HDFS-13307.004.patch > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch, > HDFS-13307.003.patch, HDFS-13307.004.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-13307) RBF: Fix setQuota bug
[
https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406010#comment-16406010
]
liuhongtong edited comment on HDFS-13307 at 3/20/18 9:35 AM:
-
[~linyiqun]
If setQuota() throws Exception, run() will catch it, print out the error
message and return error return code -1. The following is just an example.
{code:java}
$ hdfs dfsrouteradmin -setQuota /test10 -nsQuota aaa --ssQuota 200
setQuota: Cannot parse nsQuota: aaa
Federation Admin Tools:
[-add[-readonly] -owner -group
-mode ]
[-rm ]
[-ls ]
[-setQuota -nsQuota -ssQuota ]
[-clrQuota ]
[-safemode enter | leave | get]
$ echo $?
255
{code}
If as your advice, setQuota() print error message and return false, but the
caller run() ignores false return and return 0.
If we want to deal with all false return from every command, not only
setQuota, we must modify all branches, while these are tedious.
{code:java}
..
if (setQuota(argv, i)) {
System.out.println(
"Successfully set quota for mount point " + argv[i]);
+ } else {
+ exitCode = -1;
}
} else if ("-clrQuota".equals(cmd)) {
if (clrQuota(argv[i])) {
System.out.println(
"Successfully clear quota for mount point " + argv[i]);
+ } else {
+ exitCode = -1;
}
} else if ("-safemode".equals(cmd)) {
manageSafeMode(argv[i]);
..
{code}
So I think throwing Exception may be more reasonable.
was (Author: liuhongtong):
[~linyiqun]
If setQuota() throws Exception, run() will catch it, print out the error
message and return error return code -1. The following is just an example.
```shell
$ hdfs dfsrouteradmin -setQuota /test10 -nsQuota aaa --ssQuota 200
setQuota: Cannot parse nsQuota: aaa
Federation Admin Tools:
[-add[-readonly] -owner
-group -mode ]
[-rm ]
[-ls ]
[-setQuota -nsQuota -ssQuota ]
[-clrQuota ]
[-safemode enter | leave | get]
$ echo $?
255
```
If as your advice, setQuota() print error message and return false, but the
caller run() ignores false return and return 0.
If we want to deal with all false return from every command, not only setQuota,
we must modify all branches, while these are tedious.
```java
..
} else if ("-setQuota".equals(cmd)) {
if (setQuota(argv, i)) {
System.out.println(
"Successfully set quota for mount point " + argv[i]);
+ } else {
+ exitCode = -1;
}
} else if ("-clrQuota".equals(cmd)) {
if (clrQuota(argv[i])) {
System.out.println(
"Successfully clear quota for mount point " + argv[i]);
+ } else {
+ exitCode = -1;
}
} else if ("-safemode".equals(cmd)) {
..
```
So I think throwing Exception may be more reasonable.
> RBF: Fix setQuota bug
> -
>
> Key: HDFS-13307
> URL: https://issues.apache.org/jira/browse/HDFS-13307
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: liuhongtong
>Priority: Major
> Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch,
> HDFS-13307.003.patch
>
>
> If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the
> another one will be cleared.
> The following is the step:
> 1. set /test1 -nsQuota 400 -ssQuota 200
> hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200
> Successfully set quota for mount point /test1
> 2. after a moment, list /test1, everything is ok.
> hdfs dfsrouteradmin -ls /test1
> SourceDestinations Owner
> Group Mode Quota/Usage
> /test1ns1->/test1 hadp
> hadp rwxr-xr-x [NsQuota: 400/0, SsQuota:
> 200 B/0 B]
> 3. only set /test1 -nsQuota 600
> hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600
> Successfully set quota for mount point /test1
> 4. after a moment, list /test1, now ssQuota has been cleared.
> hdfs dfsrouteradmin -ls /test1
> SourceDestinations Owner
> Group Mode Quota/Usage
> /test1ns1->/test1 hadp
> hadp rwxr-xr-x [NsQuota: 600/0, SsQuota:
> -/-]
> [^HDFS-13307.001.patch]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13307) RBF: Fix setQuota bug
[
https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406010#comment-16406010
]
liuhongtong commented on HDFS-13307:
[~linyiqun]
If setQuota() throws Exception, run() will catch it, print out the error
message and return error return code -1. The following is just an example.
```shell
$ hdfs dfsrouteradmin -setQuota /test10 -nsQuota aaa --ssQuota 200
setQuota: Cannot parse nsQuota: aaa
Federation Admin Tools:
[-add[-readonly] -owner
-group -mode ]
[-rm ]
[-ls ]
[-setQuota -nsQuota -ssQuota ]
[-clrQuota ]
[-safemode enter | leave | get]
$ echo $?
255
```
If as your advice, setQuota() print error message and return false, but the
caller run() ignores false return and return 0.
If we want to deal with all false return from every command, not only setQuota,
we must modify all branches, while these are tedious.
```java
..
} else if ("-setQuota".equals(cmd)) {
if (setQuota(argv, i)) {
System.out.println(
"Successfully set quota for mount point " + argv[i]);
+ } else {
+ exitCode = -1;
}
} else if ("-clrQuota".equals(cmd)) {
if (clrQuota(argv[i])) {
System.out.println(
"Successfully clear quota for mount point " + argv[i]);
+ } else {
+ exitCode = -1;
}
} else if ("-safemode".equals(cmd)) {
..
```
So I think throwing Exception may be more reasonable.
> RBF: Fix setQuota bug
> -
>
> Key: HDFS-13307
> URL: https://issues.apache.org/jira/browse/HDFS-13307
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: liuhongtong
>Assignee: liuhongtong
>Priority: Major
> Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch,
> HDFS-13307.003.patch
>
>
> If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the
> another one will be cleared.
> The following is the step:
> 1. set /test1 -nsQuota 400 -ssQuota 200
> hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200
> Successfully set quota for mount point /test1
> 2. after a moment, list /test1, everything is ok.
> hdfs dfsrouteradmin -ls /test1
> SourceDestinations Owner
> Group Mode Quota/Usage
> /test1ns1->/test1 hadp
> hadp rwxr-xr-x [NsQuota: 400/0, SsQuota:
> 200 B/0 B]
> 3. only set /test1 -nsQuota 600
> hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600
> Successfully set quota for mount point /test1
> 4. after a moment, list /test1, now ssQuota has been cleared.
> hdfs dfsrouteradmin -ls /test1
> SourceDestinations Owner
> Group Mode Quota/Usage
> /test1ns1->/test1 hadp
> hadp rwxr-xr-x [NsQuota: 600/0, SsQuota:
> -/-]
> [^HDFS-13307.001.patch]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Attachment: HDFS-13307.003.patch > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch, > HDFS-13307.003.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405868#comment-16405868 ] liuhongtong commented on HDFS-13204: [~elgoiri] I have attached new screenshots. !Subclusters.png! !Routers.png! > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, Routers.png, > Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: Routers.png > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, Routers.png, > Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: Subclusters.png > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > Subclusters.png, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405857#comment-16405857 ] liuhongtong edited comment on HDFS-13307 at 3/20/18 6:14 AM: - [~linyiqun] Follow your advice, I have updated patch. [~ajayydv] There is no need to add new test case, since TestRouterAdminCLI#testSetAndClearQuota is very appropriate. was (Author: liuhongtong): [~linyiqun] Follow your advice, I have update patch. [~ajayydv] There is no need to add new test case, since TestRouterAdminCLI#testSetAndClearQuota is very appropriate. > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405857#comment-16405857 ] liuhongtong commented on HDFS-13307: [~linyiqun] Follow your advice, I have update patch. [~ajayydv] There is no need to add new test case, since TestRouterAdminCLI#testSetAndClearQuota is very appropriate. > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Attachment: HDFS-13307.002.patch > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch, HDFS-13307.002.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13308) RBF: Optimize setQuota error output
[ https://issues.apache.org/jira/browse/HDFS-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13308: --- Attachment: HDFS-13308.001.patch > RBF: Optimize setQuota error output > --- > > Key: HDFS-13308 > URL: https://issues.apache.org/jira/browse/HDFS-13308 > Project: Hadoop HDFS > Issue Type: Wish >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13308.001.patch > > > If hdfs dfsrouteradmin -setQuota specifies a nonexistent path in mount table, > there is any error prompt message. > I think we should print error prompt message like: > hdfs dfsrouteradmin -setQuota /test -nsQuota 400 --ssQuota 200 > /test not exist in mount table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13308) RBF: Optimize setQuota error output
[ https://issues.apache.org/jira/browse/HDFS-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13308: --- Status: Patch Available (was: Open) > RBF: Optimize setQuota error output > --- > > Key: HDFS-13308 > URL: https://issues.apache.org/jira/browse/HDFS-13308 > Project: Hadoop HDFS > Issue Type: Wish >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13308.001.patch > > > If hdfs dfsrouteradmin -setQuota specifies a nonexistent path in mount table, > there is any error prompt message. > I think we should print error prompt message like: > hdfs dfsrouteradmin -setQuota /test -nsQuota 400 --ssQuota 200 > /test not exist in mount table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13308) RBF: Optimize setQuota error output
liuhongtong created HDFS-13308: -- Summary: RBF: Optimize setQuota error output Key: HDFS-13308 URL: https://issues.apache.org/jira/browse/HDFS-13308 Project: Hadoop HDFS Issue Type: Wish Reporter: liuhongtong If hdfs dfsrouteradmin -setQuota specifies a nonexistent path in mount table, there is any error prompt message. I think we should print error prompt message like: hdfs dfsrouteradmin -setQuota /test -nsQuota 400 --ssQuota 200 /test not exist in mount table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404045#comment-16404045 ] liuhongtong commented on HDFS-13307: According to current design, hdfs dfsrouteradmin -setQuota must specify both of -nsQuota and -ssQuota, but there is no limitation to specify only one of them, which is a misusage. > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Description: If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the another one will be cleared. The following is the step: 1. set /test1 -nsQuota 400 -ssQuota 200 hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 Successfully set quota for mount point /test1 2. after a moment, list /test1, everything is ok. hdfs dfsrouteradmin -ls /test1 SourceDestinations Owner Group Mode Quota/Usage /test1ns1->/test1 hadp hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: 200 B/0 B] 3. only set /test1 -nsQuota 600 hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 Successfully set quota for mount point /test1 4. after a moment, list /test1, now ssQuota has been cleared. hdfs dfsrouteradmin -ls /test1 SourceDestinations Owner Group Mode Quota/Usage /test1ns1->/test1 hadp hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: -/-] [^HDFS-13307.001.patch] was: If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the another one will be cleared. The following is the step: 1. set /test1 -nsQuota 400 -ssQuota 200 hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 Successfully set quota for mount point /test1 2. after a moment, list /test1, everything is ok. hdfs dfsrouteradmin -ls /test1 SourceDestinations Owner Group Mode Quota/Usage /test1ns1->/test1 hadp hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: 200 B/0 B] 3. only set /test1 -nsQuota 600 hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 Successfully set quota for mount point /test1 4. after a moment, list /test1, now ssQuota has been cleared. hdfs dfsrouteradmin -ls /test1 SourceDestinations Owner Group Mode Quota/Usage /test1ns1->/test1 hadp hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: -/-] > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] > [^HDFS-13307.001.patch] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404042#comment-16404042 ] liuhongtong commented on HDFS-13307: [^HDFS-13307.001.patch] > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: liuhongtong >Priority: Major > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Status: Patch Available (was: Open) > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Issue Comment Deleted] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Comment: was deleted (was: [^HDFS-13307.001.patch] ) > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13307) RBF: Fix setQuota bug
[ https://issues.apache.org/jira/browse/HDFS-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13307: --- Attachment: HDFS-13307.001.patch > RBF: Fix setQuota bug > - > > Key: HDFS-13307 > URL: https://issues.apache.org/jira/browse/HDFS-13307 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: liuhongtong >Priority: Major > Attachments: HDFS-13307.001.patch > > > If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the > another one will be cleared. > The following is the step: > 1. set /test1 -nsQuota 400 -ssQuota 200 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 > Successfully set quota for mount point /test1 > 2. after a moment, list /test1, everything is ok. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: > 200 B/0 B] > 3. only set /test1 -nsQuota 600 > hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 > Successfully set quota for mount point /test1 > 4. after a moment, list /test1, now ssQuota has been cleared. > hdfs dfsrouteradmin -ls /test1 > SourceDestinations Owner > Group Mode Quota/Usage > /test1ns1->/test1 hadp > hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: > -/-] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13307) RBF: Fix setQuota bug
liuhongtong created HDFS-13307: -- Summary: RBF: Fix setQuota bug Key: HDFS-13307 URL: https://issues.apache.org/jira/browse/HDFS-13307 Project: Hadoop HDFS Issue Type: Bug Reporter: liuhongtong If hdfs dfsrouteradmin -setQuota only set one of -nsQuota and -ssQuota, the another one will be cleared. The following is the step: 1. set /test1 -nsQuota 400 -ssQuota 200 hdfs dfsrouteradmin -setQuota /test1 -nsQuota 400 -ssQuota 200 Successfully set quota for mount point /test1 2. after a moment, list /test1, everything is ok. hdfs dfsrouteradmin -ls /test1 SourceDestinations Owner Group Mode Quota/Usage /test1ns1->/test1 hadp hadp rwxr-xr-x [NsQuota: 400/0, SsQuota: 200 B/0 B] 3. only set /test1 -nsQuota 600 hdfs dfsrouteradmin -setQuota /test1 -nsQuota 600 Successfully set quota for mount point /test1 4. after a moment, list /test1, now ssQuota has been cleared. hdfs dfsrouteradmin -ls /test1 SourceDestinations Owner Group Mode Quota/Usage /test1ns1->/test1 hadp hadp rwxr-xr-x [NsQuota: 600/0, SsQuota: -/-] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.002.patch > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404035#comment-16404035 ] liuhongtong commented on HDFS-13204: What a busy week. Sorry for waiting me a long time. I have updated the patch. Please take a look. [^HDFS-13204.002.patch] > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Assignee: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, HDFS-13204.002.patch, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13204) RBF: Optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385537#comment-16385537 ] liuhongtong commented on HDFS-13204: [~elgoiri] i guess [~maobaolong] means rbf should own private css named by federationdfshealth-router-*. > RBF: Optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Status: Patch Available (was: Open) > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: HDFS-13204.001.patch > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: HDFS-13204.001.patch, image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Description: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-33-09-972.png! The safe mode icon of Routers: !image-2018-02-28-18-33-47-661.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the safe mode icon in Subclusters should be modified, which may be more reasonable. !image-2018-02-28-18-35-35-708.png! was: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-33-09-972.png! The safe mode icon of Routers: !image-2018-02-28-18-33-47-661.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the safe mode icon in Subclusters should be modify, which may be more reasonable. !image-2018-02-28-18-35-35-708.png! > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modified, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Description: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-33-09-972.png! The safe mode icon of Routers: !image-2018-02-28-18-33-47-661.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the safe mode icon in Subclusters should be modify, which may be more reasonable. !image-2018-02-28-18-35-35-708.png! was: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-33-09-972.png! The safe mode icon of Routers: !image-2018-02-28-18-33-47-661.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the icon below may be more reasonable. !image-2018-02-28-18-35-35-708.png! > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the safe mode icon in Subclusters should be modify, > which may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: (was: image-2018-02-28-18-23-23-909.png) > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-33-09-972.png, > image-2018-02-28-18-33-47-661.png, image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: (was: image-2018-02-28-17-46-35-127.png) > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-23-23-909.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: (was: image-2018-02-28-17-47-44-156.png) > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-23-23-909.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: (was: image-2018-02-28-17-51-33-913.png) > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-23-23-909.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: image-2018-02-28-18-33-09-972.png image-2018-02-28-18-33-47-661.png image-2018-02-28-18-35-35-708.png Description: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-33-09-972.png! The safe mode icon of Routers: !image-2018-02-28-18-33-47-661.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the icon below may be more reasonable. !image-2018-02-28-18-35-35-708.png! was: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-22-51-975.png! The safe mode icon of Routers: !image-2018-02-28-18-23-23-909.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the icon below may be more reasonable. !image-2018-02-28-17-46-35-127.png! > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-18-23-23-909.png, > image-2018-02-28-18-33-09-972.png, image-2018-02-28-18-33-47-661.png, > image-2018-02-28-18-35-35-708.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-33-09-972.png! > The safe mode icon of Routers: > !image-2018-02-28-18-33-47-661.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-18-35-35-708.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Attachment: image-2018-02-28-18-23-23-909.png Description: In federation health webpage, the safe mode icons of Subclusters and Routers are inconsistent. The safe mode icon of Subclusters may induce users the name service is maintaining. !image-2018-02-28-18-22-51-975.png! The safe mode icon of Routers: !image-2018-02-28-18-23-23-909.png! In fact, if the name service is in safe mode, users can't do writing related operations. So I think the icon below may be more reasonable. !image-2018-02-28-17-46-35-127.png! was: In federationhealth webpage，the safe mode icon in the picture below may induce users the name service is maintaining. !image-2018-02-28-17-51-33-913.png! In fact, if the name service is in safe mode, users can't do most of operations. So I think the icon below may be more reasonable. !image-2018-02-28-17-46-35-127.png! > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-17-46-35-127.png, > image-2018-02-28-17-47-44-156.png, image-2018-02-28-17-51-33-913.png, > image-2018-02-28-18-23-23-909.png > > > In federation health webpage, the safe mode icons of Subclusters and Routers > are inconsistent. > The safe mode icon of Subclusters may induce users the name service is > maintaining. > !image-2018-02-28-18-22-51-975.png! > The safe mode icon of Routers: > !image-2018-02-28-18-23-23-909.png! > In fact, if the name service is in safe mode, users can't do writing related > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-17-46-35-127.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-13204) RBF: optimize name service safe mode icon
[ https://issues.apache.org/jira/browse/HDFS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuhongtong updated HDFS-13204: --- Issue Type: Sub-task (was: Wish) Parent: HDFS-12615 > RBF: optimize name service safe mode icon > - > > Key: HDFS-13204 > URL: https://issues.apache.org/jira/browse/HDFS-13204 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: liuhongtong >Priority: Minor > Attachments: image-2018-02-28-17-46-35-127.png, > image-2018-02-28-17-47-44-156.png, image-2018-02-28-17-51-33-913.png > > > In federationhealth webpage，the safe mode icon in the picture below may > induce users the name service is maintaining. > !image-2018-02-28-17-51-33-913.png! > In fact, if the name service is in safe mode, users can't do most of > operations. So I think the icon below may be more reasonable. > !image-2018-02-28-17-46-35-127.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-13204) RBF: optimize name service safe mode icon
liuhongtong created HDFS-13204: -- Summary: RBF: optimize name service safe mode icon Key: HDFS-13204 URL: https://issues.apache.org/jira/browse/HDFS-13204 Project: Hadoop HDFS Issue Type: Wish Reporter: liuhongtong Attachments: image-2018-02-28-17-46-35-127.png, image-2018-02-28-17-47-44-156.png, image-2018-02-28-17-51-33-913.png In federationhealth webpage，the safe mode icon in the picture below may induce users the name service is maintaining. !image-2018-02-28-17-51-33-913.png! In fact, if the name service is in safe mode, users can't do most of operations. So I think the icon below may be more reasonable. !image-2018-02-28-17-46-35-127.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
