[jira] [Updated] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15277: - Description: In HDFS-15239, a new button can click to parent folder is add. However, if the path is not formatted perfectly, it will not get the real parent. Path like follows are supported to get the file list in explorer.html, but they do not get the correct parent: /a/b/c/ parent will get /a/b/c now which should be /a/b /a/b//c parent's parent will get /a/b now which should be /a Otherwise, if current path is / or // or ///. The parent button should be unabled as it has no parent. was: In HDFS-15239, a new button can click to parent folder is add. However, if the path is not formatted perfectly, it will not get the real parent. Path like follows are supported to get the file list in explorer.html, but they do not get the correct parent: /a/b/c/ parent will get /a/b/c now which should be /a/b /a/b//c parent's parent will get /a/b/ now which should be /a Otherwise, if current path is / or // or ///. The parent button should be unabled as it has no parent. > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Fix For: 3.4.0 > > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ parent will get /a/b/c now which should be /a/b > /a/b//c parent's parent will get /a/b now which should be /a > > Otherwise, if current path is / or // or ///. The parent button should be > unabled as it has no parent. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083075#comment-17083075 ] Jianfei Jiang commented on HDFS-15277: -- [~elgoiri] please have a look. Thank you > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ parent will get /a/b/c now which should be /a/b > /a/b//c parent's parent will get /a/b/ now which should be /a > > Otherwise, if current path is / or // or ///. The parent button should be > unabled as it has no parent. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15277: - Description: In HDFS-15239, a new button can click to parent folder is add. However, if the path is not formatted perfectly, it will not get the real parent. Path like follows are supported to get the file list in explorer.html, but they do not get the correct parent: /a/b/c/ parent will get /a/b/c now which should be /a/b /a/b//c parent's parent will get /a/b/ now which should be /a Otherwise, if current path is / or // or ///. The parent button should be unabled as it has no parent. was: In HDFS-15239, a new button can click to parent folder is add. However, if the path is not formatted perfectly, it will not get the real parent. Path like follows are supported to get the file list in explorer.html, but they do not get the correct parent: /a/b/c/ will get /a/b/c now /a/bc > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ parent will get /a/b/c now which should be /a/b > /a/b//c parent's parent will get /a/b/ now which should be /a > > Otherwise, if current path is / or // or ///. The parent button should be > unabled as it has no parent. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15277: - Attachment: HDFS-15277_001.patch > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ will get /a/b/c now > /a/bc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15277: - Attachment: (was: HDFS-15277_001.patch) > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ will get /a/b/c now > /a/bc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work started] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-15277 started by Jianfei Jiang. > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ will get /a/b/c now > /a/bc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15277: - Status: Patch Available (was: In Progress) > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ will get /a/b/c now > /a/bc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15277) Parent directory in the explorer does not support all path formats
[ https://issues.apache.org/jira/browse/HDFS-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15277: - Attachment: HDFS-15277_001.patch > Parent directory in the explorer does not support all path formats > -- > > Key: HDFS-15277 > URL: https://issues.apache.org/jira/browse/HDFS-15277 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-15277_001.patch > > > In HDFS-15239, a new button can click to parent folder is add. However, if > the path is not formatted perfectly, it will not get the real parent. > Path like follows are supported to get the file list in explorer.html, but > they do not get the correct parent: > /a/b/c/ will get /a/b/c now > /a/bc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-15277) Parent directory in the explorer does not support all path formats
Jianfei Jiang created HDFS-15277: Summary: Parent directory in the explorer does not support all path formats Key: HDFS-15277 URL: https://issues.apache.org/jira/browse/HDFS-15277 Project: Hadoop HDFS Issue Type: Improvement Reporter: Jianfei Jiang Assignee: Jianfei Jiang In HDFS-15239, a new button can click to parent folder is add. However, if the path is not formatted perfectly, it will not get the real parent. Path like follows are supported to get the file list in explorer.html, but they do not get the correct parent: /a/b/c/ will get /a/b/c now /a/bc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071912#comment-17071912
]
Jianfei Jiang commented on HDFS-15251:
--
I found the new zk state when we update zk dependency of our own HBASE to 3.5,
some commands throw or log the unknown state. meanwhile the dependency of HBASE
in community has not updated yet. So I check the hdfs code and find this issue.
I am not sure the the closed state should act like disconnect or expired. So I
add two patches and i am puzzled. when zkfc will close the connection actively.
If only the moment of graceful shutdown(i will build 3.3.0-snapshot version to
make sure if it actually do close at the shutdown) close
the connection, it may be unnecessary to rejoin a election as its target is
just to shutdown.
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251.002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Status: In Progress (was: Patch Available)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251.002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Status: Patch Available (was: In Progress)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251.002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Attachment: (was: HDFS-15251_002.patch)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251.002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Attachment: HDFS-15251.002.patch
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251.002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Status: Patch Available (was: In Progress)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251_002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Status: In Progress (was: Patch Available)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251_002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Attachment: HDFS-15251_002.patch
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch, HDFS-15251_002.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Comment: was deleted
(was: oops, it may be a issue with prefix of hadoop but not hdfs.)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071486#comment-17071486
]
Jianfei Jiang commented on HDFS-15251:
--
oops, it may be a issue with prefix of hadoop but not hdfs.
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071422#comment-17071422
]
Jianfei Jiang commented on HDFS-15251:
--
Thank you [~weichiu], yes it only affect unreleased 3.3.0, change the version
is absolutely correct.
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.3.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Attachment: HDFS-15251.001.patch
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang reassigned HDFS-15251:
Assignee: Jianfei Jiang
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work started] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HDFS-15251 started by Jianfei Jiang.
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
[
https://issues.apache.org/jira/browse/HDFS-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-15251:
-
Status: Patch Available (was: In Progress)
> Add new zookeeper event type case after zk updated to 3.5.x
> ---
>
> Key: HDFS-15251
> URL: https://issues.apache.org/jira/browse/HDFS-15251
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15251.001.patch
>
>
> In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add
> Close case to the swich as it is not an unexpected Zookeeper watch event
> state.
> {code:java}
> /** @deprecated */
> @Deprecated
> Unknown(-1),
> Disconnected(0),
> /** @deprecated */
> @Deprecated
> NoSyncConnected(1),
> SyncConnected(3),
> AuthFailed(4),
> ConnectedReadOnly(5),
> SaslAuthenticated(6),
> Expired(-112),
> Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-15251) Add new zookeeper event type case after zk updated to 3.5.x
Jianfei Jiang created HDFS-15251:
Summary: Add new zookeeper event type case after zk updated to
3.5.x
Key: HDFS-15251
URL: https://issues.apache.org/jira/browse/HDFS-15251
Project: Hadoop HDFS
Issue Type: Improvement
Components: hdfs
Affects Versions: 3.2.1
Reporter: Jianfei Jiang
In zookeeper 3.5.x, KeeperState add a new one named Closed, so should add Close
case to the swich as it is not an unexpected Zookeeper watch event state.
{code:java}
/** @deprecated */
@Deprecated
Unknown(-1),
Disconnected(0),
/** @deprecated */
@Deprecated
NoSyncConnected(1),
SyncConnected(3),
AuthFailed(4),
ConnectedReadOnly(5),
SaslAuthenticated(6),
Expired(-112),
Closed(7);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070170#comment-17070170 ] Jianfei Jiang commented on HDFS-15245: -- Thank you [~elgoiri] for your advice, I updated the javadoc to the new methods and uploaded a new patch. > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, HDFS-15245.006.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: In Progress (was: Patch Available) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, HDFS-15245.006.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: Patch Available (was: In Progress) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, HDFS-15245.006.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: HDFS-15245.006.patch > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, HDFS-15245.006.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: HDFS-15245.005.patch > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: In Progress (was: Patch Available) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: Patch Available (was: In Progress) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, HDFS-15245.005.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Release Note: (was: fix the failed new testcase, asflicense seems not related.) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: In Progress (was: Patch Available) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: HDFS-15245.004.patch > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: Patch Available (was: In Progress) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, > HDFS-15245.004.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069201#comment-17069201 ] Jianfei Jiang commented on HDFS-15245: -- Thank you [~elgoiri]. Yes the journalnode maybe used by more than more cluster. I forget it as I never use as this. Update a new patch to change String getClusterId() to List getClusterIds() and also solve some checkstyle problem. > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Release Note: fix the failed new testcase, asflicense seems not related. Status: Patch Available (was: In Progress) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: In Progress (was: Patch Available) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: HDFS-15245.003.patch > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, HDFS-15245.003.patch, jn web > 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-15245) Improve JournalNode web UI
[
https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068406#comment-17068406
]
Jianfei Jiang edited comment on HDFS-15245 at 3/27/20, 8:17 AM:
Thanks [~weichiu] and [~ayushtkn] for code review.
The RpcDetailedActivity statistics in jmx are some detail infomation. I wonder
whether it is proper to add to the main page. As a comparison, nn and dn seem
not have such detailed infomation at the home page. Hope you can give some
advice.
{
"name" : "Hadoop:service=JournalNode,name=RpcDetailedActivityForPort8485",
"modelerType" : "RpcDetailedActivityForPort8485",
"tag.port" : "8485",
"tag.Context" : "rpcdetailed",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"StartLogSegmentNumOps" : 67,
"StartLogSegmentAvgTime" : 6.6716417910447765,
"FinalizeLogSegmentNumOps" : 66,
"FinalizeLogSegmentAvgTime" : 1.5606060606060606,
"JournalNumOps" : 133,
"JournalAvgTime" : 0.15789473684210525,
"GetEditLogManifestNumOps" : 139,
"GetEditLogManifestAvgTime" : 3.1510791366906474,
"GetEditLogManifestFromJournalNumOps" : 68,
"GetEditLogManifestFromJournalAvgTime" : 0.8823529411764706,
"JournalOutOfSyncExceptionNumOps" : 1,
"JournalOutOfSyncExceptionAvgTime" : 13.0
}
{
"name" : "Hadoop:service=JournalNode,name=RpcActivityForPort8485",
"modelerType" : "RpcActivityForPort8485",
"tag.port" : "8485",
"tag.serverName" : "QJournalProtocolService",
"tag.Context" : "rpc",
"tag.NumOpenConnectionsPerUser" : "{}",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"ReceivedBytes" : 106302,
"SentBytes" : 76209,
"RpcQueueTimeNumOps" : 474,
"RpcQueueTimeAvgTime" : 0.0,
"RpcLockWaitTimeNumOps" : 474,
"RpcLockWaitTimeAvgTime" : 0.0,
"RpcProcessingTimeNumOps" : 474,
"RpcProcessingTimeAvgTime" : 2.282700421940928,
"DeferredRpcProcessingTimeNumOps" : 0,
"DeferredRpcProcessingTimeAvgTime" : 0.0,
"RpcAuthenticationFailures" : 0,
"RpcAuthenticationSuccesses" : 0,
"RpcAuthorizationFailures" : 0,
"RpcAuthorizationSuccesses" : 270,
"RpcClientBackoff" : 0,
"RpcSlowCalls" : 0,
"NumOpenConnections" : 0,
"CallQueueLength" : 0,
"NumDroppedConnections" : 0
}
was (Author: jiangjianfei):
Thanks [~weichiu] and [~ayushtkn] for code review.
The RpcDetailedActivity statistics in jmx are some detail infomation. I wonder
whether it is proper to add to the main page. As a comparison, nn and dn seem
not have such detailed infomation at the home page. Hope you can give some
advice.
{
"name" : "Hadoop:service=JournalNode,name=RpcDetailedActivityForPort8485",
"modelerType" : "RpcDetailedActivityForPort8485",
"tag.port" : "8485",
"tag.Context" : "rpcdetailed",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"StartLogSegmentNumOps" : 67,
"StartLogSegmentAvgTime" : 6.6716417910447765,
"FinalizeLogSegmentNumOps" : 66,
"FinalizeLogSegmentAvgTime" : 1.5606060606060606,
"JournalNumOps" : 133,
"JournalAvgTime" : 0.15789473684210525,
"GetEditLogManifestNumOps" : 139,
"GetEditLogManifestAvgTime" : 3.1510791366906474,
"GetEditLogManifestFromJournalNumOps" : 68,
"GetEditLogManifestFromJournalAvgTime" : 0.8823529411764706,
"JournalOutOfSyncExceptionNumOps" : 1,
"JournalOutOfSyncExceptionAvgTime" : 13.0
}, {
"name" : "Hadoop:service=JournalNode,name=RpcActivityForPort8485",
"modelerType" : "RpcActivityForPort8485",
"tag.port" : "8485",
"tag.serverName" : "QJournalProtocolService",
"tag.Context" : "rpc",
"tag.NumOpenConnectionsPerUser" : "{}",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"ReceivedBytes" : 106302,
"SentBytes" : 76209,
"RpcQueueTimeNumOps" : 474,
"RpcQueueTimeAvgTime" : 0.0,
"RpcLockWaitTimeNumOps" : 474,
"RpcLockWaitTimeAvgTime" : 0.0,
"RpcProcessingTimeNumOps" : 474,
"RpcProcessingTimeAvgTime" : 2.282700421940928,
"DeferredRpcProcessingTimeNumOps" : 0,
"DeferredRpcProcessingTimeAvgTime" : 0.0,
"RpcAuthenticationFailures" : 0,
"RpcAuthenticationSuccesses" : 0,
"RpcAuthorizationFailures" : 0,
"RpcAuthorizationSuccesses" : 270,
"RpcClientBackoff" : 0,
"RpcSlowCalls" : 0,
"NumOpenConnections" : 0,
"CallQueueLength" : 0,
"NumDroppedConnections" : 0
}
> Improve JournalNode web UI
> --
>
> Key: HDFS-15245
> URL: https://issues.apache.org/jira/browse/HDFS-15245
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node, ui
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15245.002.patch, jn web 1.PNG, jn web 2.PNG
>
>
> At present, journalnode web UI is a almost blank page. It almost has no
> useful infomation.
> # Add some infomation of journalnode at the main page.
> # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level,
> Metrics, Configuration & Process Thread Dump
>
--
This message was
[jira] [Commented] (HDFS-15245) Improve JournalNode web UI
[
https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068406#comment-17068406
]
Jianfei Jiang commented on HDFS-15245:
--
Thanks [~weichiu] and [~ayushtkn] for code review.
The RpcDetailedActivity statistics in jmx are some detail infomation. I wonder
whether it is proper to add to the main page. As a comparison, nn and dn seem
not have such detailed infomation at the home page. Hope you can give some
advice.
{
"name" : "Hadoop:service=JournalNode,name=RpcDetailedActivityForPort8485",
"modelerType" : "RpcDetailedActivityForPort8485",
"tag.port" : "8485",
"tag.Context" : "rpcdetailed",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"StartLogSegmentNumOps" : 67,
"StartLogSegmentAvgTime" : 6.6716417910447765,
"FinalizeLogSegmentNumOps" : 66,
"FinalizeLogSegmentAvgTime" : 1.5606060606060606,
"JournalNumOps" : 133,
"JournalAvgTime" : 0.15789473684210525,
"GetEditLogManifestNumOps" : 139,
"GetEditLogManifestAvgTime" : 3.1510791366906474,
"GetEditLogManifestFromJournalNumOps" : 68,
"GetEditLogManifestFromJournalAvgTime" : 0.8823529411764706,
"JournalOutOfSyncExceptionNumOps" : 1,
"JournalOutOfSyncExceptionAvgTime" : 13.0
}, {
"name" : "Hadoop:service=JournalNode,name=RpcActivityForPort8485",
"modelerType" : "RpcActivityForPort8485",
"tag.port" : "8485",
"tag.serverName" : "QJournalProtocolService",
"tag.Context" : "rpc",
"tag.NumOpenConnectionsPerUser" : "{}",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"ReceivedBytes" : 106302,
"SentBytes" : 76209,
"RpcQueueTimeNumOps" : 474,
"RpcQueueTimeAvgTime" : 0.0,
"RpcLockWaitTimeNumOps" : 474,
"RpcLockWaitTimeAvgTime" : 0.0,
"RpcProcessingTimeNumOps" : 474,
"RpcProcessingTimeAvgTime" : 2.282700421940928,
"DeferredRpcProcessingTimeNumOps" : 0,
"DeferredRpcProcessingTimeAvgTime" : 0.0,
"RpcAuthenticationFailures" : 0,
"RpcAuthenticationSuccesses" : 0,
"RpcAuthorizationFailures" : 0,
"RpcAuthorizationSuccesses" : 270,
"RpcClientBackoff" : 0,
"RpcSlowCalls" : 0,
"NumOpenConnections" : 0,
"CallQueueLength" : 0,
"NumDroppedConnections" : 0
}
> Improve JournalNode web UI
> --
>
> Key: HDFS-15245
> URL: https://issues.apache.org/jira/browse/HDFS-15245
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node, ui
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15245.002.patch, jn web 1.PNG, jn web 2.PNG
>
>
> At present, journalnode web UI is a almost blank page. It almost has no
> useful infomation.
> # Add some infomation of journalnode at the main page.
> # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level,
> Metrics, Configuration & Process Thread Dump
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-15245) Improve JournalNode web UI
[
https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068406#comment-17068406
]
Jianfei Jiang edited comment on HDFS-15245 at 3/27/20, 8:16 AM:
Thanks [~weichiu] and [~ayushtkn] for code review.
The RpcDetailedActivity statistics in jmx are some detail infomation. I wonder
whether it is proper to add to the main page. As a comparison, nn and dn seem
not have such detailed infomation at the home page. Hope you can give some
advice.
{
"name" : "Hadoop:service=JournalNode,name=RpcDetailedActivityForPort8485",
"modelerType" : "RpcDetailedActivityForPort8485",
"tag.port" : "8485",
"tag.Context" : "rpcdetailed",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"StartLogSegmentNumOps" : 67,
"StartLogSegmentAvgTime" : 6.6716417910447765,
"FinalizeLogSegmentNumOps" : 66,
"FinalizeLogSegmentAvgTime" : 1.5606060606060606,
"JournalNumOps" : 133,
"JournalAvgTime" : 0.15789473684210525,
"GetEditLogManifestNumOps" : 139,
"GetEditLogManifestAvgTime" : 3.1510791366906474,
"GetEditLogManifestFromJournalNumOps" : 68,
"GetEditLogManifestFromJournalAvgTime" : 0.8823529411764706,
"JournalOutOfSyncExceptionNumOps" : 1,
"JournalOutOfSyncExceptionAvgTime" : 13.0
}, {
"name" : "Hadoop:service=JournalNode,name=RpcActivityForPort8485",
"modelerType" : "RpcActivityForPort8485",
"tag.port" : "8485",
"tag.serverName" : "QJournalProtocolService",
"tag.Context" : "rpc",
"tag.NumOpenConnectionsPerUser" : "{}",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"ReceivedBytes" : 106302,
"SentBytes" : 76209,
"RpcQueueTimeNumOps" : 474,
"RpcQueueTimeAvgTime" : 0.0,
"RpcLockWaitTimeNumOps" : 474,
"RpcLockWaitTimeAvgTime" : 0.0,
"RpcProcessingTimeNumOps" : 474,
"RpcProcessingTimeAvgTime" : 2.282700421940928,
"DeferredRpcProcessingTimeNumOps" : 0,
"DeferredRpcProcessingTimeAvgTime" : 0.0,
"RpcAuthenticationFailures" : 0,
"RpcAuthenticationSuccesses" : 0,
"RpcAuthorizationFailures" : 0,
"RpcAuthorizationSuccesses" : 270,
"RpcClientBackoff" : 0,
"RpcSlowCalls" : 0,
"NumOpenConnections" : 0,
"CallQueueLength" : 0,
"NumDroppedConnections" : 0
}
was (Author: jiangjianfei):
Thanks [~weichiu] and [~ayushtkn] for code review.
The RpcDetailedActivity statistics in jmx are some detail infomation. I wonder
whether it is proper to add to the main page. As a comparison, nn and dn seem
not have such detailed infomation at the home page. Hope you can give some
advice.
{
"name" : "Hadoop:service=JournalNode,name=RpcDetailedActivityForPort8485",
"modelerType" : "RpcDetailedActivityForPort8485",
"tag.port" : "8485",
"tag.Context" : "rpcdetailed",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"StartLogSegmentNumOps" : 67,
"StartLogSegmentAvgTime" : 6.6716417910447765,
"FinalizeLogSegmentNumOps" : 66,
"FinalizeLogSegmentAvgTime" : 1.5606060606060606,
"JournalNumOps" : 133,
"JournalAvgTime" : 0.15789473684210525,
"GetEditLogManifestNumOps" : 139,
"GetEditLogManifestAvgTime" : 3.1510791366906474,
"GetEditLogManifestFromJournalNumOps" : 68,
"GetEditLogManifestFromJournalAvgTime" : 0.8823529411764706,
"JournalOutOfSyncExceptionNumOps" : 1,
"JournalOutOfSyncExceptionAvgTime" : 13.0
}, {
"name" : "Hadoop:service=JournalNode,name=RpcActivityForPort8485",
"modelerType" : "RpcActivityForPort8485",
"tag.port" : "8485",
"tag.serverName" : "QJournalProtocolService",
"tag.Context" : "rpc",
"tag.NumOpenConnectionsPerUser" : "{}",
"tag.Hostname" : "zdh-deployer-jiangjianfei01",
"ReceivedBytes" : 106302,
"SentBytes" : 76209,
"RpcQueueTimeNumOps" : 474,
"RpcQueueTimeAvgTime" : 0.0,
"RpcLockWaitTimeNumOps" : 474,
"RpcLockWaitTimeAvgTime" : 0.0,
"RpcProcessingTimeNumOps" : 474,
"RpcProcessingTimeAvgTime" : 2.282700421940928,
"DeferredRpcProcessingTimeNumOps" : 0,
"DeferredRpcProcessingTimeAvgTime" : 0.0,
"RpcAuthenticationFailures" : 0,
"RpcAuthenticationSuccesses" : 0,
"RpcAuthorizationFailures" : 0,
"RpcAuthorizationSuccesses" : 270,
"RpcClientBackoff" : 0,
"RpcSlowCalls" : 0,
"NumOpenConnections" : 0,
"CallQueueLength" : 0,
"NumDroppedConnections" : 0
}
> Improve JournalNode web UI
> --
>
> Key: HDFS-15245
> URL: https://issues.apache.org/jira/browse/HDFS-15245
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node, ui
>Affects Versions: 3.2.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-15245.002.patch, jn web 1.PNG, jn web 2.PNG
>
>
> At present, journalnode web UI is a almost blank page. It almost has no
> useful infomation.
> # Add some infomation of journalnode at the main page.
> # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level,
> Metrics, Configuration & Process Thread Dump
>
--
This message was sent
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: HDFS-15245.002.patch > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: Patch Available (was: Open) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.002.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: Open (was: Patch Available) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: (was: HDFS-15245.001.patch) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Attachment: jn web 2.PNG jn web 1.PNG HDFS-15245.001.patch > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.001.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-15245: - Status: Patch Available (was: In Progress) > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.001.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work started] (HDFS-15245) Improve JournalNode web UI
[ https://issues.apache.org/jira/browse/HDFS-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-15245 started by Jianfei Jiang. > Improve JournalNode web UI > -- > > Key: HDFS-15245 > URL: https://issues.apache.org/jira/browse/HDFS-15245 > Project: Hadoop HDFS > Issue Type: Improvement > Components: journal-node, ui >Affects Versions: 3.2.1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Major > Attachments: HDFS-15245.001.patch, jn web 1.PNG, jn web 2.PNG > > > At present, journalnode web UI is a almost blank page. It almost has no > useful infomation. > # Add some infomation of journalnode at the main page. > # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, > Metrics, Configuration & Process Thread Dump > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-15245) Improve JournalNode web UI
Jianfei Jiang created HDFS-15245: Summary: Improve JournalNode web UI Key: HDFS-15245 URL: https://issues.apache.org/jira/browse/HDFS-15245 Project: Hadoop HDFS Issue Type: Improvement Components: journal-node, ui Affects Versions: 3.2.1 Reporter: Jianfei Jiang Assignee: Jianfei Jiang At present, journalnode web UI is a almost blank page. It almost has no useful infomation. # Add some infomation of journalnode at the main page. # Add a dropdown menu Utilities like DN and JN, contains Logs, Log Level, Metrics, Configuration & Process Thread Dump -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899332#comment-16899332 ] Jianfei Jiang commented on HDFS-14691: -- Thanks [~ste...@apache.org] for your review. > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: command > Attachments: HDFS-14691-001.patch > > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897862#comment-16897862
]
Jianfei Jiang commented on HDFS-8277:
-
Anyone do something to give impetus to the solution of this issue? only this
safemod command is left that not be fixed in DFSAdmin. [~brahmareddy]
[~vinayakumarb]
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch,
> HDFS-8277_5.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-14691: - Status: Patch Available (was: In Progress) > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: command > Attachments: HDFS-14691-001.patch > > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-14691: - Affects Version/s: 3.2.0 > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-14691-001.patch > > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-14691: - Component/s: hdfs > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-14691-001.patch > > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-14691: - Labels: command (was: ) > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: command > Attachments: HDFS-14691-001.patch > > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-14691: - Attachment: HDFS-14691-001.patch > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-14691-001.patch > > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work stopped] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-14691 stopped by Jianfei Jiang. > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work started] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-14691 started by Jianfei Jiang. > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work started] (HDFS-14691) Wrong usage hint for hadoop fs command test
[ https://issues.apache.org/jira/browse/HDFS-14691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-14691 started by Jianfei Jiang. > Wrong usage hint for hadoop fs command test > --- > > Key: HDFS-14691 > URL: https://issues.apache.org/jira/browse/HDFS-14691 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > > The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / > -r / -z. > However when see the usage of this command, only see five options. w and r > are missing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-14691) Wrong usage hint for hadoop fs command test
Jianfei Jiang created HDFS-14691: Summary: Wrong usage hint for hadoop fs command test Key: HDFS-14691 URL: https://issues.apache.org/jira/browse/HDFS-14691 Project: Hadoop HDFS Issue Type: Bug Reporter: Jianfei Jiang Assignee: Jianfei Jiang The command hadoop fs -test support seven options : -d / -e / -f / -s / -w / -r / -z. However when see the usage of this command, only see five options. w and r are missing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-13914) Fix DN UI logs link broken when https is enabled after HDFS-13902
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615556#comment-16615556 ] Jianfei Jiang commented on HDFS-13914: -- Thanks [~brahmareddy] However, as I have tested, the other links except Datanode logs, they can all open properly without "/". So it is unnecessary to fix others. > Fix DN UI logs link broken when https is enabled after HDFS-13902 > - > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: patch > Fix For: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.1.2 > > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613185#comment-16613185 ] Jianfei Jiang commented on HDFS-13914: -- As mentioned in HDFS-13902, the utilities of all nodes contain four tabs: logs, jmx, conf, stacks Moreover, the nn jn & dn also have a page of logLevel, which can set log level for classes, is it necessary to add logLevel to Utilities as well? > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: patch > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-13914: - Affects Version/s: 3.2.0 > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: patch > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-13914: - Labels: patch (was: ) > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: patch > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-13914: - Component/s: datanode > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode >Affects Versions: 3.2.0 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Labels: patch > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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] [Work started] (HDFS-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-13914 started by Jianfei Jiang. > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-13914: - Status: Patch Available (was: In Progress) > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
[ https://issues.apache.org/jira/browse/HDFS-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-13914: - Attachment: HDFS-13914_001.patch > DN UI logs link is broken when https is enabled after HDFS-13902 fixed > -- > > Key: HDFS-13914 > URL: https://issues.apache.org/jira/browse/HDFS-13914 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Minor > Attachments: HDFS-13914_001.patch > > > The bug that DN UI logs link is broken when https is enabled is fixed by > HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-13914) DN UI logs link is broken when https is enabled after HDFS-13902 fixed
Jianfei Jiang created HDFS-13914: Summary: DN UI logs link is broken when https is enabled after HDFS-13902 fixed Key: HDFS-13914 URL: https://issues.apache.org/jira/browse/HDFS-13914 Project: Hadoop HDFS Issue Type: Bug Reporter: Jianfei Jiang Assignee: Jianfei Jiang Attachments: HDFS-13914_001.patch The bug that DN UI logs link is broken when https is enabled is fixed by HDFS-13581, however, after fixing HDFS-13902, this bug appears again. -- 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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580777#comment-16580777
]
Jianfei Jiang edited comment on HDFS-8277 at 9/13/18 6:30 AM:
--
Hi
[~brahmareddy], [~arpitagarwal], [~vinayrpet]
As the commands in DFSAdmin except safemode have been fixed in HDFS-12935
before some months. Safemode command has not been fixed for a long time, could
we fix it now. I have uploaded HDFS-8277_5.patch like what I did in 12935. Hope
to solve this issue asap as it is actually a bug in some cases.
was (Author: jiangjianfei):
Hi
[~brahmareddy]
As the commands in DFSAdmin except safemode have been fixed in HDFS-12935
before some months. Safemode command has not been fixed for a long time, could
we fix it now. I have uploaded HDFS-8277_5.patch like what I did in 12935. Hope
to solve this issue asap as it is actually a bug in some cases.
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch,
> HDFS-8277_5.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang reassigned HDFS-8277:
---
Assignee: Jianfei Jiang (was: Surendra Singh Lilhore)
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch,
> HDFS-8277_5.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-8277:
Status: Patch Available (was: Open)
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch,
> HDFS-8277_5.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580777#comment-16580777
]
Jianfei Jiang commented on HDFS-8277:
-
Hi
[~brahmareddy]
As the commands in DFSAdmin except safemode have been fixed in HDFS-12935
before some months. Safemode command has not been fixed for a long time, could
we fix it now. I have uploaded HDFS-8277_5.patch like what I did in 12935. Hope
to solve this issue asap as it is actually a bug in some cases.
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Surendra Singh Lilhore
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch,
> HDFS-8277_5.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-8277:
Attachment: HDFS-8277_5.patch
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Surendra Singh Lilhore
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch,
> HDFS-8277_5.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430282#comment-16430282
]
Jianfei Jiang edited comment on HDFS-13401 at 4/9/18 11:00 PM:
---
No exception or other hints show that the hdfs folder which mounted to viewfs
MUST exist and we cannot created by mkdir command. Is it necessary to make the
mount viewfs folder be creatable? Or throw a exception when mkdir command under
a viewfs path which is actually not exist?
was (Author: jiangjianfei):
No exception or other hints show that the hdfs folder which mounted to viewfs
MUST exist and we cannot created by mkdir command. Is it necessary to make the
mount viewfs folder be creatable? Or throw a exception when mkdir command under
a viewfs path which is actually not exist?
[~brahmareddy] [~sanjay.radia]
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13401.000.patch
>
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430306#comment-16430306
]
Jianfei Jiang edited comment on HDFS-13401 at 4/9/18 9:26 AM:
--
As InternalDirOfViewFs is readonly, The path of a mount path cannot be created
if no deeper path is givern. I made a prospective in patch 000, mkdir function
for ViewFileSystem is changed when resolving the path. I wonder if it is
necessary to make this change and if this change is proper.
Try to change mkdir function in FileContext as well.
was (Author: jiangjianfei):
As InternalDirOfViewFs is readonly, The path of a mount path cannot be created
if no deeper path is givern. I changed mkdir function for ViewFileSystem when
resolving the path. I wonder if it is necessary to make this change and if this
change is proper.
Try to change mkdir function in FileContext as well.
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13401.000.patch
>
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430306#comment-16430306
]
Jianfei Jiang commented on HDFS-13401:
--
As InternalDirOfViewFs is readonly, The path of a mount path cannot be created
if no deeper path is givern. I changed mkdir function for ViewFileSystem when
resolving the path. I wonder if it is necessary to make this change and if this
change is proper.
Try to change mkdir function in FileContext as well.
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13401.000.patch
>
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13401:
-
Attachment: HDFS-13401.000.patch
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13401.000.patch
>
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430282#comment-16430282
]
Jianfei Jiang commented on HDFS-13401:
--
No exception or other hints show that the hdfs folder which mounted to viewfs
MUST exist and we cannot created by mkdir command. Is it necessary to make the
mount viewfs folder be creatable? Or throw a exception when mkdir command under
a viewfs path which is actually not exist?
[~brahmareddy] [~sanjay.radia]
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Priority: Major
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang reassigned HDFS-13401:
Assignee: (was: Jianfei Jiang)
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Priority: Major
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13401:
-
Affects Version/s: 3.0.1
Component/s: hdfs
federation
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: federation, hdfs
>Affects Versions: 3.0.1
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
[
https://issues.apache.org/jira/browse/HDFS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13401:
-
Description:
In federation cases, if we have a config like below:
fs.viewfs.mounttable.ClusterX.link./foo
hdfs://nn2-clusterx.example.com:8020/footarget
When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is not
actually exist, the command {{hdfs dfs ls /}} can still see the folder, but the
folder is not actually exist. then we try to use mkdir command to create the
viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true, but the folder
is not created. However, when we use {{hdfs dfs mkdir -p /foo/xxx}} which have
a deeper location to create folder, the folder is successfully created. The
results in these two cases may be ambigiuous.
was:
In federation cases, if we have a config like below:
fs.viewfs.mounttable.ClusterX.link./foo
hdfs://nn2-clusterx.example.com:8020/footarget
When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is not
actually exist, the command [[hdfs dfs ls /]] can still see the folder, but the
folder is not actually exist. then we try to use mkdir command to create the
viewfs folder [[hdfs dfs mkdir /foo]], the return code is true, but the folder
is not created. However, when we use [[hdfs dfs mkdir -p /foo/xxx]] which have
a deeper location to create folder, the folder is successfully created. The
results in these two cases may be ambigiuous.
> Different behavior in mkdir when the target folder of mount table is uncreated
> --
>
> Key: HDFS-13401
> URL: https://issues.apache.org/jira/browse/HDFS-13401
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Major
>
> In federation cases, if we have a config like below:
>
> fs.viewfs.mounttable.ClusterX.link./foo
> hdfs://nn2-clusterx.example.com:8020/footarget
>
> When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is
> not actually exist, the command {{hdfs dfs ls /}} can still see the folder,
> but the folder is not actually exist. then we try to use mkdir command to
> create the viewfs folder {{hdfs dfs mkdir /foo}}, the return code is true,
> but the folder is not created. However, when we use {{hdfs dfs mkdir -p
> /foo/xxx}} which have a deeper location to create folder, the folder is
> successfully created. The results in these two cases may be ambigiuous.
--
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-13401) Different behavior in mkdir when the target folder of mount table is uncreated
Jianfei Jiang created HDFS-13401: Summary: Different behavior in mkdir when the target folder of mount table is uncreated Key: HDFS-13401 URL: https://issues.apache.org/jira/browse/HDFS-13401 Project: Hadoop HDFS Issue Type: Bug Reporter: Jianfei Jiang Assignee: Jianfei Jiang In federation cases, if we have a config like below: fs.viewfs.mounttable.ClusterX.link./foo hdfs://nn2-clusterx.example.com:8020/footarget When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is not actually exist, the command [[hdfs dfs ls /]] can still see the folder, but the folder is not actually exist. then we try to use mkdir command to create the viewfs folder [[hdfs dfs mkdir /foo]], the return code is true, but the folder is not created. However, when we use [[hdfs dfs mkdir -p /foo/xxx]] which have a deeper location to create folder, the folder is successfully created. The results in these two cases may be ambigiuous. -- 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-12780) Fix spelling mistake in DistCpUtils.java
[ https://issues.apache.org/jira/browse/HDFS-12780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-12780: - Priority: Trivial (was: Major) > Fix spelling mistake in DistCpUtils.java > > > Key: HDFS-12780 > URL: https://issues.apache.org/jira/browse/HDFS-12780 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 3.0.0-beta1 >Reporter: Jianfei Jiang >Assignee: Jianfei Jiang >Priority: Trivial > Labels: patch > Fix For: 3.2.0 > > Attachments: HDFS-12780.patch > > > We found a spelling mistake in DistCpUtils.java. "* If checksums's can't be > retrieved," should be " * If checksums can't be retrieved," -- 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-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13261:
-
Attachment: HDFS-13261.002-branch-2.patch
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 2.8.3, 3.0.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch, HDFS-13261.002-branch-2.patch,
> HDFS-13261.002.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13261:
-
Status: Patch Available (was: In Progress)
Thanks for [~xyao] comment, update the patch for checking message.
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 3.0.0, 2.8.3
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch, HDFS-13261.002.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13261:
-
Attachment: HDFS-13261.002.patch
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 2.8.3, 3.0.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch, HDFS-13261.002.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13261:
-
Status: In Progress (was: Patch Available)
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 3.0.0, 2.8.3
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13261:
-
Status: Patch Available (was: In Progress)
Patch for trunk. Update patch for trunk-2 after running Jenkins.
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 3.0.0, 2.8.3
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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] [Work started] (HDFS-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HDFS-13261 started by Jianfei Jiang.
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 2.8.3, 3.0.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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-13261) Incorrect null value check
[
https://issues.apache.org/jira/browse/HDFS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13261:
-
Attachment: HDFS-13261.001.patch
> Incorrect null value check
> --
>
> Key: HDFS-13261
> URL: https://issues.apache.org/jira/browse/HDFS-13261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 2.8.3, 3.0.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13261.001.patch
>
>
>
> {code:java}
> public void setZoneName(final String name) {
> Preconditions.checkNotNull(name == null)---error parameter for
> checkNotNull
> zoneName = name;
> }
> {code}
> Like above, in 3.x, the checkNotNull function gets wrong parameter in two
> cases: \{{ZoneReencryptionStatus#setZoneName}} and
> \{{AdminHelper#HelpCommand#HelpCommand}}
> In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
>
--
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-13261) Incorrect null value check
Jianfei Jiang created HDFS-13261:
Summary: Incorrect null value check
Key: HDFS-13261
URL: https://issues.apache.org/jira/browse/HDFS-13261
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs
Affects Versions: 3.0.0, 2.8.3
Reporter: Jianfei Jiang
Assignee: Jianfei Jiang
{code:java}
public void setZoneName(final String name) {
Preconditions.checkNotNull(name == null)---error parameter for
checkNotNull
zoneName = name;
}
{code}
Like above, in 3.x, the checkNotNull function gets wrong parameter in two
cases: \{{ZoneReencryptionStatus#setZoneName}} and
\{{AdminHelper#HelpCommand#HelpCommand}}
In 2.x, the error occurs once in \{{AdminHelper#HelpCommand#HelpCommand}}
--
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-13147) Support -c argument for DFS command head and tail
[
https://issues.apache.org/jira/browse/HDFS-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-13147:
-
Component/s: hdfs
> Support -c argument for DFS command head and tail
> -
>
> Key: HDFS-13147
> URL: https://issues.apache.org/jira/browse/HDFS-13147
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: hdfs, shell
>Affects Versions: 3.0.0
>Reporter: Jianfei Jiang
>Assignee: Jianfei Jiang
>Priority: Minor
> Attachments: HDFS-13147.001.patch, HDFS-13147.002.patch,
> HDFS-13147.003.patch
>
>
> The offset of command {{head}} and {{tail}} is hard coded as 1024 bytes. Goal
> to improve it that the offset can be specified by user like Linux commands.
> Then the commands will be more flexible.
--
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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianfei Jiang updated HDFS-8277:
Comment: was deleted
(was: The other commands in DFSAdmin have been fixed in HDFS-12935. Watching
this issue and hope to finalize this issue asap.)
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Surendra Singh Lilhore
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-8277) Safemode enter fails when Standby NameNode is down
[
https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378517#comment-16378517
]
Jianfei Jiang commented on HDFS-8277:
-
The other commands in DFSAdmin have been fixed in HDFS-12935. Watching this
issue and hope to finalize this issue asap.
> Safemode enter fails when Standby NameNode is down
> --
>
> Key: HDFS-8277
> URL: https://issues.apache.org/jira/browse/HDFS-8277
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
>Affects Versions: 2.6.0
> Environment: HDP 2.2.0
>Reporter: Hari Sekhon
>Assignee: Surendra Singh Lilhore
>Priority: Major
> Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch,
> HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch
>
>
> HDFS fails to enter safemode when the Standby NameNode is down (eg. due to
> AMBARI-10536).
> {code}hdfs dfsadmin -safemode enter
> safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception:
> java.net.ConnectException: Connection refused; For more details see:
> http://wiki.apache.org/hadoop/ConnectionRefused{code}
> This appears to be a bug in that it's not trying both NameNodes like the
> standard hdfs client code does, and is instead stopping after getting a
> connection refused from nn1 which is down. I verified normal hadoop fs writes
> and reads via cli did work at this time, using nn2. I happened to run this
> command as the hdfs user on nn2 which was the surviving Active NameNode.
> After I re-bootstrapped the Standby NN to fix it the command worked as
> expected again.
--
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-13194) CachePool permissions incorrectly checked
[
https://issues.apache.org/jira/browse/HDFS-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378168#comment-16378168
]
Jianfei Jiang edited comment on HDFS-13194 at 2/27/18 7:37 AM:
---
Thanks [~linyiqun] for your magnanimity and kindly review. Update the patch.
As unprivilegedUser has no group, so not use the following to avoid exception.
{code:java}
.setGroupName(unprivilegedUser.getPrimaryGroupName()
{code}
was (Author: jiangjianfei):
Thanks [~linyiqun] for your magnanimity and kindly review. Update the patch.
As unprivilegedUser has no group, so not use
{code:java}
.setGroupName(unprivilegedUser.getPrimaryGroupName()
{code}
> CachePool permissions incorrectly checked
> -
>
> Key: HDFS-13194
> URL: https://issues.apache.org/jira/browse/HDFS-13194
> Project: Hadoop HDFS
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Yiqun Lin
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13194.001.patch, HDFS-13194.002.patch
>
>
> The permissions of CachePool incorrectly checked. The checking logic:
> {code:java}
> public void checkPermission(CachePool pool, FsAction access)
> throws AccessControlException {
> FsPermission mode = pool.getMode();
> if (isSuperUser()) {
> return;
> }
> if (getUser().equals(pool.getOwnerName())
> && mode.getUserAction().implies(access)) {
> return;
> }
> if (isMemberOfGroup(pool.getGroupName())
> && mode.getGroupAction().implies(access)) {
> return;
> }
> // Following line seems incorrect,
> // we should ensure current user is not belong the pool's owner or pool's
> group.
> if (mode.getOtherAction().implies(access)) {
> return;
> }
> throw new AccessControlException("Permission denied while accessing pool "
> + pool.getPoolName() + ": user " + getUser() + " does not have "
> + access.toString() + " permissions.");
> }
> {code}
> For example one corner case, a cachepool (owner: test, group,test-group,
> permission mode:--rwx(007)), then one user which named "test" or whose
> group is "test-group" can both access this pool. But actually this is not
> allowed since permission for its owner or group is none.
> The behavior of checking other user should be updated like this:
> {code:java}
> if (!getUser().equals(pool.getOwnerName())
> && !isMemberOfGroup(pool.getGroupName())
> && mode.getOtherAction().implies(access)) {
> return;
> }
> {code}
--
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-13194) CachePool permissions incorrectly checked
[
https://issues.apache.org/jira/browse/HDFS-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378168#comment-16378168
]
Jianfei Jiang edited comment on HDFS-13194 at 2/27/18 7:36 AM:
---
Thanks [~linyiqun] for your magnanimity and kindly review. Update the patch.
As unprivilegedUser has no group, so not use
{code:java}
.setGroupName(unprivilegedUser.getPrimaryGroupName()
{code}
was (Author: jiangjianfei):
Thanks [~linyiqun] for your magnanimity and kindly review. Update the patch.
As unprivilegedUser has no group, so not use
\{{.setGroupName(unprivilegedUser.getPrimaryGroupName()}}
> CachePool permissions incorrectly checked
> -
>
> Key: HDFS-13194
> URL: https://issues.apache.org/jira/browse/HDFS-13194
> Project: Hadoop HDFS
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Yiqun Lin
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13194.001.patch, HDFS-13194.002.patch
>
>
> The permissions of CachePool incorrectly checked. The checking logic:
> {code:java}
> public void checkPermission(CachePool pool, FsAction access)
> throws AccessControlException {
> FsPermission mode = pool.getMode();
> if (isSuperUser()) {
> return;
> }
> if (getUser().equals(pool.getOwnerName())
> && mode.getUserAction().implies(access)) {
> return;
> }
> if (isMemberOfGroup(pool.getGroupName())
> && mode.getGroupAction().implies(access)) {
> return;
> }
> // Following line seems incorrect,
> // we should ensure current user is not belong the pool's owner or pool's
> group.
> if (mode.getOtherAction().implies(access)) {
> return;
> }
> throw new AccessControlException("Permission denied while accessing pool "
> + pool.getPoolName() + ": user " + getUser() + " does not have "
> + access.toString() + " permissions.");
> }
> {code}
> For example one corner case, a cachepool (owner: test, group,test-group,
> permission mode:--rwx(007)), then one user which named "test" or whose
> group is "test-group" can both access this pool. But actually this is not
> allowed since permission for its owner or group is none.
> The behavior of checking other user should be updated like this:
> {code:java}
> if (!getUser().equals(pool.getOwnerName())
> && !isMemberOfGroup(pool.getGroupName())
> && mode.getOtherAction().implies(access)) {
> return;
> }
> {code}
--
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-13194) CachePool permissions incorrectly checked
[
https://issues.apache.org/jira/browse/HDFS-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378168#comment-16378168
]
Jianfei Jiang edited comment on HDFS-13194 at 2/27/18 7:36 AM:
---
Thanks [~linyiqun] for your magnanimity and kindly review. Update the patch.
As unprivilegedUser has no group, so not use
\{{.setGroupName(unprivilegedUser.getPrimaryGroupName()}}
was (Author: jiangjianfei):
Thanks [~linyiqun] for magnanimity and kindly review. Update the patch.
> CachePool permissions incorrectly checked
> -
>
> Key: HDFS-13194
> URL: https://issues.apache.org/jira/browse/HDFS-13194
> Project: Hadoop HDFS
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Yiqun Lin
>Assignee: Jianfei Jiang
>Priority: Major
> Attachments: HDFS-13194.001.patch, HDFS-13194.002.patch
>
>
> The permissions of CachePool incorrectly checked. The checking logic:
> {code:java}
> public void checkPermission(CachePool pool, FsAction access)
> throws AccessControlException {
> FsPermission mode = pool.getMode();
> if (isSuperUser()) {
> return;
> }
> if (getUser().equals(pool.getOwnerName())
> && mode.getUserAction().implies(access)) {
> return;
> }
> if (isMemberOfGroup(pool.getGroupName())
> && mode.getGroupAction().implies(access)) {
> return;
> }
> // Following line seems incorrect,
> // we should ensure current user is not belong the pool's owner or pool's
> group.
> if (mode.getOtherAction().implies(access)) {
> return;
> }
> throw new AccessControlException("Permission denied while accessing pool "
> + pool.getPoolName() + ": user " + getUser() + " does not have "
> + access.toString() + " permissions.");
> }
> {code}
> For example one corner case, a cachepool (owner: test, group,test-group,
> permission mode:--rwx(007)), then one user which named "test" or whose
> group is "test-group" can both access this pool. But actually this is not
> allowed since permission for its owner or group is none.
> The behavior of checking other user should be updated like this:
> {code:java}
> if (!getUser().equals(pool.getOwnerName())
> && !isMemberOfGroup(pool.getGroupName())
> && mode.getOtherAction().implies(access)) {
> return;
> }
> {code}
--
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
