[
https://issues.apache.org/jira/browse/HDFS-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075100#comment-17075100
]
Andrew Timonin commented on HDFS-15060:
---
Sorry for a long delay...
[~sodonnell] Yes
[
https://issues.apache.org/jira/browse/HDFS-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Timonin updated HDFS-15060:
--
Description:
When I upgrade hadoop to new version (using for ex.
[https://hadoop.apache.org/do
[
https://issues.apache.org/jira/browse/HDFS-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Timonin updated HDFS-15060:
--
Description:
When I upgrade hadoop to new version (using for ex.
[https://hadoop.apache.org/do
[
https://issues.apache.org/jira/browse/HDFS-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995556#comment-16995556
]
Andrew Timonin edited comment on HDFS-15060 at 12/13/19 11:30 AM:
-
[
https://issues.apache.org/jira/browse/HDFS-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995556#comment-16995556
]
Andrew Timonin commented on HDFS-15060:
---
I'll try as a workaround doing
> namenode
Andrew Timonin created HDFS-15060:
-
Summary: namenode doesn't retry JN when other JN goes down
Key: HDFS-15060
URL: https://issues.apache.org/jira/browse/HDFS-15060
Project: Hadoop HDFS
Issue