[jira] [Commented] (HDFS-2291) HA: Checkpointing in an HA setup
[
https://issues.apache.org/jira/browse/HDFS-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092225#comment-13092225
]
Uma Maheswara Rao G commented on HDFS-2291:
---
{quote}
One thought is to use a third, dedicated checkpointing node in addition to the
active and standby nodes.
{quote}
Introducing new nodes may create overheads in setting up the clusters. we can
always think to reduce the cluster complexities to create setups.
{quote}
Another option would be to make the standby capable of also performing the
function of checkpointing.
{quote}
IMO , standby can do checkpointing job.
what do you say Aaron?
HA: Checkpointing in an HA setup
Key: HDFS-2291
URL: https://issues.apache.org/jira/browse/HDFS-2291
Project: Hadoop HDFS
Issue Type: Sub-task
Components: name-node
Affects Versions: HA branch (HDFS-1623)
Reporter: Aaron T. Myers
Assignee: Todd Lipcon
Fix For: HA branch (HDFS-1623)
We obviously need to create checkpoints when HA is enabled. One thought is to
use a third, dedicated checkpointing node in addition to the active and
standby nodes. Another option would be to make the standby capable of also
performing the function of checkpointing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092339#comment-13092339
]
Arun C Murthy commented on HDFS-2289:
-
Thanks Jakob. I'll commit this and we can have a follow on jira to make this
part of the native build - makes sense Roman?
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HDFS-2289:
Attachment: HDFS-2289v5.patch
Fixed a minor nit - changed d/w dir to hadoop-hdfs/target/downloads since:
# We don't want temporal files in main director
# svn needs to ignore hadoop-hdfs/downloads along with git
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch, HDFS-2289v5.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HDFS-2289:
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks Alejandro!
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch, HDFS-2289v5.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092353#comment-13092353
]
Hudson commented on HDFS-2289:
--
Integrated in Hadoop-Common-trunk-Commit #798 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/798/])
HDFS-2289. Ensure jsvc is bundled with the HDFS distribution artifact.
Contributed by Alejandro Abdelnur.
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1162421
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/pom.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-project-dist
* /hadoop/common/trunk/hadoop-project/pom.xml
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch, HDFS-2289v5.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092354#comment-13092354
]
Hudson commented on HDFS-2289:
--
Integrated in Hadoop-Hdfs-trunk-Commit #875 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/875/])
HDFS-2289. Ensure jsvc is bundled with the HDFS distribution artifact.
Contributed by Alejandro Abdelnur.
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1162421
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/pom.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-project-dist
* /hadoop/common/trunk/hadoop-project/pom.xml
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch, HDFS-2289v5.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092356#comment-13092356
]
Hudson commented on HDFS-2289:
--
Integrated in Hadoop-Mapreduce-trunk-Commit #808 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/808/])
HDFS-2289. Ensure jsvc is bundled with the HDFS distribution artifact.
Contributed by Alejandro Abdelnur.
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1162421
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/pom.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* /hadoop/common/trunk/hadoop-project-dist
* /hadoop/common/trunk/hadoop-project/pom.xml
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch, HDFS-2289v5.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-962) Make DFSOutputStream MAX_PACKETS configurable
[ https://issues.apache.org/jira/browse/HDFS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Joseph updated HDFS-962: --- Attachment: HDFS-962.patch Make DFSOutputStream MAX_PACKETS configurable - Key: HDFS-962 URL: https://issues.apache.org/jira/browse/HDFS-962 Project: Hadoop HDFS Issue Type: Improvement Components: hdfs client Affects Versions: 0.22.0 Reporter: Todd Lipcon Priority: Minor Attachments: HDFS-962.patch HDFS-959 suggests that the MAX_PACKETS variable (which determines how many outstanding data packets the DFSOutputStream will permit) may have an impact on performance. If so, we should make it configurable to trade off between memory and performance. I think it ought to be a secret/undocumented config for now - this will make it easier to benchmark without confusing users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1217) Some methods in the NameNdoe should not be public
[ https://issues.apache.org/jira/browse/HDFS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laxman updated HDFS-1217: - Attachment: HDFS-1217.patch Some methods in the NameNdoe should not be public - Key: HDFS-1217 URL: https://issues.apache.org/jira/browse/HDFS-1217 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: Tsz Wo (Nicholas), SZE Attachments: HDFS-1217.patch There are quite a few NameNode methods which are not required to be public. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1217) Some methods in the NameNdoe should not be public
[ https://issues.apache.org/jira/browse/HDFS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laxman updated HDFS-1217: - Status: Patch Available (was: Open) Some methods in the NameNdoe should not be public - Key: HDFS-1217 URL: https://issues.apache.org/jira/browse/HDFS-1217 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: Tsz Wo (Nicholas), SZE Attachments: HDFS-1217.patch There are quite a few NameNode methods which are not required to be public. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1217) Some methods in the NameNdoe should not be public
[ https://issues.apache.org/jira/browse/HDFS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092368#comment-13092368 ] Laxman commented on HDFS-1217: -- Hi Nicholas, I updated the patch for review! Thanks, Lakshman Some methods in the NameNdoe should not be public - Key: HDFS-1217 URL: https://issues.apache.org/jira/browse/HDFS-1217 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: Tsz Wo (Nicholas), SZE Attachments: HDFS-1217.patch There are quite a few NameNode methods which are not required to be public. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-962) Make DFSOutputStream MAX_PACKETS configurable
[ https://issues.apache.org/jira/browse/HDFS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092374#comment-13092374 ] Hadoop QA commented on HDFS-962: -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12491974/HDFS-962.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.blockmanagement.TestHost2NodesMap +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1171//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1171//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1171//console This message is automatically generated. Make DFSOutputStream MAX_PACKETS configurable - Key: HDFS-962 URL: https://issues.apache.org/jira/browse/HDFS-962 Project: Hadoop HDFS Issue Type: Improvement Components: hdfs client Affects Versions: 0.22.0 Reporter: Todd Lipcon Priority: Minor Attachments: HDFS-962.patch HDFS-959 suggests that the MAX_PACKETS variable (which determines how many outstanding data packets the DFSOutputStream will permit) may have an impact on performance. If so, we should make it configurable to trade off between memory and performance. I think it ought to be a secret/undocumented config for now - this will make it easier to benchmark without confusing users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1217) Some methods in the NameNdoe should not be public
[ https://issues.apache.org/jira/browse/HDFS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092373#comment-13092373 ] Hadoop QA commented on HDFS-1217: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12491975/HDFS-1217.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 9 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: +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1172//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1172//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1172//console This message is automatically generated. Some methods in the NameNdoe should not be public - Key: HDFS-1217 URL: https://issues.apache.org/jira/browse/HDFS-1217 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: Tsz Wo (Nicholas), SZE Attachments: HDFS-1217.patch There are quite a few NameNode methods which are not required to be public. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2293) Add the ability to set dfs.block.size for a given file from the command line
Add the ability to set dfs.block.size for a given file from the command line Key: HDFS-2293 URL: https://issues.apache.org/jira/browse/HDFS-2293 Project: Hadoop HDFS Issue Type: Improvement Components: hdfs client Affects Versions: 0.23.0 Reporter: Aaron T. Myers See the thread [here|http://www.mail-archive.com/hdfs-user@hadoop.apache.org/msg01459.html], in which Allen correctly points out that since dfs.block.size is a client-side config, one could just set a different value in a custom HADOOP_CONF_DIR. We might as well make that easy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2289) jsvc isn't part of the artifact
[
https://issues.apache.org/jira/browse/HDFS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092398#comment-13092398
]
Roman Shaposhnik commented on HDFS-2289:
Arun, sure I can follow up with the patch on Mon. Couple of questions -- do I
need to reopen this JIRA? Will the native build patch be included in 0.23?
jsvc isn't part of the artifact
---
Key: HDFS-2289
URL: https://issues.apache.org/jira/browse/HDFS-2289
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Arun C Murthy
Assignee: Alejandro Abdelnur
Priority: Blocker
Fix For: 0.23.0
Attachments: HDFS-2289v1.patch, HDFS-2289v2.patch, HDFS-2289v3.patch,
HDFS-2289v4.patch, HDFS-2289v5.patch
Apparently we had something like this in build.xml:
property name=jsvc.location
value=http://archive.apache.org/dist/commons/daemon/binaries/1.0.2/linux/commons-daemon-1.0.2-bin-linux-i386.tar.gz;
/
Also, when I manually add in jsvc binary I get this error:
{noformat}
25/08/2011 23:47:18 29805 jsvc.exec error: Cannot find daemon loader
org/apache/commons/daemon/support/DaemonLoader
25/08/2011 23:47:18 29778 jsvc.exec error: Service exit with a return value
of 1
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2293) Add the ability to set dfs.block.size for a given file from the command line
[ https://issues.apache.org/jira/browse/HDFS-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092400#comment-13092400 ] Todd Lipcon commented on HDFS-2293: --- I believe this is possible - hadoop fs -Ddfs.block.size= -put src dst works fine here on trunk. Add the ability to set dfs.block.size for a given file from the command line Key: HDFS-2293 URL: https://issues.apache.org/jira/browse/HDFS-2293 Project: Hadoop HDFS Issue Type: Improvement Components: hdfs client Affects Versions: 0.23.0 Reporter: Aaron T. Myers Labels: newbie See the thread [here|http://www.mail-archive.com/hdfs-user@hadoop.apache.org/msg01459.html], in which Allen correctly points out that since dfs.block.size is a client-side config, one could just set a different value in a custom HADOOP_CONF_DIR. We might as well make that easy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (HDFS-1330) Make RPCs to DataNodes timeout
[ https://issues.apache.org/jira/browse/HDFS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley reopened HDFS-1330: -- Assignee: John George (was: Hairong Kuang) Re-opening to add enhanced unit testing in v0.23 (moved from HADOOP-6889). Make RPCs to DataNodes timeout -- Key: HDFS-1330 URL: https://issues.apache.org/jira/browse/HDFS-1330 Project: Hadoop HDFS Issue Type: New Feature Components: data-node Affects Versions: 0.22.0 Reporter: Hairong Kuang Assignee: John George Fix For: 0.22.0 Attachments: hdfsRpcTimeout.patch This jira aims to make client/datanode or datanode/datanode RPC to have a timeout of DataNode#socketTimeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1330) Make RPCs to DataNodes timeout
[ https://issues.apache.org/jira/browse/HDFS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1330: - Fix Version/s: 0.24.0 0.23.0 Affects Version/s: 0.23.0 Status: Patch Available (was: Reopened) Submitted on behalf of John George. (Moved from HADOOP-6889.) Make RPCs to DataNodes timeout -- Key: HDFS-1330 URL: https://issues.apache.org/jira/browse/HDFS-1330 Project: Hadoop HDFS Issue Type: New Feature Components: data-node Affects Versions: 0.22.0, 0.23.0 Reporter: Hairong Kuang Assignee: John George Fix For: 0.22.0, 0.23.0, 0.24.0 Attachments: hdfsRpcTimeout.patch This jira aims to make client/datanode or datanode/datanode RPC to have a timeout of DataNode#socketTimeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1330) Make RPCs to DataNodes timeout
[ https://issues.apache.org/jira/browse/HDFS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1330: - Attachment: HADOOP-6889-fortrunk-2.patch Make RPCs to DataNodes timeout -- Key: HDFS-1330 URL: https://issues.apache.org/jira/browse/HDFS-1330 Project: Hadoop HDFS Issue Type: New Feature Components: data-node Affects Versions: 0.22.0, 0.23.0 Reporter: Hairong Kuang Assignee: John George Fix For: 0.22.0, 0.23.0, 0.24.0 Attachments: HADOOP-6889-fortrunk-2.patch, hdfsRpcTimeout.patch This jira aims to make client/datanode or datanode/datanode RPC to have a timeout of DataNode#socketTimeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1330) Make RPCs to DataNodes timeout
[ https://issues.apache.org/jira/browse/HDFS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092409#comment-13092409 ] Hadoop QA commented on HDFS-1330: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12491983/HADOOP-6889-fortrunk-2.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 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.server.blockmanagement.TestHost2NodesMap +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1173//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1173//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1173//console This message is automatically generated. Make RPCs to DataNodes timeout -- Key: HDFS-1330 URL: https://issues.apache.org/jira/browse/HDFS-1330 Project: Hadoop HDFS Issue Type: New Feature Components: data-node Affects Versions: 0.22.0, 0.23.0 Reporter: Hairong Kuang Assignee: John George Fix For: 0.22.0, 0.23.0, 0.24.0 Attachments: HADOOP-6889-fortrunk-2.patch, hdfsRpcTimeout.patch This jira aims to make client/datanode or datanode/datanode RPC to have a timeout of DataNode#socketTimeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1330) Make RPCs to DataNodes timeout
[ https://issues.apache.org/jira/browse/HDFS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092410#comment-13092410 ] Hadoop QA commented on HDFS-1330: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12491983/HADOOP-6889-fortrunk-2.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 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: +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1174//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1174//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1174//console This message is automatically generated. Make RPCs to DataNodes timeout -- Key: HDFS-1330 URL: https://issues.apache.org/jira/browse/HDFS-1330 Project: Hadoop HDFS Issue Type: New Feature Components: data-node Affects Versions: 0.22.0, 0.23.0 Reporter: Hairong Kuang Assignee: John George Fix For: 0.22.0, 0.23.0, 0.24.0 Attachments: HADOOP-6889-fortrunk-2.patch, hdfsRpcTimeout.patch This jira aims to make client/datanode or datanode/datanode RPC to have a timeout of DataNode#socketTimeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1330) Make RPCs to DataNodes timeout
[ https://issues.apache.org/jira/browse/HDFS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092421#comment-13092421 ] Uma Maheswara Rao G commented on HDFS-1330: --- Thanks Matt for the patch. This change is very much required. see the scenario in HADOOP-7488 Make RPCs to DataNodes timeout -- Key: HDFS-1330 URL: https://issues.apache.org/jira/browse/HDFS-1330 Project: Hadoop HDFS Issue Type: New Feature Components: data-node Affects Versions: 0.22.0, 0.23.0 Reporter: Hairong Kuang Assignee: John George Fix For: 0.22.0, 0.23.0, 0.24.0 Attachments: HADOOP-6889-fortrunk-2.patch, hdfsRpcTimeout.patch This jira aims to make client/datanode or datanode/datanode RPC to have a timeout of DataNode#socketTimeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
