[jira] [Commented] (HDFS-2162) Merge NameNode roles into NodeType.
[
https://issues.apache.org/jira/browse/HDFS-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188261#comment-13188261
]
Tsz Wo (Nicholas), SZE commented on HDFS-2162:
--
NodeType is used in Storage and Upgrade while NamenodeRole is used in
BackupNode. It does not make sense to pass DATA_NODE to BackupNode and,
similarly, it does not make sense to pass BACKUP/CHECKPOINT to Storage. Thus,
it may be better to keep two enums.
BTW, the enum names do sound confusing. How about renaming NodeType to
StorageType.
> Merge NameNode roles into NodeType.
> ---
>
> Key: HDFS-2162
> URL: https://issues.apache.org/jira/browse/HDFS-2162
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
>Affects Versions: 0.23.0
>Reporter: Suresh Srinivas
>Assignee: Suresh Srinivas
>Priority: Minor
>
> Currently Namenode has {{NamenodeRole}} with roles NAMENODE, BACKUP and
> CHECKPOINT. {{NodeType}} has node types NAME_NODE and DATA_NODE. Merge
> NamenodeRole into NodeType.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2801) Provide a method in client side translators to check for a methods supported in underlying protocol.
[ https://issues.apache.org/jira/browse/HDFS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2801: --- Attachment: HDFS-2801.trunk.patch Updated patch. > Provide a method in client side translators to check for a methods supported > in underlying protocol. > > > Key: HDFS-2801 > URL: https://issues.apache.org/jira/browse/HDFS-2801 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: HDFS-2801.trunk.patch, HDFS-2801.trunk.patch > > > This is jira corresponds to HADOOP-7965. The client side translators should > have a method boolean isMethodSupported(String methodName) which returns true > if the given method is supported and available at the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2803) Adding logging to LeaseRenewer for better lease expiration triage.
[ https://issues.apache.org/jira/browse/HDFS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187981#comment-13187981 ] Todd Lipcon commented on HDFS-2803: --- I think DEBUG level is more appropriate for both. Otherwise any time we run a dfs command like dfs -put, we'll end up with an INFO level message. > Adding logging to LeaseRenewer for better lease expiration triage. > -- > > Key: HDFS-2803 > URL: https://issues.apache.org/jira/browse/HDFS-2803 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Reporter: Jimmy Xiang >Priority: Minor > Labels: newbie > > It will be helpful to add some logging to LeaseRenewer when the daemon is > terminated (Info level), > and when the lease is renewed (Debug level). Since lacking logging, it is > hard to know > if a DFS client doesn't renew the lease because it hangs, or the lease > renewer daemon is gone somehow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2742) HA: observed dataloss in replication stress test
[ https://issues.apache.org/jira/browse/HDFS-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187957#comment-13187957 ] Todd Lipcon commented on HDFS-2742: --- This may have broken the optimization where we dont initialize repl queues until the end of safemode - we probably need to turn off the incremental tracking of safe block count in the case that it's an empty FS being loaded... Still looking into it. > HA: observed dataloss in replication stress test > > > Key: HDFS-2742 > URL: https://issues.apache.org/jira/browse/HDFS-2742 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Blocker > Attachments: hdfs-2742.txt, hdfs-2742.txt, hdfs-2742.txt, > log-colorized.txt > > > The replication stress test case failed over the weekend since one of the > replicas went missing. Still diagnosing the issue, but it seems like the > chain of events was something like: > - a block report was generated on one of the nodes while the block was being > written - thus the block report listed the block as RBW > - when the standby replayed this queued message, it was replayed after the > file was marked complete. Thus it marked this replica as corrupt > - it asked the DN holding the corrupt replica to delete it. And, I think, > removed it from the block map at this time. > - That DN then did another block report before receiving the deletion. This > caused it to be re-added to the block map, since it was "FINALIZED" now. > - Replication was lowered on the file, and it counted the above replica as > non-corrupt, and asked for the other replicas to be deleted. > - All replicas were lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2681) Add ZK client for leader election
[ https://issues.apache.org/jira/browse/HDFS-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2681: - Attachment: HDFS-2681.HDFS-1623.patch granting the ASF license this time for the previous patch on class annotations. > Add ZK client for leader election > - > > Key: HDFS-2681 > URL: https://issues.apache.org/jira/browse/HDFS-2681 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Suresh Srinivas >Assignee: Bikas Saha > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, > HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, > HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, > HDFS-2681.HDFS-1623.patch, Zookeeper based Leader Election and Monitoring > Library.pdf > > > ZKClient needs to support the following capabilities: > # Ability to create a znode for co-ordinating leader election. > # Ability to monitor and receive call backs when active znode status changes. > # Ability to get information about the active node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2681) Add ZK client for leader election
[ https://issues.apache.org/jira/browse/HDFS-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2681: - Attachment: HDFS-2681.HDFS-1623.patch Adding patch with audience.private and stability.evolving annotations for the elector class > Add ZK client for leader election > - > > Key: HDFS-2681 > URL: https://issues.apache.org/jira/browse/HDFS-2681 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Suresh Srinivas >Assignee: Bikas Saha > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, > HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, > HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, Zookeeper based Leader > Election and Monitoring Library.pdf > > > ZKClient needs to support the following capabilities: > # Ability to create a znode for co-ordinating leader election. > # Ability to monitor and receive call backs when active znode status changes. > # Ability to get information about the active node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2803) Adding logging to LeaseRenewer for better lease expiration triage.
[ https://issues.apache.org/jira/browse/HDFS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2803: -- Component/s: name-node Target Version/s: 0.23.1 Labels: newbie (was: ) This will help debug HBase issues. > Adding logging to LeaseRenewer for better lease expiration triage. > -- > > Key: HDFS-2803 > URL: https://issues.apache.org/jira/browse/HDFS-2803 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Reporter: Jimmy Xiang >Priority: Minor > Labels: newbie > > It will be helpful to add some logging to LeaseRenewer when the daemon is > terminated (Info level), > and when the lease is renewed (Debug level). Since lacking logging, it is > hard to know > if a DFS client doesn't renew the lease because it hangs, or the lease > renewer daemon is gone somehow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2804) SBN should not mark blocks under-replicated when exiting safemode
SBN should not mark blocks under-replicated when exiting safemode - Key: HDFS-2804 URL: https://issues.apache.org/jira/browse/HDFS-2804 Project: Hadoop HDFS Issue Type: Sub-task Components: ha, name-node Affects Versions: HA branch (HDFS-1623) Reporter: Todd Lipcon Assignee: Todd Lipcon In testing on a cluster, I restarted with one fewer datanodes than previously. This caused a few thousand blocks to be under-replicated. Similar to HDFS-2795, I saw the under-replicated blocks on the SBN, slowly decreasing as the replication thread ran. This seems to be because we process the replication queue when exiting safemode, even if in standby mode. It also reports many "missing blocks" in the NN UI which are slowly decreasing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2803) Adding logging to LeaseRenewer for better lease expiration triage.
[ https://issues.apache.org/jira/browse/HDFS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HDFS-2803: -- Description: It will be helpful to add some logging to LeaseRenewer when the daemon is terminated (Info level), and when the lease is renewed (Debug level). Since lacking logging, it is hard to know if a DFS client doesn't renew the lease because it hangs, or the lease renewer daemon is gone somehow. was: It be helpful to add some logging to LeaseRenewer when the daemon is terminated (Info level), and when the lease is renewed (Debug level). Since lacking logging, it will be hard to know if a DFS client doesn't renew the lease because it hangs, or the lease renewer daemon is gone somehow. > Adding logging to LeaseRenewer for better lease expiration triage. > -- > > Key: HDFS-2803 > URL: https://issues.apache.org/jira/browse/HDFS-2803 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jimmy Xiang >Priority: Minor > > It will be helpful to add some logging to LeaseRenewer when the daemon is > terminated (Info level), > and when the lease is renewed (Debug level). Since lacking logging, it is > hard to know > if a DFS client doesn't renew the lease because it hangs, or the lease > renewer daemon is gone somehow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2803) Adding logging to LeaseRenewer for better lease expiration triage.
Adding logging to LeaseRenewer for better lease expiration triage. -- Key: HDFS-2803 URL: https://issues.apache.org/jira/browse/HDFS-2803 Project: Hadoop HDFS Issue Type: Improvement Reporter: Jimmy Xiang Priority: Minor It be helpful to add some logging to LeaseRenewer when the daemon is terminated (Info level), and when the lease is renewed (Debug level). Since lacking logging, it will be hard to know if a DFS client doesn't renew the lease because it hangs, or the lease renewer daemon is gone somehow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2802) Support for RW/RO snapshots in HDFS
Support for RW/RO snapshots in HDFS --- Key: HDFS-2802 URL: https://issues.apache.org/jira/browse/HDFS-2802 Project: Hadoop HDFS Issue Type: New Feature Components: name-node Reporter: Hari Mankude Assignee: Hari Mankude Fix For: 0.24.0 Snapshots are point in time images of parts of the filesystem or the entire filesystem. Snapshots can be a read-only or a read-write point in time copy of the filesystem. There are several use cases for snapshots in HDFS. I will post a detailed write-up soon with with more information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HDFS-2592) HA: Balancer support for HA namenodes
[ https://issues.apache.org/jira/browse/HDFS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2592. --- Resolution: Fixed Fix Version/s: HA branch (HDFS-1623) Hadoop Flags: Reviewed > HA: Balancer support for HA namenodes > - > > Key: HDFS-2592 > URL: https://issues.apache.org/jira/browse/HDFS-2592 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Uma Maheswara Rao G > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2592.patch, HDFS-2592.patch, HDFS-2592.patch, > HDFS-2592.patch > > > The balancer currently interacts directly with namenode InetSocketAddresses > and makes its own IPC proxies. We need to integrate it with HA so that it > uses the same client failover infrastructure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2592) HA: Balancer support for HA namenodes
[ https://issues.apache.org/jira/browse/HDFS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187868#comment-13187868 ] Todd Lipcon commented on HDFS-2592: --- +1, will commit momentarily. > HA: Balancer support for HA namenodes > - > > Key: HDFS-2592 > URL: https://issues.apache.org/jira/browse/HDFS-2592 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Uma Maheswara Rao G > Attachments: HDFS-2592.patch, HDFS-2592.patch, HDFS-2592.patch, > HDFS-2592.patch > > > The balancer currently interacts directly with namenode InetSocketAddresses > and makes its own IPC proxies. We need to integrate it with HA so that it > uses the same client failover infrastructure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2592) HA: Balancer support for HA namenodes
[ https://issues.apache.org/jira/browse/HDFS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187789#comment-13187789 ] Uma Maheswara Rao G commented on HDFS-2592: --- Thank you very much Todd, for the nice reviews! Updated the patch. > HA: Balancer support for HA namenodes > - > > Key: HDFS-2592 > URL: https://issues.apache.org/jira/browse/HDFS-2592 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Uma Maheswara Rao G > Attachments: HDFS-2592.patch, HDFS-2592.patch, HDFS-2592.patch, > HDFS-2592.patch > > > The balancer currently interacts directly with namenode InetSocketAddresses > and makes its own IPC proxies. We need to integrate it with HA so that it > uses the same client failover infrastructure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2592) HA: Balancer support for HA namenodes
[ https://issues.apache.org/jira/browse/HDFS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-2592: -- Attachment: HDFS-2592.patch > HA: Balancer support for HA namenodes > - > > Key: HDFS-2592 > URL: https://issues.apache.org/jira/browse/HDFS-2592 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Uma Maheswara Rao G > Attachments: HDFS-2592.patch, HDFS-2592.patch, HDFS-2592.patch, > HDFS-2592.patch > > > The balancer currently interacts directly with namenode InetSocketAddresses > and makes its own IPC proxies. We need to integrate it with HA so that it > uses the same client failover infrastructure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-362) FSEditLog should not writes long and short as UTF8 and should not use ArrayWritable for writing non-array items
[ https://issues.apache.org/jira/browse/HDFS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187664#comment-13187664 ] Hudson commented on HDFS-362: - Integrated in Hadoop-Mapreduce-trunk #961 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/961/]) Update changelog for HDFS-362 to reflect the merge. eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232205 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > FSEditLog should not writes long and short as UTF8 and should not use > ArrayWritable for writing non-array items > --- > > Key: HDFS-362 > URL: https://issues.apache.org/jira/browse/HDFS-362 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.23.0, 0.24.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Uma Maheswara Rao G > Fix For: 0.23.1 > > Attachments: HDFS-362.1.patch, HDFS-362.2.patch, HDFS-362.2b.patch, > HDFS-362.2c.patch, HDFS-362.2d.patch, HDFS-362.2d.patch, HDFS-362.2e.patch, > HDFS-362.patch > > > In FSEditLog, > - long and short are first converted to String and are further converted to > UTF8 > - For some non-array items, it first create an ArrayWritable object to hold > all the items and then writes the ArrayWritable object. > These result creating many intermediate objects which affects Namenode CPU > performance and Namenode restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2740) Enable the trash feature by default
[ https://issues.apache.org/jira/browse/HDFS-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187655#comment-13187655 ] T Meyarivan commented on HDFS-2740: --- Re the common case where a user issues an incorrect delete cmd - Is short fs.trash.interval (even as low as 1 hr) reasonable ? (recovery is still possible, the space is freed up in a reasonable time frame for others) -- > Enable the trash feature by default > --- > > Key: HDFS-2740 > URL: https://issues.apache.org/jira/browse/HDFS-2740 > Project: Hadoop HDFS > Issue Type: Wish > Components: hdfs client, name-node >Affects Versions: 0.23.0 >Reporter: Harsh J > Labels: newbie > Attachments: hdfs-2740.patch, hdfs-2740.patch > > > Currently trash is disabled out of box. I do not think it'd be of high > surprise to anyone (but surely a relief when *hit happens) to have trash > enabled by default, with the usually recommended periods of 1-day. > Thoughts? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-362) FSEditLog should not writes long and short as UTF8 and should not use ArrayWritable for writing non-array items
[ https://issues.apache.org/jira/browse/HDFS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187651#comment-13187651 ] Hudson commented on HDFS-362: - Integrated in Hadoop-Mapreduce-0.23-Build #163 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/163/]) HDFS-362. svn merge -c 1171945 from trunk eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232203 Files : * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LayoutVersion.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogOp.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImageSerialization.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineEditsViewer/EditsLoaderCurrent.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineImageViewer/ImageLoaderCurrent.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSEditLogLoader.java > FSEditLog should not writes long and short as UTF8 and should not use > ArrayWritable for writing non-array items > --- > > Key: HDFS-362 > URL: https://issues.apache.org/jira/browse/HDFS-362 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.23.0, 0.24.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Uma Maheswara Rao G > Fix For: 0.23.1 > > Attachments: HDFS-362.1.patch, HDFS-362.2.patch, HDFS-362.2b.patch, > HDFS-362.2c.patch, HDFS-362.2d.patch, HDFS-362.2d.patch, HDFS-362.2e.patch, > HDFS-362.patch > > > In FSEditLog, > - long and short are first converted to String and are further converted to > UTF8 > - For some non-array items, it first create an ArrayWritable object to hold > all the items and then writes the ArrayWritable object. > These result creating many intermediate objects which affects Namenode CPU > performance and Namenode restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2795) HA: Standby NN takes a long time to recover from a dead DN starting up
[ https://issues.apache.org/jira/browse/HDFS-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187633#comment-13187633 ] Hudson commented on HDFS-2795: -- Integrated in Hadoop-Hdfs-HAbranch-build #50 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/50/]) HDFS-2795. Standby NN takes a long time to recover from a dead DN starting up. Contributed by Todd Lipcon. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232285 Files : * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManagerTestUtil.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestStandbyIsHot.java > HA: Standby NN takes a long time to recover from a dead DN starting up > -- > > Key: HDFS-2795 > URL: https://issues.apache.org/jira/browse/HDFS-2795 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Aaron T. Myers >Assignee: Todd Lipcon >Priority: Critical > Fix For: HA branch (HDFS-1623) > > Attachments: hdfs-2795.txt > > > To reproduce: > # Start an HA cluster with a DN. > # Write several blocks to the FS with replication 1. > # Shutdown the DN > # Wait for the NNs to declare the DN dead. All blocks will be > under-replicated. > # Restart the DN. > Note that upon restarting the DN, the active NN will immediately get all > block locations from the initial BR. The standby NN will not, and instead > will slowly add block locations for a subset of the previously-missing blocks > on every DN heartbeat. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2747) HA: entering safe mode after starting SBN can NPE
[
https://issues.apache.org/jira/browse/HDFS-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187634#comment-13187634
]
Hudson commented on HDFS-2747:
--
Integrated in Hadoop-Hdfs-HAbranch-build #50 (See
[https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/50/])
HDFS-2747. Entering safe mode after starting SBN can NPE. Contributed by
Uma Maheswara Rao G.
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232176
Files :
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestHASafeMode.java
> HA: entering safe mode after starting SBN can NPE
> -
>
> Key: HDFS-2747
> URL: https://issues.apache.org/jira/browse/HDFS-2747
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
>Affects Versions: HA branch (HDFS-1623)
>Reporter: Eli Collins
>Assignee: Uma Maheswara Rao G
> Fix For: HA branch (HDFS-1623)
>
> Attachments: HDFS-2747.patch, HDFS-2747.patch
>
>
> Entering Safemode on the primary after while it's already in safemode after
> the SBN is started results in an NPE:
> {noformat}
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs dfsadmin -safemode get
> Safe mode is ON
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs dfsadmin -safemode enter
> safemode: java.lang.NullPointerException
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2767) HA: ConfiguredFailoverProxyProvider should support NameNodeProtocol
[ https://issues.apache.org/jira/browse/HDFS-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187632#comment-13187632 ] Hudson commented on HDFS-2767: -- Integrated in Hadoop-Hdfs-HAbranch-build #50 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/50/]) HDFS-2767. ConfiguredFailoverProxyProvider should support NameNodeProtocol. Contributed by Uma Maheswara Rao G. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232284 Files : * /hadoop/common/branches/HDFS-1623/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/DefaultFailoverProxyProvider.java * /hadoop/common/branches/HDFS-1623/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/FailoverProxyProvider.java * /hadoop/common/branches/HDFS-1623/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/retry/TestFailoverProxy.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSUtil.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HAUtil.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/NameNodeConnector.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/ConfiguredFailoverProxyProvider.java > HA: ConfiguredFailoverProxyProvider should support NameNodeProtocol > --- > > Key: HDFS-2767 > URL: https://issues.apache.org/jira/browse/HDFS-2767 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, hdfs client >Affects Versions: HA branch (HDFS-1623) >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Blocker > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2767.patch, HDFS-2767.patch, HDFS-2767.patch, > hdfs-2767-what-todd-had.txt > > > Presentely ConfiguredFailoverProxyProvider supports ClinetProtocol. > It should support NameNodeProtocol also, because Balancer uses > NameNodeProtocol for getting blocks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2772) HA: On transition to active, standby should not swallow ELIE
[ https://issues.apache.org/jira/browse/HDFS-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187631#comment-13187631 ] Hudson commented on HDFS-2772: -- Integrated in Hadoop-Hdfs-HAbranch-build #50 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/50/]) HDFS-2772. On transition to active, standby should not swallow ELIE. Contributed by Aaron T. Myers atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232197 Files : * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/EditLogTailer.java * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestFailureToReadEdits.java > HA: On transition to active, standby should not swallow ELIE > > > Key: HDFS-2772 > URL: https://issues.apache.org/jira/browse/HDFS-2772 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Aaron T. Myers >Assignee: Aaron T. Myers > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2772-HDFS-1623.patch > > > EditLogTailer#doTailEdits currently catches, logs, and swallows > EditLogInputException. This is fine in the case when the standby is sitting > idly behind tailing logs. However, when the standby is transitioning to > active, swallowing this exception is incorrect, since it could cause the > standby to silently fail to load all the edits before becoming active. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-362) FSEditLog should not writes long and short as UTF8 and should not use ArrayWritable for writing non-array items
[ https://issues.apache.org/jira/browse/HDFS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187625#comment-13187625 ] Hudson commented on HDFS-362: - Integrated in Hadoop-Hdfs-0.23-Build #141 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/141/]) HDFS-362. svn merge -c 1171945 from trunk eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232203 Files : * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LayoutVersion.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogOp.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImageSerialization.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineEditsViewer/EditsLoaderCurrent.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineImageViewer/ImageLoaderCurrent.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSEditLogLoader.java > FSEditLog should not writes long and short as UTF8 and should not use > ArrayWritable for writing non-array items > --- > > Key: HDFS-362 > URL: https://issues.apache.org/jira/browse/HDFS-362 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.23.0, 0.24.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Uma Maheswara Rao G > Fix For: 0.23.1 > > Attachments: HDFS-362.1.patch, HDFS-362.2.patch, HDFS-362.2b.patch, > HDFS-362.2c.patch, HDFS-362.2d.patch, HDFS-362.2d.patch, HDFS-362.2e.patch, > HDFS-362.patch > > > In FSEditLog, > - long and short are first converted to String and are further converted to > UTF8 > - For some non-array items, it first create an ArrayWritable object to hold > all the items and then writes the ArrayWritable object. > These result creating many intermediate objects which affects Namenode CPU > performance and Namenode restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-362) FSEditLog should not writes long and short as UTF8 and should not use ArrayWritable for writing non-array items
[ https://issues.apache.org/jira/browse/HDFS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187619#comment-13187619 ] Hudson commented on HDFS-362: - Integrated in Hadoop-Hdfs-trunk #928 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/928/]) Update changelog for HDFS-362 to reflect the merge. eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1232205 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > FSEditLog should not writes long and short as UTF8 and should not use > ArrayWritable for writing non-array items > --- > > Key: HDFS-362 > URL: https://issues.apache.org/jira/browse/HDFS-362 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.23.0, 0.24.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Uma Maheswara Rao G > Fix For: 0.23.1 > > Attachments: HDFS-362.1.patch, HDFS-362.2.patch, HDFS-362.2b.patch, > HDFS-362.2c.patch, HDFS-362.2d.patch, HDFS-362.2d.patch, HDFS-362.2e.patch, > HDFS-362.patch > > > In FSEditLog, > - long and short are first converted to String and are further converted to > UTF8 > - For some non-array items, it first create an ArrayWritable object to hold > all the items and then writes the ArrayWritable object. > These result creating many intermediate objects which affects Namenode CPU > performance and Namenode restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2725) hdfs script usage information is missing the information about "dfs" command
[ https://issues.apache.org/jira/browse/HDFS-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187572#comment-13187572 ] Hadoop QA commented on HDFS-2725: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12510819/HDFS-2725.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 javadoc. The javadoc tool appears to have generated 21 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. -1 release audit. The applied patch generated 1 release audit warnings (more than the trunk's current 0 warnings). +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1780//testReport/ Release audit warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1780//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1780//artifact/trunk/hadoop-hdfs-project/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1780//console This message is automatically generated. > hdfs script usage information is missing the information about "dfs" command > > > Key: HDFS-2725 > URL: https://issues.apache.org/jira/browse/HDFS-2725 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client >Affects Versions: 0.23.0, 0.24.0 >Reporter: Prashant Sharma > Labels: hdfs > Fix For: 0.23.0, 0.24.0 > > Attachments: HDFS-2725.patch, HDFS-2725.patch > > > hdfs script does not print the command "dfs" in the usage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2801) Provide a method in client side translators to check for a methods supported in underlying protocol.
[ https://issues.apache.org/jira/browse/HDFS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2801: --- Attachment: HDFS-2801.trunk.patch > Provide a method in client side translators to check for a methods supported > in underlying protocol. > > > Key: HDFS-2801 > URL: https://issues.apache.org/jira/browse/HDFS-2801 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: HDFS-2801.trunk.patch > > > This is jira corresponds to HADOOP-7965. The client side translators should > have a method boolean isMethodSupported(String methodName) which returns true > if the given method is supported and available at the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2367) HA: Enable the configuration of multiple HA cluster addresses
[ https://issues.apache.org/jira/browse/HDFS-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187549#comment-13187549 ] Todd Lipcon commented on HDFS-2367: --- Rather than add the new initialize API, can we just add another argument to the "conventional constructor" for the interface? ie we already require that the implementations have a constructor which takes the interface - let's just require they also take the URI? It seems reasonable to me. Perhaps we should add a test case which sets up a federated cluster, each of the nameservices being HA? I think we have the pieces in place to do it, but would be good to verify. > HA: Enable the configuration of multiple HA cluster addresses > - > > Key: HDFS-2367 > URL: https://issues.apache.org/jira/browse/HDFS-2367 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, hdfs client >Affects Versions: HA branch (HDFS-1623) >Reporter: Aaron T. Myers >Assignee: Aaron T. Myers > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2367-HDFS-1623.patch > > > Todd pointed out this issue with the current patch posted for HDFS-1623. It > seems like the solution would be to replace "dfs.ha.namenode.addresses" with > something like "dfs.ha.namenode.addresses.", so as to be able to > support configuring the addresses of multiple HA clusters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2801) Provide a method in client side translators to check for a methods supported in underlying protocol.
Provide a method in client side translators to check for a methods supported in underlying protocol. Key: HDFS-2801 URL: https://issues.apache.org/jira/browse/HDFS-2801 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Jitendra Nath Pandey Assignee: Jitendra Nath Pandey This is jira corresponds to HADOOP-7965. The client side translators should have a method boolean isMethodSupported(String methodName) which returns true if the given method is supported and available at the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2725) hdfs script usage information is missing the information about "dfs" command
[ https://issues.apache.org/jira/browse/HDFS-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Sharma updated HDFS-2725: -- Attachment: HDFS-2725.patch Reattaching, to check if it applies to .23 and .24 > hdfs script usage information is missing the information about "dfs" command > > > Key: HDFS-2725 > URL: https://issues.apache.org/jira/browse/HDFS-2725 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client >Affects Versions: 0.23.0, 0.24.0 >Reporter: Prashant Sharma > Labels: hdfs > Fix For: 0.23.0, 0.24.0 > > Attachments: HDFS-2725.patch, HDFS-2725.patch > > > hdfs script does not print the command "dfs" in the usage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HDFS-2796) TestDFSClientFailover shuold use simpleHATopology.
[ https://issues.apache.org/jira/browse/HDFS-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-2796. --- Resolution: Duplicate As HDFS-2367 handling this fix, marking this as duplicate. > TestDFSClientFailover shuold use simpleHATopology. > -- > > Key: HDFS-2796 > URL: https://issues.apache.org/jira/browse/HDFS-2796 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > > This is to address the TODO in TestDFSClientFailover. > Here presently we used SimpleFederationTopology to test client failover. Now > HATopology is availale to test actual cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2367) HA: Enable the configuration of multiple HA cluster addresses
[ https://issues.apache.org/jira/browse/HDFS-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187523#comment-13187523 ] Uma Maheswara Rao G commented on HDFS-2367: --- Ok Aaron, I will do that. Thanks for the confirmation. > HA: Enable the configuration of multiple HA cluster addresses > - > > Key: HDFS-2367 > URL: https://issues.apache.org/jira/browse/HDFS-2367 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, hdfs client >Affects Versions: HA branch (HDFS-1623) >Reporter: Aaron T. Myers >Assignee: Aaron T. Myers > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2367-HDFS-1623.patch > > > Todd pointed out this issue with the current patch posted for HDFS-1623. It > seems like the solution would be to replace "dfs.ha.namenode.addresses" with > something like "dfs.ha.namenode.addresses.", so as to be able to > support configuring the addresses of multiple HA clusters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
