[jira] [Updated] (HDFS-3092) Enable journal protocol based editlog streaming for standby namenode
[ https://issues.apache.org/jira/browse/HDFS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-3092: - Attachment: ComparisonofApproachesforHAJournals.pdf Sanjay and I were trying to objectively compare different approaches (HDFS-3077, HDFS-3092, BookKeeper). I have attached a document outlining the observations. Hopefully, this will help in structuring the discussions going forward. > Enable journal protocol based editlog streaming for standby namenode > > > Key: HDFS-3092 > URL: https://issues.apache.org/jira/browse/HDFS-3092 > Project: Hadoop HDFS > Issue Type: Improvement > Components: ha, name-node >Affects Versions: 0.24.0, 0.23.3 >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Attachments: ComparisonofApproachesforHAJournals.pdf, > MultipleSharedJournals.pdf, MultipleSharedJournals.pdf, > MultipleSharedJournals.pdf > > > Currently standby namenode relies on reading shared editlogs to stay current > with the active namenode, for namespace changes. BackupNode used streaming > edits from active namenode for doing the same. This jira is to explore using > journal protocol based editlog streams for the standby namenode. A daemon in > standby will get the editlogs from the active and write it to local edits. To > begin with, the existing standby mechanism of reading from a file, will > continue to be used, instead of from shared edits, from the local edits. -- 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-2185) HA: ZK-based FailoverController
[ https://issues.apache.org/jira/browse/HDFS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2185: - Attachment: Failover_Controller.jpg > HA: ZK-based FailoverController > --- > > Key: HDFS-2185 > URL: https://issues.apache.org/jira/browse/HDFS-2185 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha >Affects Versions: HA branch (HDFS-1623) >Reporter: Eli Collins >Assignee: Todd Lipcon > Attachments: Failover_Controller.jpg > > > This jira is for a ZK-based FailoverController daemon. The FailoverController > is a separate daemon from the NN that does the following: > * Initiates leader election (via ZK) when necessary > * Performs health monitoring (aka failure detection) > * Performs fail-over (standby to active and active to standby transitions) > * Heartbeats to ensure the liveness > It should have the same/similar interface as the Linux HA RM to aid > pluggability. -- 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-2909) HA: Inaccessible shared edits dir not getting removed from FSImage storage dirs upon error
[ https://issues.apache.org/jira/browse/HDFS-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2909: - Attachment: HDFS-2909-HDFS-1623.patch Attaching a patch which syncs FileJournalManager with NNStorage. When FileJournalManager has an error doing I/O then it reports an error against its StorageDirectory to NNStorage. Thus errors in file journal get reported to the NNStorage dirs. This only does the half the sync. IMO, FileJournalManager should check the state of its StorageDirectory inside NNStorage before proceeding to make changes. That would complete the sync between FileJournalManager and NNStorage. That way when a StorageDirectory get removed/restored then the FileJournalManager can stop/restore write to it. > HA: Inaccessible shared edits dir not getting removed from FSImage storage > dirs upon error > -- > > Key: HDFS-2909 > URL: https://issues.apache.org/jira/browse/HDFS-2909 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2909-HDFS-1623.patch > > -- 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-2902) HA: Allow new (shared) edits log dir to be configured while NN is running
[ https://issues.apache.org/jira/browse/HDFS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2902: - Summary: HA: Allow new (shared) edits log dir to be configured while NN is running (was: HA: Allow new edits log dir to be configured while NN is running) > HA: Allow new (shared) edits log dir to be configured while NN is running > - > > Key: HDFS-2902 > URL: https://issues.apache.org/jira/browse/HDFS-2902 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > -- 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-2902) HA: Allow new edits log dir to be configured while NN is running
[ https://issues.apache.org/jira/browse/HDFS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2902: - Summary: HA: Allow new edits log dir to be configured while NN is running (was: HA: Allow new shared edit logs dir to be configured while NN is running) > HA: Allow new edits log dir to be configured while NN is running > > > Key: HDFS-2902 > URL: https://issues.apache.org/jira/browse/HDFS-2902 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > -- 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-2912) HA: Namenode not shutting down when shared edits dir is inaccessible
[ https://issues.apache.org/jira/browse/HDFS-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2912: - Attachment: HDFS-2912.HDFS-1623.patch I need to make Eclipse warn me when I dont follow coding convention. This patch also addresses your comments from [HDFS-2915|https://issues.apache.org/jira/browse/HDFS-2915] > HA: Namenode not shutting down when shared edits dir is inaccessible > > > Key: HDFS-2912 > URL: https://issues.apache.org/jira/browse/HDFS-2912 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2909.HDFS-1623.patch, HDFS-2912.HDFS-1623.patch, > HDFS-2912.HDFS-1623.patch > > > When there is an error in shared edits dir then current policy requires the > active name node to abort and shutdown. > Currently there is no way to shut down the name node and hence this does not > happen even after all journals have been aborted on error. In fact the name > node stays Active and also is not in safe mode. Ideally it should shut down, > or at least go into safe mode or standby mode. -- 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-2915) HA: TestFailureOfSharedDir.testFailureOfSharedDir() has race condition
[ https://issues.apache.org/jira/browse/HDFS-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2915: - Attachment: HDFS-2915.HDFS-1623.patch Sorry. I attached the patch made for testing. > HA: TestFailureOfSharedDir.testFailureOfSharedDir() has race condition > -- > > Key: HDFS-2915 > URL: https://issues.apache.org/jira/browse/HDFS-2915 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Attachments: HDFS-2915.HDFS-1623.patch, HDFS-2915.HDFS-1623.patch > > > The test deletes the shared edits dir to simulate a failure. Then it calls > rollEditLogs() to trigger the deleted dir to be used and fail with an > IOException. Unfortunately, deleting the shared dir can put the NN in safe > mode due to lack of space. This causes a SafeModeException to be thrown when > rollEditDirs() is called. This exception is caught as an IOException in the > test but the associated assert in the catch block fails. > This always happens in the debugger because the delay in stepping through > causes the safe mode change to happen before rollEditLogs() gets called. -- 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-2912) HA: Namenode not shutting down when shared edits dir is inaccessible
[ https://issues.apache.org/jira/browse/HDFS-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2912: - Attachment: HDFS-2912.HDFS-1623.patch Adding patch that does the above. > HA: Namenode not shutting down when shared edits dir is inaccessible > > > Key: HDFS-2912 > URL: https://issues.apache.org/jira/browse/HDFS-2912 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2909.HDFS-1623.patch, HDFS-2912.HDFS-1623.patch > > > When there is an error in shared edits dir then current policy requires the > active name node to abort and shutdown. > Currently there is no way to shut down the name node and hence this does not > happen even after all journals have been aborted on error. In fact the name > node stays Active and also is not in safe mode. Ideally it should shut down, > or at least go into safe mode or standby mode. -- 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-2915) HA: TestFailureOfSharedDir.testFailureOfSharedDir() has race condition
[ https://issues.apache.org/jira/browse/HDFS-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2915: - Attachment: HDFS-2915.HDFS-1623.patch Attaching a patch that replaces shared dir delete with shared dir write permissions revoked. This removes the race with safe mode. > HA: TestFailureOfSharedDir.testFailureOfSharedDir() has race condition > -- > > Key: HDFS-2915 > URL: https://issues.apache.org/jira/browse/HDFS-2915 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Attachments: HDFS-2915.HDFS-1623.patch > > > The test deletes the shared edits dir to simulate a failure. Then it calls > rollEditLogs() to trigger the deleted dir to be used and fail with an > IOException. Unfortunately, deleting the shared dir can put the NN in safe > mode due to lack of space. This causes a SafeModeException to be thrown when > rollEditDirs() is called. This exception is caught as an IOException in the > test but the associated assert in the catch block fails. > This always happens in the debugger because the delay in stepping through > causes the safe mode change to happen before rollEditLogs() gets called. -- 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-2912) HA: Namenode not shutting down when shared edits dir is inaccessible
[ https://issues.apache.org/jira/browse/HDFS-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2912: - Attachment: HDFS-2909.HDFS-1623.patch Attached patch that implements the changed proposed in the previous comment. Since the patch calls Runtime.exit(1) I dont know of any way to test it other than the manual test. > HA: Namenode not shutting down when shared edits dir is inaccessible > > > Key: HDFS-2912 > URL: https://issues.apache.org/jira/browse/HDFS-2912 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2909.HDFS-1623.patch > > > When there is an error in shared edits dir then current policy requires the > active name node to abort and shutdown. > Currently there is no way to shut down the name node and hence this does not > happen even after all journals have been aborted on error. In fact the name > node stays Active and also is not in safe mode. Ideally it should shut down, > or at least go into safe mode or standby mode. -- 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-2905) HA: Standby NN NPE when shared edits dir is deleted
[ https://issues.apache.org/jira/browse/HDFS-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2905: - Summary: HA: Standby NN NPE when shared edits dir is deleted (was: Standby NN NPE when shared edits dir is deleted) > HA: Standby NN NPE when shared edits dir is deleted > --- > > Key: HDFS-2905 > URL: https://issues.apache.org/jira/browse/HDFS-2905 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2905.HDFS-1623.patch, HDFS-2905.HDFS-1623.patch > > -- 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-2902) HA: Allow new shared edit logs dir to be configured while NN is running
[ https://issues.apache.org/jira/browse/HDFS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2902: - Summary: HA: Allow new shared edit logs dir to be configured while NN is running (was: Allow new shared edit logs dir to be configured while NN is running) > HA: Allow new shared edit logs dir to be configured while NN is running > --- > > Key: HDFS-2902 > URL: https://issues.apache.org/jira/browse/HDFS-2902 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > -- 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-2905) Standby NN NPE when shared edits dir is deleted
[ https://issues.apache.org/jira/browse/HDFS-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2905: - Attachment: HDFS-2905.HDFS-1623.patch I added a helper wrapper around matchEditLogs (File) that takes the dir as input and get the file list on its own. Most use cases were of this kind and it made sense to not have to repeat the file list code everywhere. Added a unit test to make sure IOException is thrown for invalid dirs. Changed another test util to use the new wrapper and verify the new code path to the actual matchEditLogs(File []). > Standby NN NPE when shared edits dir is deleted > --- > > Key: HDFS-2905 > URL: https://issues.apache.org/jira/browse/HDFS-2905 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2905.HDFS-1623.patch, HDFS-2905.HDFS-1623.patch > > -- 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-2905) Standby NN NPE when shared edits dir is deleted
[ https://issues.apache.org/jira/browse/HDFS-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2905: - Attachment: HDFS-2905.HDFS-1623.patch Simple patch for the NPE added to both places where java.io.listFiles is used. > Standby NN NPE when shared edits dir is deleted > --- > > Key: HDFS-2905 > URL: https://issues.apache.org/jira/browse/HDFS-2905 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2905.HDFS-1623.patch > > -- 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-2902) Allow new shared edit logs dir to be configured while NN is running
[ https://issues.apache.org/jira/browse/HDFS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2902: - Summary: Allow new shared edit logs dir to be configured while NN is running (was: Allow new edit logs dir to be configured while NN is running) > Allow new shared edit logs dir to be configured while NN is running > --- > > Key: HDFS-2902 > URL: https://issues.apache.org/jira/browse/HDFS-2902 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha > -- 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-2863) Failures observed if dfs.edits.dir and shared.edits.dir have same directories.
[ https://issues.apache.org/jira/browse/HDFS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2863: - Attachment: HDFS-2863.HDFS-1623.patch Got it after a git pull. Attached. > Failures observed if dfs.edits.dir and shared.edits.dir have same directories. > -- > > Key: HDFS-2863 > URL: https://issues.apache.org/jira/browse/HDFS-2863 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Jitendra Nath Pandey >Assignee: Bikas Saha > Attachments: HDFS-2863.HDFS-1623.patch, HDFS-2863.HDFS-1623.patch, > HDFS-2863.HDFS-1623.patch, HDFS-2863.HDFS-1623.patch, > HDFS-2863.HDFS-1623.patch > > > If same edits directory is configured in twice, both are treated > independently. Edit log roll is called on the same directory twice causing > exceptions. -- 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-2863) Failures observed if dfs.edits.dir and shared.edits.dir have same directories.
[ https://issues.apache.org/jira/browse/HDFS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2863: - Attachment: HDFS-2863.HDFS-1623.patch I split the tests and renamed the one with shared edits to contain HA in the name. I did not find a TestHAConfiguration in the source code. > Failures observed if dfs.edits.dir and shared.edits.dir have same directories. > -- > > Key: HDFS-2863 > URL: https://issues.apache.org/jira/browse/HDFS-2863 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Jitendra Nath Pandey >Assignee: Bikas Saha > Attachments: HDFS-2863.HDFS-1623.patch, HDFS-2863.HDFS-1623.patch, > HDFS-2863.HDFS-1623.patch, HDFS-2863.HDFS-1623.patch > > > If same edits directory is configured in twice, both are treated > independently. Edit log roll is called on the same directory twice causing > exceptions. -- 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-2863) Failures observed if dfs.edits.dir and shared.edits.dir have same directories.
[ https://issues.apache.org/jira/browse/HDFS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2863: - Attachment: HDFS-2863.HDFS-1623.patch new patch. > Failures observed if dfs.edits.dir and shared.edits.dir have same directories. > -- > > Key: HDFS-2863 > URL: https://issues.apache.org/jira/browse/HDFS-2863 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Jitendra Nath Pandey >Assignee: Bikas Saha > Attachments: HDFS-2863.HDFS-1623.patch, HDFS-2863.HDFS-1623.patch, > HDFS-2863.HDFS-1623.patch > > > If same edits directory is configured in twice, both are treated > independently. Edit log roll is called on the same directory twice causing > exceptions. -- 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-2863) Failures observed if dfs.edits.dir and shared.edits.dir have same directories.
[ https://issues.apache.org/jira/browse/HDFS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2863: - Attachment: HDFS-2863.HDFS-1623.patch Found Joiner on Google. Thanks anyways. Attached latest patch with test. > Failures observed if dfs.edits.dir and shared.edits.dir have same directories. > -- > > Key: HDFS-2863 > URL: https://issues.apache.org/jira/browse/HDFS-2863 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Jitendra Nath Pandey >Assignee: Bikas Saha > Attachments: HDFS-2863.HDFS-1623.patch, HDFS-2863.HDFS-1623.patch > > > If same edits directory is configured in twice, both are treated > independently. Edit log roll is called on the same directory twice causing > exceptions. -- 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-2863) Failures observed if dfs.edits.dir and shared.edits.dir have same directories.
[ https://issues.apache.org/jira/browse/HDFS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2863: - Attachment: HDFS-2863.HDFS-1623.patch Simple patch to fix the issue. Any existing tests I could change? > Failures observed if dfs.edits.dir and shared.edits.dir have same directories. > -- > > Key: HDFS-2863 > URL: https://issues.apache.org/jira/browse/HDFS-2863 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Jitendra Nath Pandey >Assignee: Bikas Saha > Attachments: HDFS-2863.HDFS-1623.patch > > > If same edits directory is configured in twice, both are treated > independently. Edit log roll is called on the same directory twice causing > exceptions. -- 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-2845) SBN should not allow browsing of the file system via web UI
[ https://issues.apache.org/jira/browse/HDFS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2845: - Attachment: HDFS-2485.HDFS-1623.patch Sorry about that. I missed Jitendra's comments in Gmails conversation view. Adding the license in this patch. > SBN should not allow browsing of the file system via web UI > --- > > Key: HDFS-2845 > URL: https://issues.apache.org/jira/browse/HDFS-2845 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2485.HDFS-1623.patch, HDFS-2485.HDFS-1623.patch, > HDFS-2485.HDFS-1623.patch, HDFS-2485.HDFS-1623.patch > > -- 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-2845) SBN should not allow browsing of the file system via web UI
[ https://issues.apache.org/jira/browse/HDFS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2845: - Attachment: HDFS-2485.HDFS-1623.patch New patch for review comments > SBN should not allow browsing of the file system via web UI > --- > > Key: HDFS-2845 > URL: https://issues.apache.org/jira/browse/HDFS-2845 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2485.HDFS-1623.patch, HDFS-2485.HDFS-1623.patch, > HDFS-2485.HDFS-1623.patch > > -- 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-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2859: - Attachment: HDFS-2859.HDFS-1623.patch Attaching a patch with a simple fix for the NPE. A general question I have is whether it is ok for certain name node hosts to be unresolved during startup. I guess it might be ok because some machines might legitimately be out of service and disconnected from the network. > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Attachments: HDFS-2859.HDFS-1623.patch > > -- 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-2845) SBN should not allow browsing of the file system via web UI
[ https://issues.apache.org/jira/browse/HDFS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2845: - Attachment: HDFS-2485.HDFS-1623.patch Added new patch with test. > SBN should not allow browsing of the file system via web UI > --- > > Key: HDFS-2845 > URL: https://issues.apache.org/jira/browse/HDFS-2845 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2485.HDFS-1623.patch, HDFS-2485.HDFS-1623.patch > > -- 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-2845) SBN should not allow browsing of the file system via web UI
[ https://issues.apache.org/jira/browse/HDFS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2845: - Attachment: HDFS-2485.HDFS-1623.patch Attached the simple patch for this. Is anyone aware of any UI tests that I could change for this. I tested it manually on local box name node. > SBN should not allow browsing of the file system via web UI > --- > > Key: HDFS-2845 > URL: https://issues.apache.org/jira/browse/HDFS-2845 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: HDFS-2485.HDFS-1623.patch > > -- 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-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2859: - Priority: Minor (was: Major) > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > -- 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-2858) DFSUtil.getSuffixIDs silently ignores exception in NetUtils.createSocketAddr
[ https://issues.apache.org/jira/browse/HDFS-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2858: - Priority: Minor (was: Major) > DFSUtil.getSuffixIDs silently ignores exception in NetUtils.createSocketAddr > > > Key: HDFS-2858 > URL: https://issues.apache.org/jira/browse/HDFS-2858 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > -- 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-2845) SBN should not allow browsing of the file system via web UI
[ https://issues.apache.org/jira/browse/HDFS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated HDFS-2845: - Summary: SBN should not allow browsing of the file system via web UI (was: SBN should not allow browsing of the file system) > SBN should not allow browsing of the file system via web UI > --- > > Key: HDFS-2845 > URL: https://issues.apache.org/jira/browse/HDFS-2845 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha > -- 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 Fixed review comments > 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, HDFS-2681.HDFS-1623.patch, > HDFS-2681.HDFS-1623.patch, HDFS-2681.HDFS-1623.patch, HDFS-2681.txt, > 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 Sorry for the spam. There were some unsupported characters that somehow showed up only when building from the top level hadoop project. Fixing that and adding some more comments. > 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, 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 functional test using real ZooKeeper server. > 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, 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 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-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 Uploading new patch that address review comments. > 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, 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 new patch will all changes > 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, 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 Patch that takes care of review comments. > 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, 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 New patch with inconsistent names fixed across comments and code. > 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, > 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 Zookeeper based Leader Election and Monitoring Library.pdf Hi, I have submitted a short design document for this library and a patch that implements the functionality. Both are up for review and comments. Thanks > 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, 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: - Assignee: Bikas Saha (was: Suresh Srinivas) > 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) > > > 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
