[jira] [Commented] (HDFS-667) test-contrib target fails on hdfsproxy tests
[ https://issues.apache.org/jira/browse/HDFS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161454#comment-13161454 ] Matt Foley commented on HDFS-667: - Note HDFS-2210 was applied only to trunk and 22, not 20 where this bug relates. > test-contrib target fails on hdfsproxy tests > > > Key: HDFS-667 > URL: https://issues.apache.org/jira/browse/HDFS-667 > Project: Hadoop HDFS > Issue Type: Bug > Components: contrib/hdfsproxy >Reporter: Giridharan Kesavan > Attachments: hdfs-667.patch > > > hdfsproxy test fails only on hadoop-20 branch. > http://hudson.zones.apache.org/hudson/view/Hadoop/job/Hadoop-20-Build/33/console -- 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-2617) Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution
[ https://issues.apache.org/jira/browse/HDFS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161373#comment-13161373 ] Jakob Homan commented on HDFS-2617: --- I seem to remember this idea coming up during initial development and being rejected, but I don't remember why. Does anyone? > Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution > -- > > Key: HDFS-2617 > URL: https://issues.apache.org/jira/browse/HDFS-2617 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jakob Homan >Assignee: Jakob Homan > > The current approach to secure and authenticate nn web services is based on > Kerberized SSL and was developed when a SPNEGO solution wasn't available. Now > that we have one, we can get rid of the non-standard KSSL and use SPNEGO > throughout. This will simplify setup and configuration. Also, Kerberized > SSL is a non-standard approach with its own quirks and dark corners > (HDFS-2386). -- 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-2617) Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution
[ https://issues.apache.org/jira/browse/HDFS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161352#comment-13161352 ] Aaron T. Myers commented on HDFS-2617: -- Hey Jakob, I think getting rid of KSSL (e.g. replacing it with SPNEGO) would be a huge improvement. But, I'd like to propose an alternate design which should be just as secure, and potentially simpler to implement. Given that a checkpoint by the 2NN already has to do a few RPCs before the transfer of the fsimage/edits (to, e.g. initiate an edits log roll), we could easily generate a shared secret token between the NN and 2NN in this RPC, which then could be included as a URL parameter during the fsimage/edits transfers over HTTP. I suspect this will be easier to implement, is just as secure as SPNEGO/KSSL since when security is enabled the RPCs creating the secret token will be authenticated, and has the advantage of making checkpoints execute the same code paths with or without security enabled. Thoughts? > Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution > -- > > Key: HDFS-2617 > URL: https://issues.apache.org/jira/browse/HDFS-2617 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jakob Homan >Assignee: Jakob Homan > > The current approach to secure and authenticate nn web services is based on > Kerberized SSL and was developed when a SPNEGO solution wasn't available. Now > that we have one, we can get rid of the non-standard KSSL and use SPNEGO > throughout. This will simplify setup and configuration. Also, Kerberized > SSL is a non-standard approach with its own quirks and dark corners > (HDFS-2386). -- 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-1972) HA: Datanode fencing mechanism
[ https://issues.apache.org/jira/browse/HDFS-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1972: -- Attachment: hdfs-1972-v1.txt Here's some initial work on this JIRA - the NNs return their HA state in the heartbeat, and the DNs use that to determine which is active. I may break this out to a separate JIRA for commit so that the patches are manageable to review. Still need to implement the rest of the above proposal. > HA: Datanode fencing mechanism > -- > > Key: HDFS-1972 > URL: https://issues.apache.org/jira/browse/HDFS-1972 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, name-node >Reporter: Suresh Srinivas >Assignee: Todd Lipcon > Attachments: hdfs-1972-v1.txt > > > In high availability setup, with an active and standby namenode, there is a > possibility of two namenodes sending commands to the datanode. The datanode > must honor commands from only the active namenode and reject the commands > from standby, to prevent corruption. This invariant must be complied with > during fail over and other states such as split brain. This jira addresses > issues related to this, design of the solution and implementation. -- 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-1972) HA: Datanode fencing mechanism
[ https://issues.apache.org/jira/browse/HDFS-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161329#comment-13161329 ] dhruba borthakur commented on HDFS-1972: I recollect that we prevent primary namenode from issuing BLOCK_INVALIDATE commands for a particular datanode until the time it has received a full block report from that datanode (since the last failover event). But I will read proposal 3 in greater detail, > HA: Datanode fencing mechanism > -- > > Key: HDFS-1972 > URL: https://issues.apache.org/jira/browse/HDFS-1972 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, name-node >Reporter: Suresh Srinivas >Assignee: Todd Lipcon > > In high availability setup, with an active and standby namenode, there is a > possibility of two namenodes sending commands to the datanode. The datanode > must honor commands from only the active namenode and reject the commands > from standby, to prevent corruption. This invariant must be complied with > during fail over and other states such as split brain. This jira addresses > issues related to this, design of the solution and implementation. -- 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-1108) Log newly allocated blocks
[ https://issues.apache.org/jira/browse/HDFS-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161325#comment-13161325 ] Hadoop QA commented on HDFS-1108: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505835/hdfs-1108-habranch.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1627//console This message is automatically generated. > Log newly allocated blocks > -- > > Key: HDFS-1108 > URL: https://issues.apache.org/jira/browse/HDFS-1108 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Reporter: dhruba borthakur >Assignee: Todd Lipcon > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-1108.patch, hdfs-1108-habranch.txt, > hdfs-1108-habranch.txt, hdfs-1108-habranch.txt, hdfs-1108-habranch.txt, > hdfs-1108.txt > > > The current HDFS design says that newly allocated blocks for a file are not > persisted in the NN transaction log when the block is allocated. Instead, a > hflush() or a close() on the file persists the blocks into the transaction > log. It would be nice if we can immediately persist newly allocated blocks > (as soon as they are allocated) for specific files. -- 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-1765) Block Replication should respect under-replication block priority
[ https://issues.apache.org/jira/browse/HDFS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161322#comment-13161322 ] Tsz Wo (Nicholas), SZE commented on HDFS-1765: -- Hi Uma, the proposed solution sounds good. Having an index for each priority will solve the problem. BTW, chooseUnderReplicatedBlocks(..) and replIndex in BlockManager should be moved to UnderReplicatedBlocks. > Block Replication should respect under-replication block priority > - > > Key: HDFS-1765 > URL: https://issues.apache.org/jira/browse/HDFS-1765 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node >Affects Versions: 0.23.0 >Reporter: Hairong Kuang >Assignee: Hairong Kuang > Fix For: 0.24.0 > > Attachments: HDFS-1765.pdf, underReplicatedQueue.pdf > > > Currently under-replicated blocks are assigned different priorities depending > on how many replicas a block has. However the replication monitor works on > blocks in a round-robin fashion. So the newly added high priority blocks > won't get replicated until all low-priority blocks are done. One example is > that on decommissioning datanode WebUI we often observe that "blocks with > only decommissioning replicas" do not get scheduled to replicate before other > blocks, so risking data availability if the node is shutdown for repair > before decommission completes. -- 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-2616) Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse
[ https://issues.apache.org/jira/browse/HDFS-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2616. --- Resolution: Fixed Committed hdfs-2616-addendum.txt as r1209315. > Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse > - > > Key: HDFS-2616 > URL: https://issues.apache.org/jira/browse/HDFS-2616 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, > HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, hdfs-2616-addendum.txt > > > DatanodeProtocol#sendHeartbeat() returns DatanodeCommand[]. This jira > proposes changing it to to return HeartbeatResponse that has > DatanodeCommand[]. This allows adding other information that can be returned > by the namenode to the datanode, instead of having to only return > DatanodeCommand[]. For relevant discussion see HDFS-1972. -- 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-1108) Log newly allocated blocks
[
https://issues.apache.org/jira/browse/HDFS-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-1108:
-
Attachment: hdfs-1108-habranch.txt
Here's an updated patch which adds back in the {{dfs.persist.blocks}} config
and changes the test to use it. Persistence of blocks is also enabled
automatically in the case HA is enabled with shared edits dir, regardless of
the value of {{dfs.persist.blocks}}.
> Log newly allocated blocks
> --
>
> Key: HDFS-1108
> URL: https://issues.apache.org/jira/browse/HDFS-1108
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
>Reporter: dhruba borthakur
>Assignee: Todd Lipcon
> Fix For: HA branch (HDFS-1623)
>
> Attachments: HDFS-1108.patch, hdfs-1108-habranch.txt,
> hdfs-1108-habranch.txt, hdfs-1108-habranch.txt, hdfs-1108-habranch.txt,
> hdfs-1108.txt
>
>
> The current HDFS design says that newly allocated blocks for a file are not
> persisted in the NN transaction log when the block is allocated. Instead, a
> hflush() or a close() on the file persists the blocks into the transaction
> log. It would be nice if we can immediately persist newly allocated blocks
> (as soon as they are allocated) for specific files.
--
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] [Assigned] (HDFS-1842) Cannot upgrade 0.20.203 to 0.21 with an editslog present
[ https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins reassigned HDFS-1842: - Assignee: Suresh Srinivas > Cannot upgrade 0.20.203 to 0.21 with an editslog present > > > Key: HDFS-1842 > URL: https://issues.apache.org/jira/browse/HDFS-1842 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Affects Versions: 0.20.203.0 >Reporter: Allen Wittenauer >Assignee: Suresh Srinivas >Priority: Blocker > Attachments: HDFS-1842.rel203.patch, HDFS-1842.rel204.2.patch, > HDFS-1842.rel204.3.patch, HDFS-1842.rel204.patch > > > If a user installs 0.20.203 and then upgrades to 0.21 with an editslog > present, 0.21 will corrupt the file system due to opcode re-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-1842) Cannot upgrade 0.20.203 to 0.21 with an editslog present
[ https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-1842: -- Release Note: (was: I committed the patch. Konstantin, I wanted to commit this patch, as soon as possible. Please do review and let me know your feedback. I will open another jira to take care of the comments, if there are any.) > Cannot upgrade 0.20.203 to 0.21 with an editslog present > > > Key: HDFS-1842 > URL: https://issues.apache.org/jira/browse/HDFS-1842 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node >Affects Versions: 0.20.203.0 >Reporter: Allen Wittenauer >Priority: Blocker > Attachments: HDFS-1842.rel203.patch, HDFS-1842.rel204.2.patch, > HDFS-1842.rel204.3.patch, HDFS-1842.rel204.patch > > > If a user installs 0.20.203 and then upgrades to 0.21 with an editslog > present, 0.21 will corrupt the file system due to opcode re-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-2616) Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse
[ https://issues.apache.org/jira/browse/HDFS-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2616: -- Attachment: hdfs-2616-addendum.txt Needed a slight addendum here for the mocking of DatanodeProtocol in TestBPOfferService. It was previously returning null which was treated as "no commands", but now that triggers an NPE in the tests. I'll commit this trivial fix in a few minutes. > Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse > - > > Key: HDFS-2616 > URL: https://issues.apache.org/jira/browse/HDFS-2616 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, > HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, hdfs-2616-addendum.txt > > > DatanodeProtocol#sendHeartbeat() returns DatanodeCommand[]. This jira > proposes changing it to to return HeartbeatResponse that has > DatanodeCommand[]. This allows adding other information that can be returned > by the namenode to the datanode, instead of having to only return > DatanodeCommand[]. For relevant discussion see HDFS-1972. -- 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] [Reopened] (HDFS-2616) Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse
[ https://issues.apache.org/jira/browse/HDFS-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reopened HDFS-2616: --- > Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse > - > > Key: HDFS-2616 > URL: https://issues.apache.org/jira/browse/HDFS-2616 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, > HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, hdfs-2616-addendum.txt > > > DatanodeProtocol#sendHeartbeat() returns DatanodeCommand[]. This jira > proposes changing it to to return HeartbeatResponse that has > DatanodeCommand[]. This allows adding other information that can be returned > by the namenode to the datanode, instead of having to only return > DatanodeCommand[]. For relevant discussion see HDFS-1972. -- 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-1580) Add interface for generic Write Ahead Logging mechanisms
[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161254#comment-13161254 ] Hadoop QA commented on HDFS-1580: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505819/HDFS-1580.diff against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hdfs.TestDistributedFileSystem org.apache.hadoop.hdfs.TestConnCache org.apache.hadoop.hdfs.server.namenode.TestParallelImageWrite org.apache.hadoop.hdfs.TestSafeMode org.apache.hadoop.hdfs.server.datanode.TestDataNodeExit org.apache.hadoop.hdfs.server.namenode.TestHDFSConcat org.apache.hadoop.hdfs.TestFileAppend org.apache.hadoop.hdfs.TestDatanodeDeath org.apache.hadoop.hdfs.server.namenode.TestFileLimit org.apache.hadoop.hdfs.TestLease org.apache.hadoop.hdfs.TestShortCircuitLocalRead org.apache.hadoop.hdfs.TestDFSRename org.apache.hadoop.hdfs.TestPipelines org.apache.hadoop.hdfs.TestSetrepDecreasing org.apache.hadoop.hdfs.TestLeaseRecovery2 org.apache.hadoop.hdfs.TestFileAppend2 org.apache.hadoop.security.TestRefreshUserMappings org.apache.hadoop.hdfs.server.datanode.TestRefreshNamenodes org.apache.hadoop.hdfs.TestHFlush org.apache.hadoop.hdfs.TestLeaseRecovery org.apache.hadoop.hdfs.web.TestWebHdfsFileSystemContract org.apache.hadoop.fs.loadGenerator.TestLoadGenerator org.apache.hadoop.hdfs.server.datanode.TestMulitipleNNDataBlockScanner org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount org.apache.hadoop.fs.TestGlobPaths org.apache.hadoop.hdfs.server.namenode.TestBlockUnderConstruction org.apache.hadoop.fs.TestResolveHdfsSymlink org.apache.hadoop.hdfs.TestFileCreationNamenodeRestart org.apache.hadoop.hdfs.server.namenode.TestListCorruptFileBlocks org.apache.hadoop.hdfs.server.namenode.TestCheckPointForSecurityTokens org.apache.hadoop.hdfs.TestDfsOverAvroRpc org.apache.hadoop.hdfs.server.blockmanagement.TestReplicationPolicy org.apache.hadoop.hdfs.server.datanode.TestDeleteBlockPool org.apache.hadoop.hdfs.server.namenode.TestStorageRestore org.apache.hadoop.hdfs.server.namenode.TestNameNodeResourceChecker org.apache.hadoop.hdfs.TestAbandonBlock org.apache.hadoop.fs.TestUrlStreamHandler org.apache.hadoop.hdfs.server.namenode.TestTransferFsImage org.apache.hadoop.hdfs.TestBlockMissingException org.apache.hadoop.fs.viewfs.TestViewFsFileStatusHdfs org.apache.hadoop.hdfs.TestClientReportBadBlock org.apache.hadoop.hdfs.TestDFSShell org.apache.hadoop.hdfs.server.datanode.TestDataNodeMultipleRegistrations org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure org.apache.hadoop.hdfs.server.namenode.TestProcessCorruptBlocks org.apache.hadoop.hdfs.TestFileCreation org.apache.hadoop.fs.TestFcHdfsPermission org.apache.hadoop.hdfs.TestCrcCorruption org.apache.hadoop.hdfs.server.namenode.TestNamenodeCapacityReport org.apache.hadoop.hdfs.TestListFilesInFileContext org.apache.hadoop.hdfs.server.datanode.TestBlockReplacement org.apache.hadoop.hdfs.server.namenode.TestNameEditsConfigs org.apache.hadoop.hdfs.TestListPathServlet org.apache.hadoop.hdfs.TestMultiThreadedHflush org.apache.hadoop.hdfs.TestDFSFinalize org.apache.hadoop.hdfs.TestLocalDFS org.apache.hadoop.hdfs.server.namenode.TestBackupNode org.apache.hadoop.hdfs.TestSeekBug org.apache.hadoop.hdfs.TestDFSStartupVersi
[jira] [Updated] (HDFS-1580) Add interface for generic Write Ahead Logging mechanisms
[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-1580: - Attachment: HDFS-1580.diff > Add interface for generic Write Ahead Logging mechanisms > > > Key: HDFS-1580 > URL: https://issues.apache.org/jira/browse/HDFS-1580 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Ivan Kelly >Assignee: Jitendra Nath Pandey > Fix For: HA branch (HDFS-1623), 0.24.0 > > Attachments: EditlogInterface.1.pdf, EditlogInterface.2.pdf, > EditlogInterface.3.pdf, HDFS-1580+1521.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, generic_wal_iface.pdf, generic_wal_iface.pdf, > generic_wal_iface.pdf, generic_wal_iface.txt > > -- 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-1580) Add interface for generic Write Ahead Logging mechanisms
[
https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161234#comment-13161234
]
Ivan Kelly commented on HDFS-1580:
--
I couldn't find any, but multiple reruns of it and the surrounding tests didnt
have any fails :/
{code}
Running org.apache.hadoop.hdfs.TestMissingBlocksAlert
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.422 sec
Running org.apache.hadoop.hdfs.TestDecommission
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 172.954 sec
Running org.apache.hadoop.hdfs.TestAppendDifferentChecksum
Tests run: 3, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 7.52 sec
Running org.apache.hadoop.hdfs.TestBlocksScheduledCounter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.017 sec
Running org.apache.hadoop.hdfs.server.namenode.TestGenericJournalConf
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.41 sec
{code}
Im going to reupload the patch to kick off tests again.
> Add interface for generic Write Ahead Logging mechanisms
>
>
> Key: HDFS-1580
> URL: https://issues.apache.org/jira/browse/HDFS-1580
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Ivan Kelly
>Assignee: Jitendra Nath Pandey
> Fix For: HA branch (HDFS-1623), 0.24.0
>
> Attachments: EditlogInterface.1.pdf, EditlogInterface.2.pdf,
> EditlogInterface.3.pdf, HDFS-1580+1521.diff, HDFS-1580.diff, HDFS-1580.diff,
> HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff,
> HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff,
> HDFS-1580.diff, generic_wal_iface.pdf, generic_wal_iface.pdf,
> generic_wal_iface.pdf, generic_wal_iface.txt
>
>
--
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-2623) HA: Add test case for hot standby capability
[ https://issues.apache.org/jira/browse/HDFS-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2623. --- Resolution: Fixed Fix Version/s: HA branch (HDFS-1623) Hadoop Flags: Reviewed Committed the failing test case so we can all share it while working towards getting the hot-standby in working shape. > HA: Add test case for hot standby capability > > > Key: HDFS-2623 > URL: https://issues.apache.org/jira/browse/HDFS-2623 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Fix For: HA branch (HDFS-1623) > > Attachments: hdfs-2623.txt > > > Putting up a fairly simple test case I wrote that verifies that the standby > is kept "hot" -- 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-2612) HA: handle refreshNameNodes in federated HA clusters
[
https://issues.apache.org/jira/browse/HDFS-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HDFS-2612.
---
Resolution: Fixed
Fix Version/s: HA branch (HDFS-1623)
Hadoop Flags: Reviewed
Committed to branch, thanks for the review.
> HA: handle refreshNameNodes in federated HA clusters
>
>
> Key: HDFS-2612
> URL: https://issues.apache.org/jira/browse/HDFS-2612
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: data-node, ha
>Affects Versions: HA branch (HDFS-1623)
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
> Fix For: HA branch (HDFS-1623)
>
> Attachments: hdfs-2612.txt, hdfs-2612.txt
>
>
> For expediency in HDFS-1971 we've commented out the {{refreshNameNodes}}
> function temporarily on branch. Need to fix that code to handle refresh with
> HA.
--
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-776) Fix exception handling in Balancer
[
https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161182#comment-13161182
]
Hadoop QA commented on HDFS-776:
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505799/HDFS-776.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 did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.server.datanode.TestMulitipleNNDataBlockScanner
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/1625//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/1625//artifact/trunk/hadoop-hdfs-project/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1625//console
This message is automatically generated.
> Fix exception handling in Balancer
> --
>
> Key: HDFS-776
> URL: https://issues.apache.org/jira/browse/HDFS-776
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
>Reporter: Owen O'Malley
>Assignee: Uma Maheswara Rao G
>Priority: Critical
> Attachments: HDFS-776.0.patch, HDFS-776.patch
>
>
> The Balancer's AccessKeyUpdater handles exceptions badly. In particular:
> 1. Catching Exception too low. The wrapper around setKeys should only catch
> IOException.
> 2. InterruptedException is ignored. It should be caught at the top level and
> exit run.
> 3. Throwable is not caught. It should be caught at the top level and kill the
> Balancer server process.
> {code}
> class AccessKeyUpdater implements Runnable {
> public void run() {
> while (shouldRun) {
> try {
> accessTokenHandler.setKeys(namenode.getAccessKeys());
> } catch (Exception e) {
> LOG.error(StringUtils.stringifyException(e));
> }
> try {
> Thread.sleep(keyUpdaterInterval);
> } catch (InterruptedException ie) {
> }
> }
> }
> }
> {code}
--
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-2612) HA: handle refreshNameNodes in federated HA clusters
[
https://issues.apache.org/jira/browse/HDFS-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161179#comment-13161179
]
Eli Collins commented on HDFS-2612:
---
+1 lgtm
> HA: handle refreshNameNodes in federated HA clusters
>
>
> Key: HDFS-2612
> URL: https://issues.apache.org/jira/browse/HDFS-2612
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: data-node, ha
>Affects Versions: HA branch (HDFS-1623)
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
> Attachments: hdfs-2612.txt, hdfs-2612.txt
>
>
> For expediency in HDFS-1971 we've commented out the {{refreshNameNodes}}
> function temporarily on branch. Need to fix that code to handle refresh with
> HA.
--
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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1685: - Issue Type: Task (was: Sub-task) Parent: (was: HDFS-1052) > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Task > Components: documentation >Affects Versions: 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h1685_20111201.patch, h1685_20111201b.patch, screenshot > for the updated cli doc.jpg > > > Update Balancer documentation for the new balancing policy and CLI. -- 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-2623) HA: Add test case for hot standby capability
[ https://issues.apache.org/jira/browse/HDFS-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161163#comment-13161163 ] Aaron T. Myers commented on HDFS-2623: -- +1, the test looks good to me. I think we might as well commit this now even if it doesn't yet pass. Agreed? > HA: Add test case for hot standby capability > > > Key: HDFS-2623 > URL: https://issues.apache.org/jira/browse/HDFS-2623 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Attachments: hdfs-2623.txt > > > Putting up a fairly simple test case I wrote that verifies that the standby > is kept "hot" -- 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-2622) HA: fix TestDFSUpgrade on HA branch
[ https://issues.apache.org/jira/browse/HDFS-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2622. --- Resolution: Fixed Fix Version/s: HA branch (HDFS-1623) Hadoop Flags: Reviewed Committed, thanks Eli. > HA: fix TestDFSUpgrade on HA branch > --- > > Key: HDFS-2622 > URL: https://issues.apache.org/jira/browse/HDFS-2622 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: HA branch (HDFS-1623) > > Attachments: hdfs-2622.txt > > > Since HDFS-1975, we now increment the generation stamp for each block > allocation. So the EXPECTED_TXID constant is wrong now in TestDFSUpgrade, > since we do twice as many txns while creating files in the first phase of the > test. -- 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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161131#comment-13161131 ] Uma Maheswara Rao G commented on HDFS-1685: --- +1, looks good. > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, documentation >Affects Versions: Federation Branch, 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h1685_20111201.patch, h1685_20111201b.patch, screenshot > for the updated cli doc.jpg > > > Update Balancer documentation for the new balancing policy and CLI. -- 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-2623) HA: Add test case for hot standby capability
[ https://issues.apache.org/jira/browse/HDFS-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2623: -- Attachment: hdfs-2623.txt Here's the test case. It doesn't currently pass due to some of the other open JIRAs that are still in flight, but will be useful for testing those JIRAs as they progress. > HA: Add test case for hot standby capability > > > Key: HDFS-2623 > URL: https://issues.apache.org/jira/browse/HDFS-2623 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon > Attachments: hdfs-2623.txt > > > Putting up a fairly simple test case I wrote that verifies that the standby > is kept "hot" -- 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-2623) HA: Add test case for hot standby capability
[ https://issues.apache.org/jira/browse/HDFS-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2623: -- Description: Putting up a fairly simple test case I wrote that verifies that the standby is kept "hot" (was: Putting up a fairly test case I wrote that verifies that the standby is kept "hot") > HA: Add test case for hot standby capability > > > Key: HDFS-2623 > URL: https://issues.apache.org/jira/browse/HDFS-2623 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon > > Putting up a fairly simple test case I wrote that verifies that the standby > is kept "hot" -- 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-776) Fix exception handling in Balancer
[
https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161123#comment-13161123
]
Brock Noland commented on HDFS-776:
---
+1 patch looks good
> Fix exception handling in Balancer
> --
>
> Key: HDFS-776
> URL: https://issues.apache.org/jira/browse/HDFS-776
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
>Reporter: Owen O'Malley
>Assignee: Uma Maheswara Rao G
>Priority: Critical
> Attachments: HDFS-776.0.patch, HDFS-776.patch
>
>
> The Balancer's AccessKeyUpdater handles exceptions badly. In particular:
> 1. Catching Exception too low. The wrapper around setKeys should only catch
> IOException.
> 2. InterruptedException is ignored. It should be caught at the top level and
> exit run.
> 3. Throwable is not caught. It should be caught at the top level and kill the
> Balancer server process.
> {code}
> class AccessKeyUpdater implements Runnable {
> public void run() {
> while (shouldRun) {
> try {
> accessTokenHandler.setKeys(namenode.getAccessKeys());
> } catch (Exception e) {
> LOG.error(StringUtils.stringifyException(e));
> }
> try {
> Thread.sleep(keyUpdaterInterval);
> } catch (InterruptedException ie) {
> }
> }
> }
> }
> {code}
--
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-2623) HA: Add test case for hot standby capability
HA: Add test case for hot standby capability Key: HDFS-2623 URL: https://issues.apache.org/jira/browse/HDFS-2623 Project: Hadoop HDFS Issue Type: Sub-task Components: ha, test Affects Versions: HA branch (HDFS-1623) Reporter: Todd Lipcon Assignee: Todd Lipcon Putting up a fairly test case I wrote that verifies that the standby is kept "hot" -- 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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1316#comment-1316 ] Tsz Wo (Nicholas), SZE commented on HDFS-1685: -- See the attached screenshot for the updated cli doc. > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, documentation >Affects Versions: Federation Branch, 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h1685_20111201.patch, h1685_20111201b.patch, screenshot > for the updated cli doc.jpg > > > Update Balancer documentation for the new balancing policy and CLI. -- 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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1685: - Attachment: screenshot for the updated cli doc.jpg > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, documentation >Affects Versions: Federation Branch, 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h1685_20111201.patch, h1685_20111201b.patch, screenshot > for the updated cli doc.jpg > > > Update Balancer documentation for the new balancing policy and CLI. -- 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-776) Fix exception handling in Balancer
[
https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HDFS-776:
-
Assignee: Uma Maheswara Rao G
Status: Patch Available (was: Open)
> Fix exception handling in Balancer
> --
>
> Key: HDFS-776
> URL: https://issues.apache.org/jira/browse/HDFS-776
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
>Reporter: Owen O'Malley
>Assignee: Uma Maheswara Rao G
>Priority: Critical
> Attachments: HDFS-776.0.patch, HDFS-776.patch
>
>
> The Balancer's AccessKeyUpdater handles exceptions badly. In particular:
> 1. Catching Exception too low. The wrapper around setKeys should only catch
> IOException.
> 2. InterruptedException is ignored. It should be caught at the top level and
> exit run.
> 3. Throwable is not caught. It should be caught at the top level and kill the
> Balancer server process.
> {code}
> class AccessKeyUpdater implements Runnable {
> public void run() {
> while (shouldRun) {
> try {
> accessTokenHandler.setKeys(namenode.getAccessKeys());
> } catch (Exception e) {
> LOG.error(StringUtils.stringifyException(e));
> }
> try {
> Thread.sleep(keyUpdaterInterval);
> } catch (InterruptedException ie) {
> }
> }
> }
> }
> {code}
--
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-776) Fix exception handling in Balancer
[
https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161103#comment-13161103
]
Uma Maheswara Rao G commented on HDFS-776:
--
Patch looks good.
Updated patch removes the unnecessary stacktraces and updated the messages.
> Fix exception handling in Balancer
> --
>
> Key: HDFS-776
> URL: https://issues.apache.org/jira/browse/HDFS-776
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
>Reporter: Owen O'Malley
>Priority: Critical
> Attachments: HDFS-776.0.patch, HDFS-776.patch
>
>
> The Balancer's AccessKeyUpdater handles exceptions badly. In particular:
> 1. Catching Exception too low. The wrapper around setKeys should only catch
> IOException.
> 2. InterruptedException is ignored. It should be caught at the top level and
> exit run.
> 3. Throwable is not caught. It should be caught at the top level and kill the
> Balancer server process.
> {code}
> class AccessKeyUpdater implements Runnable {
> public void run() {
> while (shouldRun) {
> try {
> accessTokenHandler.setKeys(namenode.getAccessKeys());
> } catch (Exception e) {
> LOG.error(StringUtils.stringifyException(e));
> }
> try {
> Thread.sleep(keyUpdaterInterval);
> } catch (InterruptedException ie) {
> }
> }
> }
> }
> {code}
--
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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1685: - Attachment: h1685_20111201b.patch h1685_20111201b.patch: added some > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, documentation >Affects Versions: Federation Branch, 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h1685_20111201.patch, h1685_20111201b.patch > > > Update Balancer documentation for the new balancing policy and CLI. -- 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-776) Fix exception handling in Balancer
[
https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HDFS-776:
-
Attachment: HDFS-776.patch
> Fix exception handling in Balancer
> --
>
> Key: HDFS-776
> URL: https://issues.apache.org/jira/browse/HDFS-776
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
>Reporter: Owen O'Malley
>Priority: Critical
> Attachments: HDFS-776.0.patch, HDFS-776.patch
>
>
> The Balancer's AccessKeyUpdater handles exceptions badly. In particular:
> 1. Catching Exception too low. The wrapper around setKeys should only catch
> IOException.
> 2. InterruptedException is ignored. It should be caught at the top level and
> exit run.
> 3. Throwable is not caught. It should be caught at the top level and kill the
> Balancer server process.
> {code}
> class AccessKeyUpdater implements Runnable {
> public void run() {
> while (shouldRun) {
> try {
> accessTokenHandler.setKeys(namenode.getAccessKeys());
> } catch (Exception e) {
> LOG.error(StringUtils.stringifyException(e));
> }
> try {
> Thread.sleep(keyUpdaterInterval);
> } catch (InterruptedException ie) {
> }
> }
> }
> }
> {code}
--
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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1685: - Attachment: h1685_20111201.patch h1685_20111201.patch: updated the cli usage. > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, documentation >Affects Versions: Federation Branch, 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > Attachments: h1685_20111201.patch > > > Update Balancer documentation for the new balancing policy and CLI. -- 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-2622) HA: fix TestDFSUpgrade on HA branch
[ https://issues.apache.org/jira/browse/HDFS-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161081#comment-13161081 ] Eli Collins commented on HDFS-2622: --- +1 lgtm > HA: fix TestDFSUpgrade on HA branch > --- > > Key: HDFS-2622 > URL: https://issues.apache.org/jira/browse/HDFS-2622 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-2622.txt > > > Since HDFS-1975, we now increment the generation stamp for each block > allocation. So the EXPECTED_TXID constant is wrong now in TestDFSUpgrade, > since we do twice as many txns while creating files in the first phase of the > test. -- 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-2622) HA: fix TestDFSUpgrade on HA branch
[ https://issues.apache.org/jira/browse/HDFS-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2622: -- Attachment: hdfs-2622.txt > HA: fix TestDFSUpgrade on HA branch > --- > > Key: HDFS-2622 > URL: https://issues.apache.org/jira/browse/HDFS-2622 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, test >Affects Versions: HA branch (HDFS-1623) >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-2622.txt > > > Since HDFS-1975, we now increment the generation stamp for each block > allocation. So the EXPECTED_TXID constant is wrong now in TestDFSUpgrade, > since we do twice as many txns while creating files in the first phase of the > test. -- 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-2622) HA: fix TestDFSUpgrade on HA branch
HA: fix TestDFSUpgrade on HA branch --- Key: HDFS-2622 URL: https://issues.apache.org/jira/browse/HDFS-2622 Project: Hadoop HDFS Issue Type: Sub-task Components: ha, test Affects Versions: HA branch (HDFS-1623) Reporter: Todd Lipcon Assignee: Todd Lipcon Priority: Minor Since HDFS-1975, we now increment the generation stamp for each block allocation. So the EXPECTED_TXID constant is wrong now in TestDFSUpgrade, since we do twice as many txns while creating files in the first phase of the test. -- 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-2594) webhdfs HTTP API should implement getDelegationTokens() instead getDelegationToken()
[ https://issues.apache.org/jira/browse/HDFS-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161072#comment-13161072 ] Hadoop QA commented on HDFS-2594: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505793/h2594_20111201.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 8 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1624//console This message is automatically generated. > webhdfs HTTP API should implement getDelegationTokens() instead > getDelegationToken() > > > Key: HDFS-2594 > URL: https://issues.apache.org/jira/browse/HDFS-2594 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.24.0, 0.23.1 >Reporter: Alejandro Abdelnur >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2594_2030.patch, h2594_2030_no_apt.patch, > h2594_20111201.patch > > > The current API returns a single delegation token, that method from the > FileSystem API is deprecated in favor of the one that returns a list of > tokens. The HTTP API should implement the new/undeprecated signature > getDelegationTokens(). -- 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-2621) Balancer is not checking ALREADY_RUNNING state and never returns this state.
[
https://issues.apache.org/jira/browse/HDFS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161070#comment-13161070
]
Uma Maheswara Rao G commented on HDFS-2621:
---
since 'alredy running' check made in NameNodeConnector ctor.
{code}
// Check if there is another balancer running.
// Exit if there is another one running.
out = checkAndMarkRunningBalancer();
if (out == null) {
throw new IOException("Another balancer is running");
}
{code}
simply it is throwing IOException and will not return correct status.
> Balancer is not checking ALREADY_RUNNING state and never returns this state.
>
>
> Key: HDFS-2621
> URL: https://issues.apache.org/jira/browse/HDFS-2621
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
>Affects Versions: 0.24.0, 0.23.1
>Reporter: Uma Maheswara Rao G
>
--
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] [Assigned] (HDFS-2621) Balancer is not checking ALREADY_RUNNING state and never returns this state.
[ https://issues.apache.org/jira/browse/HDFS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G reassigned HDFS-2621: - Assignee: Uma Maheswara Rao G > Balancer is not checking ALREADY_RUNNING state and never returns this state. > > > Key: HDFS-2621 > URL: https://issues.apache.org/jira/browse/HDFS-2621 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer >Affects Versions: 0.24.0, 0.23.1 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > -- 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-2594) webhdfs HTTP API should implement getDelegationTokens() instead getDelegationToken()
[ https://issues.apache.org/jira/browse/HDFS-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2594: - Attachment: h2594_20111201.patch h2594_20111201.patch: revised the apt doc, no code changes. > webhdfs HTTP API should implement getDelegationTokens() instead > getDelegationToken() > > > Key: HDFS-2594 > URL: https://issues.apache.org/jira/browse/HDFS-2594 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 0.24.0, 0.23.1 >Reporter: Alejandro Abdelnur >Assignee: Tsz Wo (Nicholas), SZE >Priority: Critical > Attachments: h2594_2030.patch, h2594_2030_no_apt.patch, > h2594_20111201.patch > > > The current API returns a single delegation token, that method from the > FileSystem API is deprecated in favor of the one that returns a list of > tokens. The HTTP API should implement the new/undeprecated signature > getDelegationTokens(). -- 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-2620) commands_manual.html balancer documentation missing -policy option
[ https://issues.apache.org/jira/browse/HDFS-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161042#comment-13161042 ] Tsz Wo (Nicholas), SZE commented on HDFS-2620: -- Thomas and Uma, I will update the balancer doc soon. Thanks for checking it. > commands_manual.html balancer documentation missing -policy option > -- > > Key: HDFS-2620 > URL: https://issues.apache.org/jira/browse/HDFS-2620 > Project: Hadoop HDFS > Issue Type: Bug > Components: documentation >Affects Versions: 0.23.0 >Reporter: Thomas Graves > > the documentation for the balancer: commands_manual.html#balancer is > missing the -policy option that was added with federation. -- 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-1685) Federation: update Balancer documentation
[ https://issues.apache.org/jira/browse/HDFS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HDFS-1685: Affects Version/s: 0.23.0 > Federation: update Balancer documentation > - > > Key: HDFS-1685 > URL: https://issues.apache.org/jira/browse/HDFS-1685 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer, documentation >Affects Versions: Federation Branch, 0.23.0 >Reporter: Tsz Wo (Nicholas), SZE >Assignee: Tsz Wo (Nicholas), SZE > > Update Balancer documentation for the new balancing policy and CLI. -- 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-2620) commands_manual.html balancer documentation missing -policy option
[ https://issues.apache.org/jira/browse/HDFS-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161037#comment-13161037 ] Thomas Graves commented on HDFS-2620: - yes we can duplicate, sorry I didn't see that when doing quick search. > commands_manual.html balancer documentation missing -policy option > -- > > Key: HDFS-2620 > URL: https://issues.apache.org/jira/browse/HDFS-2620 > Project: Hadoop HDFS > Issue Type: Bug > Components: documentation >Affects Versions: 0.23.0 >Reporter: Thomas Graves > > the documentation for the balancer: commands_manual.html#balancer is > missing the -policy option that was added with federation. -- 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-2620) commands_manual.html balancer documentation missing -policy option
[ https://issues.apache.org/jira/browse/HDFS-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves resolved HDFS-2620. - Resolution: Duplicate duplicate of HDFS-1685 > commands_manual.html balancer documentation missing -policy option > -- > > Key: HDFS-2620 > URL: https://issues.apache.org/jira/browse/HDFS-2620 > Project: Hadoop HDFS > Issue Type: Bug > Components: documentation >Affects Versions: 0.23.0 >Reporter: Thomas Graves > > the documentation for the balancer: commands_manual.html#balancer is > missing the -policy option that was added with federation. -- 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-2621) Balancer is not checking ALREADY_RUNNING state and never returns this state.
Balancer is not checking ALREADY_RUNNING state and never returns this state. Key: HDFS-2621 URL: https://issues.apache.org/jira/browse/HDFS-2621 Project: Hadoop HDFS Issue Type: Bug Reporter: Uma Maheswara Rao G -- 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-2621) Balancer is not checking ALREADY_RUNNING state and never returns this state.
[ https://issues.apache.org/jira/browse/HDFS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-2621: -- Component/s: balancer Affects Version/s: 0.23.1 0.24.0 > Balancer is not checking ALREADY_RUNNING state and never returns this state. > > > Key: HDFS-2621 > URL: https://issues.apache.org/jira/browse/HDFS-2621 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer >Affects Versions: 0.24.0, 0.23.1 >Reporter: Uma Maheswara Rao G > -- 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-2620) commands_manual.html balancer documentation missing -policy option
[ https://issues.apache.org/jira/browse/HDFS-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161027#comment-13161027 ] Uma Maheswara Rao G commented on HDFS-2620: --- Thomas, i think -policy option added in Federation. Already there is one issue in Federation for Balancer documentation updation. https://issues.apache.org/jira/browse/HDFS-1685. May be can make it duplicate with that issue? > commands_manual.html balancer documentation missing -policy option > -- > > Key: HDFS-2620 > URL: https://issues.apache.org/jira/browse/HDFS-2620 > Project: Hadoop HDFS > Issue Type: Bug > Components: documentation >Affects Versions: 0.23.0 >Reporter: Thomas Graves > > the documentation for the balancer: commands_manual.html#balancer is > missing the -policy option that was added with federation. -- 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-2620) commands_manual.html balancer documentation missing -policy option
commands_manual.html balancer documentation missing -policy option -- Key: HDFS-2620 URL: https://issues.apache.org/jira/browse/HDFS-2620 Project: Hadoop HDFS Issue Type: Bug Components: documentation Affects Versions: 0.23.0 Reporter: Thomas Graves the documentation for the balancer: commands_manual.html#balancer is missing the -policy option that was added with federation. -- 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-1580) Add interface for generic Write Ahead Logging mechanisms
[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161016#comment-13161016 ] Todd Lipcon commented on HDFS-1580: --- Looks like TestDecommission timed out... is that timing out on trunk? > Add interface for generic Write Ahead Logging mechanisms > > > Key: HDFS-1580 > URL: https://issues.apache.org/jira/browse/HDFS-1580 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Ivan Kelly >Assignee: Jitendra Nath Pandey > Fix For: HA branch (HDFS-1623), 0.24.0 > > Attachments: EditlogInterface.1.pdf, EditlogInterface.2.pdf, > EditlogInterface.3.pdf, HDFS-1580+1521.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > generic_wal_iface.pdf, generic_wal_iface.pdf, generic_wal_iface.pdf, > generic_wal_iface.txt > > -- 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-2619) Remove my personal email address from the libhdfs build file.
[
https://issues.apache.org/jira/browse/HDFS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161014#comment-13161014
]
Eli Collins commented on HDFS-2619:
---
+1
> Remove my personal email address from the libhdfs build file.
> -
>
> Key: HDFS-2619
> URL: https://issues.apache.org/jira/browse/HDFS-2619
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
> Attachments: h-2619.patch
>
>
> When I first wrote the libhdfs autoconf/automake stuff, I incorrectly put my
> email address in the AC_INIT line, which means if something goes wrong, you
> get:
> {quote}
> > configure: WARNING: ## Report this to ##
> {quote}
--
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-2618) Implement protobuf service for NamenodeProtocol
[
https://issues.apache.org/jira/browse/HDFS-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161013#comment-13161013
]
Todd Lipcon commented on HDFS-2618:
---
{code}
- required BlockProto block = 1;// Block
- repeated DatanodeIDProto datanodeIDs = 2; // Datanodes with replicas of the
block
+ required BlockProto block = 1; // Block
+ repeated string datanodeIDs = 2; // Datanodes with replicas of the block
{code}
What's the reason for this change? Encapsulating the DNIDs has the nice
property that if we want to add extra flags about each location, it would be a
simple non-breaking change.
> Implement protobuf service for NamenodeProtocol
> ---
>
> Key: HDFS-2618
> URL: https://issues.apache.org/jira/browse/HDFS-2618
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: name-node
>Reporter: Suresh Srinivas
>Assignee: Suresh Srinivas
> Fix For: 0.24.0
>
> Attachments: HDFS-2618.txt, HDFS-2618.txt
>
>
> This jira adds implementation for NamenodeProtocol protobuf service along the
> same lines as HDFS-2181
--
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-2614) hadoop dist tarball is missing hdfs headers
[ https://issues.apache.org/jira/browse/HDFS-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161005#comment-13161005 ] Hudson commented on HDFS-2614: -- Integrated in Hadoop-Mapreduce-0.23-Commit #251 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/251/]) Merge -r 1208927:1208928 from trunk to branch. FIXES: HDFS-2614 tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1209163 Files : * /hadoop/common/branches/branch-0.23/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > hadoop dist tarball is missing hdfs headers > --- > > Key: HDFS-2614 > URL: https://issues.apache.org/jira/browse/HDFS-2614 > Project: Hadoop HDFS > Issue Type: Bug > Components: build >Affects Versions: 0.24.0, 0.23.1 >Reporter: Bruno Mahé >Assignee: Alejandro Abdelnur > Labels: bigtop > Fix For: 0.24.0, 0.23.1 > > Attachments: HDFS-2614.patch > > > It would be nice to provide hdfs header so one could easily write programs to > be linked against that library and access HDFS -- 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-2614) hadoop dist tarball is missing hdfs headers
[ https://issues.apache.org/jira/browse/HDFS-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160997#comment-13160997 ] Hudson commented on HDFS-2614: -- Integrated in Hadoop-Common-0.23-Commit #241 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/241/]) Merge -r 1208927:1208928 from trunk to branch. FIXES: HDFS-2614 tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1209163 Files : * /hadoop/common/branches/branch-0.23/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > hadoop dist tarball is missing hdfs headers > --- > > Key: HDFS-2614 > URL: https://issues.apache.org/jira/browse/HDFS-2614 > Project: Hadoop HDFS > Issue Type: Bug > Components: build >Affects Versions: 0.24.0, 0.23.1 >Reporter: Bruno Mahé >Assignee: Alejandro Abdelnur > Labels: bigtop > Fix For: 0.24.0, 0.23.1 > > Attachments: HDFS-2614.patch > > > It would be nice to provide hdfs header so one could easily write programs to > be linked against that library and access HDFS -- 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-2614) hadoop dist tarball is missing hdfs headers
[ https://issues.apache.org/jira/browse/HDFS-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160995#comment-13160995 ] Hudson commented on HDFS-2614: -- Integrated in Hadoop-Hdfs-0.23-Commit #238 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/238/]) Merge -r 1208927:1208928 from trunk to branch. FIXES: HDFS-2614 tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1209163 Files : * /hadoop/common/branches/branch-0.23/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > hadoop dist tarball is missing hdfs headers > --- > > Key: HDFS-2614 > URL: https://issues.apache.org/jira/browse/HDFS-2614 > Project: Hadoop HDFS > Issue Type: Bug > Components: build >Affects Versions: 0.24.0, 0.23.1 >Reporter: Bruno Mahé >Assignee: Alejandro Abdelnur > Labels: bigtop > Fix For: 0.24.0, 0.23.1 > > Attachments: HDFS-2614.patch > > > It would be nice to provide hdfs header so one could easily write programs to > be linked against that library and access HDFS -- 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] [Assigned] (HDFS-2617) Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution
[ https://issues.apache.org/jira/browse/HDFS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan reassigned HDFS-2617: - Assignee: Jakob Homan > Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution > -- > > Key: HDFS-2617 > URL: https://issues.apache.org/jira/browse/HDFS-2617 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Jakob Homan >Assignee: Jakob Homan > > The current approach to secure and authenticate nn web services is based on > Kerberized SSL and was developed when a SPNEGO solution wasn't available. Now > that we have one, we can get rid of the non-standard KSSL and use SPNEGO > throughout. This will simplify setup and configuration. Also, Kerberized > SSL is a non-standard approach with its own quirks and dark corners > (HDFS-2386). -- 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-2619) Remove my personal email address from the libhdfs build file.
[
https://issues.apache.org/jira/browse/HDFS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160988#comment-13160988
]
Hadoop QA commented on HDFS-2619:
-
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505776/h-2619.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 did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.TestLeaseRecovery2
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/1623//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1623//console
This message is automatically generated.
> Remove my personal email address from the libhdfs build file.
> -
>
> Key: HDFS-2619
> URL: https://issues.apache.org/jira/browse/HDFS-2619
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
> Attachments: h-2619.patch
>
>
> When I first wrote the libhdfs autoconf/automake stuff, I incorrectly put my
> email address in the AC_INIT line, which means if something goes wrong, you
> get:
> {quote}
> > configure: WARNING: ## Report this to ##
> {quote}
--
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-2619) Remove my personal email address from the libhdfs build file.
[
https://issues.apache.org/jira/browse/HDFS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HDFS-2619:
Status: Patch Available (was: Open)
> Remove my personal email address from the libhdfs build file.
> -
>
> Key: HDFS-2619
> URL: https://issues.apache.org/jira/browse/HDFS-2619
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
> Attachments: h-2619.patch
>
>
> When I first wrote the libhdfs autoconf/automake stuff, I incorrectly put my
> email address in the AC_INIT line, which means if something goes wrong, you
> get:
> {quote}
> > configure: WARNING: ## Report this to ##
> {quote}
--
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-2619) Remove my personal email address from the libhdfs build file.
[
https://issues.apache.org/jira/browse/HDFS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HDFS-2619:
Attachment: h-2619.patch
> Remove my personal email address from the libhdfs build file.
> -
>
> Key: HDFS-2619
> URL: https://issues.apache.org/jira/browse/HDFS-2619
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
> Attachments: h-2619.patch
>
>
> When I first wrote the libhdfs autoconf/automake stuff, I incorrectly put my
> email address in the AC_INIT line, which means if something goes wrong, you
> get:
> {quote}
> > configure: WARNING: ## Report this to ##
> {quote}
--
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-2619) Remove my personal email address from the libhdfs build file.
Remove my personal email address from the libhdfs build file.
-
Key: HDFS-2619
URL: https://issues.apache.org/jira/browse/HDFS-2619
Project: Hadoop HDFS
Issue Type: Bug
Components: build
Reporter: Owen O'Malley
Assignee: Owen O'Malley
When I first wrote the libhdfs autoconf/automake stuff, I incorrectly put my
email address in the AC_INIT line, which means if something goes wrong, you get:
{quote}
> configure: WARNING: ## Report this to ##
{quote}
--
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-2614) hadoop dist tarball is missing hdfs headers
[ https://issues.apache.org/jira/browse/HDFS-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160909#comment-13160909 ] Hudson commented on HDFS-2614: -- Integrated in Hadoop-Mapreduce-trunk #914 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/914/]) HDFS-2614. hadoop dist tarball is missing hdfs headers. (tucu) tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208928 Files : * /hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt > hadoop dist tarball is missing hdfs headers > --- > > Key: HDFS-2614 > URL: https://issues.apache.org/jira/browse/HDFS-2614 > Project: Hadoop HDFS > Issue Type: Bug > Components: build >Affects Versions: 0.24.0, 0.23.1 >Reporter: Bruno Mahé >Assignee: Alejandro Abdelnur > Labels: bigtop > Fix For: 0.24.0, 0.23.1 > > Attachments: HDFS-2614.patch > > > It would be nice to provide hdfs header so one could easily write programs to > be linked against that library and access HDFS -- 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-2614) hadoop dist tarball is missing hdfs headers
[ https://issues.apache.org/jira/browse/HDFS-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160879#comment-13160879 ] Hudson commented on HDFS-2614: -- Integrated in Hadoop-Hdfs-trunk #881 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/881/]) HDFS-2614. hadoop dist tarball is missing hdfs headers. (tucu) tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208928 Files : * /hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt > hadoop dist tarball is missing hdfs headers > --- > > Key: HDFS-2614 > URL: https://issues.apache.org/jira/browse/HDFS-2614 > Project: Hadoop HDFS > Issue Type: Bug > Components: build >Affects Versions: 0.24.0, 0.23.1 >Reporter: Bruno Mahé >Assignee: Alejandro Abdelnur > Labels: bigtop > Fix For: 0.24.0, 0.23.1 > > Attachments: HDFS-2614.patch > > > It would be nice to provide hdfs header so one could easily write programs to > be linked against that library and access HDFS -- 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-1580) Add interface for generic Write Ahead Logging mechanisms
[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160860#comment-13160860 ] Hadoop QA commented on HDFS-1580: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505753/HDFS-1580.diff against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hdfs.TestHDFSServerPorts org.apache.hadoop.hdfs.TestBlocksScheduledCounter org.apache.hadoop.hdfs.TestAppendDifferentChecksum +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1622//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1622//console This message is automatically generated. > Add interface for generic Write Ahead Logging mechanisms > > > Key: HDFS-1580 > URL: https://issues.apache.org/jira/browse/HDFS-1580 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Ivan Kelly >Assignee: Jitendra Nath Pandey > Fix For: HA branch (HDFS-1623), 0.24.0 > > Attachments: EditlogInterface.1.pdf, EditlogInterface.2.pdf, > EditlogInterface.3.pdf, HDFS-1580+1521.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > generic_wal_iface.pdf, generic_wal_iface.pdf, generic_wal_iface.pdf, > generic_wal_iface.txt > > -- 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-1580) Add interface for generic Write Ahead Logging mechanisms
[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-1580: - Attachment: HDFS-1580.diff Thanks for reviewing Jitendra. I addressed comments in the latest patch. I also made the interfaces @InterfaceStability.Evolving as they have been changing lately and could still change a bit more with HA (if they haven't already). > Add interface for generic Write Ahead Logging mechanisms > > > Key: HDFS-1580 > URL: https://issues.apache.org/jira/browse/HDFS-1580 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Ivan Kelly >Assignee: Jitendra Nath Pandey > Fix For: HA branch (HDFS-1623), 0.24.0 > > Attachments: EditlogInterface.1.pdf, EditlogInterface.2.pdf, > EditlogInterface.3.pdf, HDFS-1580+1521.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, HDFS-1580.diff, > generic_wal_iface.pdf, generic_wal_iface.pdf, generic_wal_iface.pdf, > generic_wal_iface.txt > > -- 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-2618) Implement protobuf service for NamenodeProtocol
[ https://issues.apache.org/jira/browse/HDFS-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-2618: -- Attachment: HDFS-2618.txt Updated patch. > Implement protobuf service for NamenodeProtocol > --- > > Key: HDFS-2618 > URL: https://issues.apache.org/jira/browse/HDFS-2618 > Project: Hadoop HDFS > Issue Type: New Feature > Components: name-node >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: 0.24.0 > > Attachments: HDFS-2618.txt, HDFS-2618.txt > > > This jira adds implementation for NamenodeProtocol protobuf service along the > same lines as HDFS-2181 -- 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-2618) Implement protobuf service for NamenodeProtocol
[ https://issues.apache.org/jira/browse/HDFS-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-2618: -- Attachment: HDFS-2618.txt > Implement protobuf service for NamenodeProtocol > --- > > Key: HDFS-2618 > URL: https://issues.apache.org/jira/browse/HDFS-2618 > Project: Hadoop HDFS > Issue Type: New Feature > Components: name-node >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: 0.24.0 > > Attachments: HDFS-2618.txt > > > This jira adds implementation for NamenodeProtocol protobuf service along the > same lines as HDFS-2181 -- 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-2618) Implement protobuf service for NamenodeProtocol
Implement protobuf service for NamenodeProtocol --- Key: HDFS-2618 URL: https://issues.apache.org/jira/browse/HDFS-2618 Project: Hadoop HDFS Issue Type: New Feature Components: name-node Reporter: Suresh Srinivas Assignee: Suresh Srinivas Fix For: 0.24.0 This jira adds implementation for NamenodeProtocol protobuf service along the same lines as HDFS-2181 -- 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-2581) Implement protobuf service for JournalProtocol
[ https://issues.apache.org/jira/browse/HDFS-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160720#comment-13160720 ] Hadoop QA commented on HDFS-2581: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505731/HDFS-2581.txt 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 did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit 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/1621//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1621//console This message is automatically generated. > Implement protobuf service for JournalProtocol > -- > > Key: HDFS-2581 > URL: https://issues.apache.org/jira/browse/HDFS-2581 > Project: Hadoop HDFS > Issue Type: New Feature > Components: name-node >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: 0.24.0 > > Attachments: HDFS-2581.txt, HDFS-2581.txt, HDFS-2581.txt > > > This jira adds implementation for JournalProtocol protobuf service along the > same lines as HDFS-2181 -- 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-2616) Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse
[ https://issues.apache.org/jira/browse/HDFS-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-2616. --- Resolution: Fixed Hadoop Flags: Reviewed Committed it to HDFS-1623 branch. > Change DatanodeProtocol#sendHeartbeat to return HeartbeatResponse > - > > Key: HDFS-2616 > URL: https://issues.apache.org/jira/browse/HDFS-2616 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: data-node, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt, > HDFS-2616.txt, HDFS-2616.txt, HDFS-2616.txt > > > DatanodeProtocol#sendHeartbeat() returns DatanodeCommand[]. This jira > proposes changing it to to return HeartbeatResponse that has > DatanodeCommand[]. This allows adding other information that can be returned > by the namenode to the datanode, instead of having to only return > DatanodeCommand[]. For relevant discussion see HDFS-1972. -- 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
