date:20120410


[ 
https://issues.apache.org/jira/browse/HDFS-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250619#comment-13250619
 ] 

Hudson commented on HDFS-3236:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3236. NameNode does not initialize generic conf keys when started with 
-initializeSharedEditsDir. Contributed by Aaron T. Myers. (Revision 1311554)

 Result = FAILURE
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311554
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestInitializeSharedEdits.java


 NameNode does not initialize generic conf keys when started with 
 -initializeSharedEditsDir
 --

 Key: HDFS-3236
 URL: https://issues.apache.org/jira/browse/HDFS-3236
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: ha, name-node
Affects Versions: 2.0.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers
Priority: Minor
 Fix For: 2.0.0

 Attachments: HDFS-3236.patch


 This means that configurations that scope the location of the 
 name/edits/shared edits dirs by nameserice or namenode won't work with `hdfs 
 namenode -initializeSharedEdits'.

--
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-3119) Overreplicated block is not deleted even after the replication factor is reduced after sync follwed by closing that file


[ 
https://issues.apache.org/jira/browse/HDFS-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250616#comment-13250616
 ] 

Hudson commented on HDFS-3119:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3119. Overreplicated block is not deleted even after the replication 
factor is reduced after sync follwed by closing that file. Contributed by 
Ashish Singhi. (Revision 1311380)

 Result = FAILURE
umamahesh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311380
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestOverReplicatedBlocks.java


 Overreplicated block is not deleted even after the replication factor is 
 reduced after sync follwed by closing that file
 

 Key: HDFS-3119
 URL: https://issues.apache.org/jira/browse/HDFS-3119
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Affects Versions: 0.24.0
Reporter: J.Andreina
Assignee: Ashish Singhi
Priority: Minor
  Labels: patch
 Fix For: 0.24.0, 2.0.0

 Attachments: HDFS-3119-1.patch, HDFS-3119-1.patch, HDFS-3119.patch


 cluster setup:
 --
 1NN,2 DN,replication factor 2,block report interval 3sec ,block size-256MB
 step1: write a file filewrite.txt of size 90bytes with sync(not closed) 
 step2: change the replication factor to 1  using the command: ./hdfs dfs 
 -setrep 1 /filewrite.txt
 step3: close the file
 * At the NN side the file Decreasing replication from 2 to 1 for 
 /filewrite.txt , logs has occured but the overreplicated blocks are not 
 deleted even after the block report is sent from DN
 * while listing the file in the console using ./hdfs dfs -ls  the 
 replication factor for that file is mentioned as 1
 * In fsck report for that files displays that the file is replicated to 2 
 datanodes

--
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-3240) Drop log level of heartbeat: ... in BPServiceActor to DEBUG


[ 
https://issues.apache.org/jira/browse/HDFS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250626#comment-13250626
 ] 

Hudson commented on HDFS-3240:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3240. Drop log level of heartbeat: ... in BPServiceActor to DEBUG. 
Contributed by Todd Lipcon. (Revision 1311577)

 Result = FAILURE
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311577
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java


 Drop log level of heartbeat: ... in BPServiceActor to DEBUG
 -

 Key: HDFS-3240
 URL: https://issues.apache.org/jira/browse/HDFS-3240
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: data-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Fix For: 2.0.0

 Attachments: hdfs-3240.txt


 The following log message is at INFO level, but should be at DEBUG level:
 {code}
 LOG.info(heartbeat:  + this);
 {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-3234) Accidentally left log message in GetConf after HDFS-3226


[ 
https://issues.apache.org/jira/browse/HDFS-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250623#comment-13250623
 ] 

Hudson commented on HDFS-3234:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3234. Accidentally left log message in GetConf after HDFS-3226. 
Contributed by Todd Lipcon. (Revision 1311541)

 Result = FAILURE
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311541
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/GetConf.java


 Accidentally left log message in GetConf after HDFS-3226
 

 Key: HDFS-3234
 URL: https://issues.apache.org/jira/browse/HDFS-3234
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Fix For: 2.0.0

 Attachments: hdfs-3234.txt


 I accidentally left a debug printout in. It doesn't cause a functionality 
 regression, but it does cause noisy output on the command line:
 $ ./bin/hdfs getconf -confKey fs.defaultFS
 key: fs.defaultFS
 hdfs://nameserviceId1

--
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-3235) MiniDFSClusterManager doesn't correctly support -format option


[ 
https://issues.apache.org/jira/browse/HDFS-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250621#comment-13250621
 ] 

Hudson commented on HDFS-3235:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3235. MiniDFSClusterManager doesn't correctly support -format option. 
Contributed by Henry Robinson. (Revision 1311556)

 Result = FAILURE
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311556
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/test/MiniDFSClusterManager.java


 MiniDFSClusterManager doesn't correctly support -format option
 --

 Key: HDFS-3235
 URL: https://issues.apache.org/jira/browse/HDFS-3235
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Henry Robinson
Assignee: Henry Robinson
Priority: Minor
 Fix For: 3.0.0

 Attachments: HDFS-3235.0.patch


 MiniDFSClusterManager.java correctly honours -format for setting 
 StartupOption.FORMAT, but does not set .format(true) on the 
 MiniDFSClusterBuilder. This means the datanodes' data dirs will be formatted 
 every time. 

--
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-3226) Allow GetConf tool to print arbitrary keys


[ 
https://issues.apache.org/jira/browse/HDFS-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250625#comment-13250625
 ] 

Hudson commented on HDFS-3226:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3234. Accidentally left log message in GetConf after HDFS-3226. 
Contributed by Todd Lipcon. (Revision 1311541)

 Result = FAILURE
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311541
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/GetConf.java


 Allow GetConf tool to print arbitrary keys
 --

 Key: HDFS-3226
 URL: https://issues.apache.org/jira/browse/HDFS-3226
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: tools
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
 Fix For: 2.0.0

 Attachments: hdfs-3226.txt


 Currently the hdfs getconf tool can only print out certain keys, like the 
 list of NNs, etc. It would be handy to allow it to fetch an arbitrary 
 configuration. For example, users may wish to write shell scripts that 
 interact with their hadoop cluster, and it is useful to be able to fetch 
 configs like the name of the superuser, or the state of whether HA is enabled.

--
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-3004) Implement Recovery Mode


[ 
https://issues.apache.org/jira/browse/HDFS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250622#comment-13250622
 ] 

Hudson commented on HDFS-3004:
--

Integrated in Hadoop-Hdfs-trunk #1010 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1010/])
HDFS-3004. Implement Recovery Mode. Contributed by Colin Patrick McCabe 
(Revision 1311394)

 Result = FAILURE
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311394
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/dev-support/findbugsExcludeFile.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/main/java/org/apache/hadoop/contrib/bkjournal/BookKeeperEditLogInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/test/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogTestUtil.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/docs/src/documentation/content/xdocs/hdfs_user_guide.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/HdfsServerConstants.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/BackupImage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/Checkpointer.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogBackupInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogFileInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogOutputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogLoader.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogOp.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImageTransactionalStorageInspector.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FileJournalManager.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/JournalStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/MetaRecoveryContext.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/EditLogTailer.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineEditsViewer/OfflineEditsXmlLoader.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/MiniDFSCluster.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLog.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLogRace.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSEditLogLoader.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeRecovery.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestSecurityTokenEditLog.java


 Implement Recovery Mode
 ---

 Key: HDFS-3004
 URL: https://issues.apache.org/jira/browse/HDFS-3004
 Project: Hadoop HDFS
  Issue Type: New Feature
  Components: tools
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
 Fix For: 2.0.0

 Attachments: HDFS-3004.010.patch, HDFS-3004.011.patch,

[jira] [Commented] (HDFS-3236) NameNode does not initialize generic conf keys when started with -initializeSharedEditsDir


[ 
https://issues.apache.org/jira/browse/HDFS-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250664#comment-13250664
 ] 

Hudson commented on HDFS-3236:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3236. NameNode does not initialize generic conf keys when started with 
-initializeSharedEditsDir. Contributed by Aaron T. Myers. (Revision 1311554)

 Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311554
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestInitializeSharedEdits.java


 NameNode does not initialize generic conf keys when started with 
 -initializeSharedEditsDir
 --

 Key: HDFS-3236
 URL: https://issues.apache.org/jira/browse/HDFS-3236
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: ha, name-node
Affects Versions: 2.0.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers
Priority: Minor
 Fix For: 2.0.0

 Attachments: HDFS-3236.patch


 This means that configurations that scope the location of the 
 name/edits/shared edits dirs by nameserice or namenode won't work with `hdfs 
 namenode -initializeSharedEdits'.

--
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-3119) Overreplicated block is not deleted even after the replication factor is reduced after sync follwed by closing that file


[ 
https://issues.apache.org/jira/browse/HDFS-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250661#comment-13250661
 ] 

Hudson commented on HDFS-3119:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3119. Overreplicated block is not deleted even after the replication 
factor is reduced after sync follwed by closing that file. Contributed by 
Ashish Singhi. (Revision 1311380)

 Result = SUCCESS
umamahesh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311380
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestOverReplicatedBlocks.java


 Overreplicated block is not deleted even after the replication factor is 
 reduced after sync follwed by closing that file
 

 Key: HDFS-3119
 URL: https://issues.apache.org/jira/browse/HDFS-3119
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Affects Versions: 0.24.0
Reporter: J.Andreina
Assignee: Ashish Singhi
Priority: Minor
  Labels: patch
 Fix For: 0.24.0, 2.0.0

 Attachments: HDFS-3119-1.patch, HDFS-3119-1.patch, HDFS-3119.patch


 cluster setup:
 --
 1NN,2 DN,replication factor 2,block report interval 3sec ,block size-256MB
 step1: write a file filewrite.txt of size 90bytes with sync(not closed) 
 step2: change the replication factor to 1  using the command: ./hdfs dfs 
 -setrep 1 /filewrite.txt
 step3: close the file
 * At the NN side the file Decreasing replication from 2 to 1 for 
 /filewrite.txt , logs has occured but the overreplicated blocks are not 
 deleted even after the block report is sent from DN
 * while listing the file in the console using ./hdfs dfs -ls  the 
 replication factor for that file is mentioned as 1
 * In fsck report for that files displays that the file is replicated to 2 
 datanodes

--
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-3226) Allow GetConf tool to print arbitrary keys


[ 
https://issues.apache.org/jira/browse/HDFS-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250670#comment-13250670
 ] 

Hudson commented on HDFS-3226:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3234. Accidentally left log message in GetConf after HDFS-3226. 
Contributed by Todd Lipcon. (Revision 1311541)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311541
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/GetConf.java


 Allow GetConf tool to print arbitrary keys
 --

 Key: HDFS-3226
 URL: https://issues.apache.org/jira/browse/HDFS-3226
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: tools
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
 Fix For: 2.0.0

 Attachments: hdfs-3226.txt


 Currently the hdfs getconf tool can only print out certain keys, like the 
 list of NNs, etc. It would be handy to allow it to fetch an arbitrary 
 configuration. For example, users may wish to write shell scripts that 
 interact with their hadoop cluster, and it is useful to be able to fetch 
 configs like the name of the superuser, or the state of whether HA is enabled.

--
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-3240) Drop log level of heartbeat: ... in BPServiceActor to DEBUG


[ 
https://issues.apache.org/jira/browse/HDFS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250671#comment-13250671
 ] 

Hudson commented on HDFS-3240:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3240. Drop log level of heartbeat: ... in BPServiceActor to DEBUG. 
Contributed by Todd Lipcon. (Revision 1311577)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311577
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java


 Drop log level of heartbeat: ... in BPServiceActor to DEBUG
 -

 Key: HDFS-3240
 URL: https://issues.apache.org/jira/browse/HDFS-3240
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: data-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Fix For: 2.0.0

 Attachments: hdfs-3240.txt


 The following log message is at INFO level, but should be at DEBUG level:
 {code}
 LOG.info(heartbeat:  + this);
 {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-3234) Accidentally left log message in GetConf after HDFS-3226


[ 
https://issues.apache.org/jira/browse/HDFS-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250668#comment-13250668
 ] 

Hudson commented on HDFS-3234:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3234. Accidentally left log message in GetConf after HDFS-3226. 
Contributed by Todd Lipcon. (Revision 1311541)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311541
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/GetConf.java


 Accidentally left log message in GetConf after HDFS-3226
 

 Key: HDFS-3234
 URL: https://issues.apache.org/jira/browse/HDFS-3234
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Fix For: 2.0.0

 Attachments: hdfs-3234.txt


 I accidentally left a debug printout in. It doesn't cause a functionality 
 regression, but it does cause noisy output on the command line:
 $ ./bin/hdfs getconf -confKey fs.defaultFS
 key: fs.defaultFS
 hdfs://nameserviceId1

--
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-3235) MiniDFSClusterManager doesn't correctly support -format option


[ 
https://issues.apache.org/jira/browse/HDFS-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250666#comment-13250666
 ] 

Hudson commented on HDFS-3235:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3235. MiniDFSClusterManager doesn't correctly support -format option. 
Contributed by Henry Robinson. (Revision 1311556)

 Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311556
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/test/MiniDFSClusterManager.java


 MiniDFSClusterManager doesn't correctly support -format option
 --

 Key: HDFS-3235
 URL: https://issues.apache.org/jira/browse/HDFS-3235
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Henry Robinson
Assignee: Henry Robinson
Priority: Minor
 Fix For: 3.0.0

 Attachments: HDFS-3235.0.patch


 MiniDFSClusterManager.java correctly honours -format for setting 
 StartupOption.FORMAT, but does not set .format(true) on the 
 MiniDFSClusterBuilder. This means the datanodes' data dirs will be formatted 
 every time. 

--
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-3004) Implement Recovery Mode


[ 
https://issues.apache.org/jira/browse/HDFS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250667#comment-13250667
 ] 

Hudson commented on HDFS-3004:
--

Integrated in Hadoop-Mapreduce-trunk #1045 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1045/])
HDFS-3004. Implement Recovery Mode. Contributed by Colin Patrick McCabe 
(Revision 1311394)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311394
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/dev-support/findbugsExcludeFile.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/main/java/org/apache/hadoop/contrib/bkjournal/BookKeeperEditLogInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/test/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogTestUtil.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/docs/src/documentation/content/xdocs/hdfs_user_guide.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/HdfsServerConstants.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/BackupImage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/Checkpointer.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogBackupInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogFileInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogInputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditLogOutputStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogLoader.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogOp.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImageTransactionalStorageInspector.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FileJournalManager.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/JournalStream.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/MetaRecoveryContext.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/EditLogTailer.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineEditsViewer/OfflineEditsXmlLoader.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/MiniDFSCluster.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLog.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLogRace.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSEditLogLoader.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeRecovery.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestSecurityTokenEditLog.java


 Implement Recovery Mode
 ---

 Key: HDFS-3004
 URL: https://issues.apache.org/jira/browse/HDFS-3004
 Project: Hadoop HDFS
  Issue Type: New Feature
  Components: tools
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
 Fix For: 2.0.0

 Attachments: HDFS-3004.010.patch, HDFS-3004.011.patch,

[jira] [Commented] (HDFS-3239) Hadoop-1.0.2 is taking the wrong class path during setup

2012-04-10 Thread Hadoopuser (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250676#comment-13250676
 ] 

Hadoopuser commented on HDFS-3239:
--

Thank you for the quick reply.

so Java in my local machine is configured as

/usr/lib/jvm/jdk1.6.0_27/bin/java





-- 
Srikanth Kommineni,
Graduate Assistant,
Dept of Computer Science,
Rochester Institute of Technology.


 Hadoop-1.0.2 is taking the wrong class path during setup 
 -

 Key: HDFS-3239
 URL: https://issues.apache.org/jira/browse/HDFS-3239
 Project: Hadoop HDFS
  Issue Type: Bug
 Environment: I am using 32 bit ubuntu 11.10
Reporter: Hadoopuser

 /usr/libexec/../bin/hadoop: line 321: /usr/lib/jvm/java-6-sun/bin/java: No 
 such file or directory
 /usr/libexec/../bin/hadoop: line 387: /usr/lib/jvm/java-6-sun/bin/java: No 
 such file or directory

--
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-3238) ServerCommand and friends don't need to be writables


 [ 
https://issues.apache.org/jira/browse/HDFS-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3238:
--

  Resolution: Fixed
   Fix Version/s: 2.0.0
Target Version/s:   (was: 2.0.0)
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

I've committed this and merged to branch-2.

 ServerCommand and friends don't need to be writables
 

 Key: HDFS-3238
 URL: https://issues.apache.org/jira/browse/HDFS-3238
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Eli Collins
 Fix For: 2.0.0

 Attachments: hdfs-3238.txt


 We can remove writable infrastructure from the ServerCommand classes as 
 they're not uses across clients and we're PB within the server side. 

--
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-3238) ServerCommand and friends don't need to be writables


[ 
https://issues.apache.org/jira/browse/HDFS-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250726#comment-13250726
 ] 

Hudson commented on HDFS-3238:
--

Integrated in Hadoop-Hdfs-trunk-Commit #2112 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2112/])
HDFS-3238. ServerCommand and friends don't need to be writables. 
Contributed by Eli Collins (Revision 1311774)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311774
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BalancerBandwidthCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockRecoveryCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/CheckpointCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/FinalizeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/KeyUpdateCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/RegisterCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/ServerCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/UpgradeCommand.java


 ServerCommand and friends don't need to be writables
 

 Key: HDFS-3238
 URL: https://issues.apache.org/jira/browse/HDFS-3238
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Eli Collins
 Fix For: 2.0.0

 Attachments: hdfs-3238.txt


 We can remove writable infrastructure from the ServerCommand classes as 
 they're not uses across clients and we're PB within the server side. 

--
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-3238) ServerCommand and friends don't need to be writables


[ 
https://issues.apache.org/jira/browse/HDFS-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250728#comment-13250728
 ] 

Hudson commented on HDFS-3238:
--

Integrated in Hadoop-Common-trunk-Commit #2038 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2038/])
HDFS-3238. ServerCommand and friends don't need to be writables. 
Contributed by Eli Collins (Revision 1311774)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311774
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BalancerBandwidthCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockRecoveryCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/CheckpointCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/FinalizeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/KeyUpdateCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/RegisterCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/ServerCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/UpgradeCommand.java


 ServerCommand and friends don't need to be writables
 

 Key: HDFS-3238
 URL: https://issues.apache.org/jira/browse/HDFS-3238
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Eli Collins
 Fix For: 2.0.0

 Attachments: hdfs-3238.txt


 We can remove writable infrastructure from the ServerCommand classes as 
 they're not uses across clients and we're PB within the server side. 

--
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-3238) ServerCommand and friends don't need to be writables


[ 
https://issues.apache.org/jira/browse/HDFS-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250741#comment-13250741
 ] 

Hudson commented on HDFS-3238:
--

Integrated in Hadoop-Mapreduce-trunk-Commit #2051 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2051/])
HDFS-3238. ServerCommand and friends don't need to be writables. 
Contributed by Eli Collins (Revision 1311774)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1311774
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BalancerBandwidthCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockRecoveryCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/CheckpointCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/FinalizeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/KeyUpdateCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/RegisterCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/ServerCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/UpgradeCommand.java


 ServerCommand and friends don't need to be writables
 

 Key: HDFS-3238
 URL: https://issues.apache.org/jira/browse/HDFS-3238
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Eli Collins
 Fix For: 2.0.0

 Attachments: hdfs-3238.txt


 We can remove writable infrastructure from the ServerCommand classes as 
 they're not uses across clients and we're PB within the server side. 

--
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-3243) TestParallelRead timing out on jenkins

TestParallelRead timing out on jenkins
--

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon


Trunk builds have been failing recently due to a TestParallelRead timeout. It 
doesn't report in the Jenkins failure list because surefire handles timeouts 
really poorly.

--
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-3243) TestParallelRead timing out on jenkins

2012-04-10 Thread Todd Lipcon (Assigned) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon reassigned HDFS-3243:
-

Assignee: Henry Robinson

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson

 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3243) TestParallelRead timing out on jenkins


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250803#comment-13250803
 ] 

Todd Lipcon commented on HDFS-3243:
---

Seems like this test was lengthened by HDFS-2834. I'm not sure yet whether it 
represents a performance regression, or if the test itself was just changed in 
such a way that it runs much longer.

On branch-2:
{code}
  testcase time=9.15 classname=org.apache.hadoop.hdfs.TestParallelRead 
name=testParallelRead/
{code}

On trunk:
{code}
  testcase time=23.397 classname=org.apache.hadoop.hdfs.TestParallelRead 
name=testParallelReadCopying/
  testcase time=133.218 classname=org.apache.hadoop.hdfs.TestParallelRead 
name=testParallelReadByteBuffer/
  testcase time=61.364 classname=org.apache.hadoop.hdfs.TestParallelRead 
name=testParallelReadMixed/
{code}

I also see a lot of blocked threads in the jstack on trunk. I asked Henry to 
take a look at this.

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson

 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3243) TestParallelRead timing out on jenkins


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250820#comment-13250820
 ] 

Todd Lipcon commented on HDFS-3243:
---

fwiw I tried copying the old TestParallelRead from branch-2 into trunk, and it 
runs just as fast there as it does in branch-2. So this seems like an issue 
with the new test code, rather than a regression in the read performance of the 
existing path.

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson

 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3243) TestParallelRead timing out on jenkins

2012-04-10 Thread Henry Robinson (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250829#comment-13250829
 ] 

Henry Robinson commented on HDFS-3243:
--

Todd mentions that the test does eventually finish, so I don't think this is a 
correctness bug (thankfully). I'm looking to see how the test changes could 
have made this much slower. 

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson

 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3244) Remove dead writable code from hdfs/protocol

Remove dead writable code from hdfs/protocol


 Key: HDFS-3244
 URL: https://issues.apache.org/jira/browse/HDFS-3244
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins


While doing HDFS-3238 I noticed that there's more dead writable code in 
hdfs/protocol. Let's remove it.

--
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-3244) Remove dead writable code from hdfs/protocol


 [ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3244:
--

Attachment: hdfs-3244.txt

Patch attached. Removes the dead code and fixes up some references to 
protocolR23Compatible in comments that are no longer valid.

 Remove dead writable code from hdfs/protocol
 

 Key: HDFS-3244
 URL: https://issues.apache.org/jira/browse/HDFS-3244
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins
 Attachments: hdfs-3244.txt


 While doing HDFS-3238 I noticed that there's more dead writable code in 
 hdfs/protocol. Let's remove it.

--
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-3244) Remove dead writable code from hdfs/protocol


 [ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3244:
--

Status: Patch Available  (was: Open)

 Remove dead writable code from hdfs/protocol
 

 Key: HDFS-3244
 URL: https://issues.apache.org/jira/browse/HDFS-3244
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins
 Attachments: hdfs-3244.txt


 While doing HDFS-3238 I noticed that there's more dead writable code in 
 hdfs/protocol. Let's remove it.

--
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-2983) Relax the build version check to permit rolling upgrades within a release


[ 
https://issues.apache.org/jira/browse/HDFS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250954#comment-13250954
 ] 

Todd Lipcon commented on HDFS-2983:
---

How about the following proposal:

- change the check for DN registration so that, if the DN's ctime differs from 
the NN's ctime (i.e the NN has started a snapshot style upgrade), then the 
version check will be strict
- file a follow-up JIRA to add a cluster version summary to the web UI and to 
the NN metrics, allowing ops to monitor whether they have machines that might 
have missed a rolling upgrade

Does that address your concern? I agree with your point that it can be 
confusing to manage, but not sure what the specific change you're asking for is.

 Relax the build version check to permit rolling upgrades within a release
 -

 Key: HDFS-2983
 URL: https://issues.apache.org/jira/browse/HDFS-2983
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Aaron T. Myers
 Attachments: HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, 
 HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch


 Currently the version check for DN/NN communication is strict (it checks the 
 exact svn revision or git hash, Storage#getBuildVersion calls 
 VersionInfo#getRevision), which prevents rolling upgrades across any 
 releases. Once we have the PB-base RPC in place (coming soon to branch-23) 
 we'll have the necessary pieces in place to loosen this restriction, though 
 perhaps it takes another 23 minor release or so before we're ready to commit 
 to making the minor versions compatible.

--
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-3245) Add metrics and web UI for cluster version summary

Add metrics and web UI for cluster version summary
--

 Key: HDFS-3245
 URL: https://issues.apache.org/jira/browse/HDFS-3245
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon


With the introduction of protocol compatibility, once HDFS-2983 is committed, 
we have the possibility that different nodes in a cluster are running different 
software versions. To aid operators, we should add the ability to summarize the 
status of versions in the cluster, so they can easily determine whether a 
rolling upgrade is in progress or if some nodes missed an upgrade (eg maybe 
they were out of service when the software was updated)

--
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-2696) fuse-dfs build problems

2012-04-10 Thread Eli Collins (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250964#comment-13250964
 ] 

Eli Collins commented on HDFS-2696:
---

Let's have the new directory structure be src/contrib/fuse-dfs/src instead of 
src/contrib/fuse-dfs/src/main/contrib/fuse-dfs/src.  Otherwise looks great.

 fuse-dfs build problems
 ---

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven.patch, 
 HDFS-2696-plus.patch, HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-3246) pRead equivalent for direct read path

2012-04-10 Thread Henry Robinson (Created) (JIRA)

pRead equivalent for direct read path
-

 Key: HDFS-3246
 URL: https://issues.apache.org/jira/browse/HDFS-3246
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Henry Robinson
Assignee: Henry Robinson


There is no pread equivalent in ByteBufferReadable. We should consider adding 
one. It would be relatively easy to implement for the distributed case 
(certainly compared to HDFS-2834), since DFSInputStream does most of the heavy 
lifting.

--
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-3243) TestParallelRead timing out on jenkins

2012-04-10 Thread Henry Robinson (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henry Robinson updated HDFS-3243:
-

Status: Patch Available  (was: Open)

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3243) TestParallelRead timing out on jenkins

2012-04-10 Thread Henry Robinson (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henry Robinson updated HDFS-3243:
-

Attachment: HDFS-3243.0.patch

Turns out I left N_ITERATIONS as 4096 in HDFS-2834, not 1024 as it used to be. 
The tests run much more quickly for me now, as you might expect, and directly 
comparable with the old test code run against trunk.

This does shine a light on a separate issue, which is that ByteBufferReadable 
lacks a lockless pread, which is faked out in this test by seeking-then-reading 
under a lock, with a bit of unnecessary serialisation as a result. I've opened 
HDSF-3246 to track this. 

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3244) Remove dead writable code from hdfs/protocol

2012-04-10 Thread Robert Joseph Evans (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250970#comment-13250970
]

Hadoop QA commented on HDFS-3244:
-

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522141/hdfs-3244.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 7 new or modified test
files.

+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 eclipse:eclipse. The patch built with eclipse:eclipse.

+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/2242//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2242//console

This message is automatically generated.

Remove dead writable code from hdfs/protocol

Key: HDFS-3244
URL: https://issues.apache.org/jira/browse/HDFS-3244
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hdfs-3244.txt

While doing HDFS-3238 I noticed that there's more dead writable code in
hdfs/protocol. Let's remove it.

[jira] [Commented] (HDFS-3245) Add metrics and web UI for cluster version summary


[ 
https://issues.apache.org/jira/browse/HDFS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250990#comment-13250990
 ] 

Robert Joseph Evans commented on HDFS-3245:
---

It would be great to have some sort of statistics about the clients as well.  I 
know that is harder because they are transient so it may need to be a separate 
JIRA, but it would be very useful. We have seen many issues in the past where a 
client was not upgraded, but all of the servers have been, and tracking it down 
can be painful.

 Add metrics and web UI for cluster version summary
 --

 Key: HDFS-3245
 URL: https://issues.apache.org/jira/browse/HDFS-3245
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon

 With the introduction of protocol compatibility, once HDFS-2983 is committed, 
 we have the possibility that different nodes in a cluster are running 
 different software versions. To aid operators, we should add the ability to 
 summarize the status of versions in the cluster, so they can easily determine 
 whether a rolling upgrade is in progress or if some nodes missed an upgrade 
 (eg maybe they were out of service when the software was updated)

--
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-3245) Add metrics and web UI for cluster version summary


[ 
https://issues.apache.org/jira/browse/HDFS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250998#comment-13250998
 ] 

Todd Lipcon commented on HDFS-3245:
---

Another thing: we already have some per-datanode info in JMX. We should be sure 
to add the registered software version to this info (and to the DFS node list 
pages)

bq. It would be great to have some sort of statistics about the clients as well

I agree it would be nice, but we don't currently send software version strings 
in the IPC handshake or anything. So, I think we should handle it separately 
(this JIRA is just about exposing info we can already easily track)

 Add metrics and web UI for cluster version summary
 --

 Key: HDFS-3245
 URL: https://issues.apache.org/jira/browse/HDFS-3245
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon

 With the introduction of protocol compatibility, once HDFS-2983 is committed, 
 we have the possibility that different nodes in a cluster are running 
 different software versions. To aid operators, we should add the ability to 
 summarize the status of versions in the cluster, so they can easily determine 
 whether a rolling upgrade is in progress or if some nodes missed an upgrade 
 (eg maybe they were out of service when the software was updated)

--
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-3247) Improve bootstrapStandby behavior when original NN is not active

2012-04-10 Thread Tsz Wo (Nicholas), SZE (Commented) (JIRA)

Improve bootstrapStandby behavior when original NN is not active


 Key: HDFS-3247
 URL: https://issues.apache.org/jira/browse/HDFS-3247
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: ha
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor


Currently, if you run bootstrapStandby while the first NN is in standby mode, 
it will spit out an ugly StandbyException with a trace. Instead, it should 
print an explanation that you should transition the first NN to active before 
bootstrapping.

--
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-3247) Improve bootstrapStandby behavior when original NN is not active


[ 
https://issues.apache.org/jira/browse/HDFS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251013#comment-13251013
 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-3247:
--

Do you mean improving the error message instead of the behavior?

 Improve bootstrapStandby behavior when original NN is not active
 

 Key: HDFS-3247
 URL: https://issues.apache.org/jira/browse/HDFS-3247
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: ha
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor

 Currently, if you run bootstrapStandby while the first NN is in standby mode, 
 it will spit out an ugly StandbyException with a trace. Instead, it should 
 print an explanation that you should transition the first NN to active before 
 bootstrapping.

--
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-3243) TestParallelRead timing out on jenkins

[
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251028#comment-13251028
]

Hadoop QA commented on HDFS-3243:
-

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522151/HDFS-3243.0.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+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 eclipse:eclipse. The patch built with eclipse:eclipse.

+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/2243//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2243//console

This message is automatically generated.

TestParallelRead timing out on jenkins
--

Key: HDFS-3243
URL: https://issues.apache.org/jira/browse/HDFS-3243
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
Attachments: HDFS-3243.0.patch

Trunk builds have been failing recently due to a TestParallelRead timeout. It
doesn't report in the Jenkins failure list because surefire handles timeouts
really poorly.

[jira] [Commented] (HDFS-3247) Improve bootstrapStandby behavior when original NN is not active

2012-04-10 Thread Robert Joseph Evans (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251029#comment-13251029
 ] 

Todd Lipcon commented on HDFS-3247:
---

I think we could do one of the following:
1) Improve the error message to note that the admin should make sure the other 
NN is active before proceeding
2) Have it automatically transition it to active if this is the case.

What do you think? I think 1 makes more sense, since the admin has to make an 
explicit decision.

 Improve bootstrapStandby behavior when original NN is not active
 

 Key: HDFS-3247
 URL: https://issues.apache.org/jira/browse/HDFS-3247
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: ha
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor

 Currently, if you run bootstrapStandby while the first NN is in standby mode, 
 it will spit out an ugly StandbyException with a trace. Instead, it should 
 print an explanation that you should transition the first NN to active before 
 bootstrapping.

--
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-3247) Improve bootstrapStandby behavior when original NN is not active

2012-04-10 Thread Aaron T. Myers (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251030#comment-13251030
 ] 

Aaron T. Myers commented on HDFS-3247:
--

How about do #1, prompt the user if they'd like to do #2, and then do it if 
they say 'Y' ?

 Improve bootstrapStandby behavior when original NN is not active
 

 Key: HDFS-3247
 URL: https://issues.apache.org/jira/browse/HDFS-3247
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: ha
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor

 Currently, if you run bootstrapStandby while the first NN is in standby mode, 
 it will spit out an ugly StandbyException with a trace. Instead, it should 
 print an explanation that you should transition the first NN to active before 
 bootstrapping.

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message

2012-04-10 Thread Colin Patrick McCabe (Created) (JIRA)

bootstrapstanby repeated twice in hdfs namenode usage message
-

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor


The HDFS usage message repeats bootstrapStandby twice.

{code}
Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
[-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
[-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
[-recover [ -force ] ]
{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-3248) bootstrapstanby repeated twice in hdfs namenode usage message

2012-04-10 Thread Colin Patrick McCabe (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colin Patrick McCabe updated HDFS-3248:
---

Status: Patch Available  (was: Open)

 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3248) bootstrapstanby repeated twice in hdfs namenode usage message

2012-04-10 Thread Colin Patrick McCabe (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colin Patrick McCabe updated HDFS-3248:
---

Attachment: HDFS-3248.002.patch

 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3245) Add metrics and web UI for cluster version summary


[ 
https://issues.apache.org/jira/browse/HDFS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251052#comment-13251052
 ] 

Robert Joseph Evans commented on HDFS-3245:
---

That makes since.

 Add metrics and web UI for cluster version summary
 --

 Key: HDFS-3245
 URL: https://issues.apache.org/jira/browse/HDFS-3245
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon

 With the introduction of protocol compatibility, once HDFS-2983 is committed, 
 we have the possibility that different nodes in a cluster are running 
 different software versions. To aid operators, we should add the ability to 
 summarize the status of versions in the cluster, so they can easily determine 
 whether a rolling upgrade is in progress or if some nodes missed an upgrade 
 (eg maybe they were out of service when the software was updated)

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message


[ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251102#comment-13251102
 ] 

Hadoop QA commented on HDFS-3248:
-

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12522163/HDFS-3248.002.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 eclipse:eclipse.  The patch built with eclipse:eclipse.

+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/2244//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2244//console

This message is automatically generated.

 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3213) JournalDaemon (server) should persist the cluster id and nsid in the storage directory

2012-04-10 Thread Hari Mankude (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251105#comment-13251105
 ] 

Hari Mankude commented on HDFS-3213:


Attached a patch for branch-3092. Not sure if jenkins run can be started on the 
branch.

 JournalDaemon (server) should persist the cluster id and nsid in the storage 
 directory
 --

 Key: HDFS-3213
 URL: https://issues.apache.org/jira/browse/HDFS-3213
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: ha, name-node
Reporter: Hari Mankude
Assignee: Hari Mankude
 Attachments: hdfs-3213.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HDFS-3213) JournalDaemon (server) should persist the cluster id and nsid in the storage directory

2012-04-10 Thread Hari Mankude (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hari Mankude updated HDFS-3213:
---

Attachment: hdfs-3213.patch

 JournalDaemon (server) should persist the cluster id and nsid in the storage 
 directory
 --

 Key: HDFS-3213
 URL: https://issues.apache.org/jira/browse/HDFS-3213
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: ha, name-node
Reporter: Hari Mankude
Assignee: Hari Mankude
 Attachments: hdfs-3213.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HDFS-3094) add -nonInteractive and -force option to namenode -format command


[ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251118#comment-13251118
 ] 

Todd Lipcon commented on HDFS-3094:
---

+1, I'll commit this momentarily

 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-3094) add -nonInteractive and -force option to namenode -format command


 [ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3094:
--

   Resolution: Fixed
Fix Version/s: 2.0.0
 Release Note: The 'namenode -format' command now supports the flags 
'-nonInteractive' and '-force' to improve usefulness without user input.
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Committed to branch-2 and trunk. Thanks, Arpit.

 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Fix For: 2.0.0

 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message


[ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251123#comment-13251123
 ] 

Todd Lipcon commented on HDFS-3248:
---

+1, thanks for fixing this.

 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3244) Remove dead writable code from hdfs/protocol


[ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251122#comment-13251122
 ] 

Todd Lipcon commented on HDFS-3244:
---

+1, thanks for the cleanup, glad to be rid of that code.

 Remove dead writable code from hdfs/protocol
 

 Key: HDFS-3244
 URL: https://issues.apache.org/jira/browse/HDFS-3244
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins
 Attachments: hdfs-3244.txt


 While doing HDFS-3238 I noticed that there's more dead writable code in 
 hdfs/protocol. Let's remove it.

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message


 [ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3248:
--

   Resolution: Fixed
Fix Version/s: 2.0.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Committed to branch-2 and trunk, thanks Colin.

 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Fix For: 2.0.0

 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3243) TestParallelRead timing out on jenkins


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251127#comment-13251127
 ] 

Todd Lipcon commented on HDFS-3243:
---

+1, verified in the test results above that TestParallelRead passed relatively 
quickly.

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-2696) fuse-dfs build problems

2012-04-10 Thread Updated


 [ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Mahé updated HDFS-2696:
-

Attachment: HDFS-2696-maven-all.patch
HDFS-2696-maven-part-2.patch

Attaching 2 patches:
* HDFS-2696-maven-part-2 - patch to be applied on top of the previous one, in 
case you would like to see what is different from the previous one
* HDFS-2696-maven-all.patch - Complete patch that includes both patches. 

 fuse-dfs build problems
 ---

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch, 
 HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch, 
 HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-3243) TestParallelRead timing out on jenkins


 [ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3243:
--

   Resolution: Fixed
Fix Version/s: 3.0.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Committed to trunk, thanks

 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Fix For: 3.0.0

 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message


[ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251132#comment-13251132
 ] 

Hudson commented on HDFS-3248:
--

Integrated in Hadoop-Hdfs-trunk-Commit #2120 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2120/])
HDFS-3248. bootstrapStandby repeated twice in hdfs namenode usage message. 
Contributed by Colin Patrick McCabe. (Revision 1312028)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312028
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java


 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Fix For: 2.0.0

 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3094) add -nonInteractive and -force option to namenode -format command


[ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251133#comment-13251133
 ] 

Hudson commented on HDFS-3094:
--

Integrated in Hadoop-Hdfs-trunk-Commit #2120 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2120/])
HDFS-3094. add -nonInteractive and -force option to namenode -format 
command. Contributed by Arpit Gupta. (Revision 1312025)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312025
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/HdfsServerConstants.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestClusterId.java


 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Fix For: 2.0.0

 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-3243) TestParallelRead timing out on jenkins


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251134#comment-13251134
 ] 

Hudson commented on HDFS-3243:
--

Integrated in Hadoop-Common-trunk-Commit #2046 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2046/])
HDFS-3243. TestParallelRead timing out on jenkins. Contributed by Henry 
Robinson. (Revision 1312029)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312029
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestParallelReadUtil.java


 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Fix For: 3.0.0

 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message


[ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251135#comment-13251135
 ] 

Hudson commented on HDFS-3248:
--

Integrated in Hadoop-Common-trunk-Commit #2046 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2046/])
HDFS-3248. bootstrapStandby repeated twice in hdfs namenode usage message. 
Contributed by Colin Patrick McCabe. (Revision 1312028)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312028
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java


 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Fix For: 2.0.0

 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3243) TestParallelRead timing out on jenkins


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251131#comment-13251131
 ] 

Hudson commented on HDFS-3243:
--

Integrated in Hadoop-Hdfs-trunk-Commit #2120 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2120/])
HDFS-3243. TestParallelRead timing out on jenkins. Contributed by Henry 
Robinson. (Revision 1312029)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312029
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestParallelReadUtil.java


 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Fix For: 3.0.0

 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3094) add -nonInteractive and -force option to namenode -format command


[ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251136#comment-13251136
 ] 

Hudson commented on HDFS-3094:
--

Integrated in Hadoop-Common-trunk-Commit #2046 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2046/])
HDFS-3094. add -nonInteractive and -force option to namenode -format 
command. Contributed by Arpit Gupta. (Revision 1312025)

 Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312025
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/HdfsServerConstants.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestClusterId.java


 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Fix For: 2.0.0

 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-3246) pRead equivalent for direct read path

2012-04-10 Thread Konstantin Shvachko (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251137#comment-13251137
 ] 

Todd Lipcon commented on HDFS-3246:
---

Agreed -- this would be particularly useful for HBase which does a lot of preads

 pRead equivalent for direct read path
 -

 Key: HDFS-3246
 URL: https://issues.apache.org/jira/browse/HDFS-3246
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Henry Robinson
Assignee: Henry Robinson

 There is no pread equivalent in ByteBufferReadable. We should consider adding 
 one. It would be relatively easy to implement for the distributed case 
 (certainly compared to HDFS-2834), since DFSInputStream does most of the 
 heavy lifting.

--
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-2983) Relax the build version check to permit rolling upgrades within a release


[ 
https://issues.apache.org/jira/browse/HDFS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251148#comment-13251148
 ] 

Konstantin Shvachko commented on HDFS-2983:
---

Yes that summarizes what I was asking. Thanks.

 Relax the build version check to permit rolling upgrades within a release
 -

 Key: HDFS-2983
 URL: https://issues.apache.org/jira/browse/HDFS-2983
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Aaron T. Myers
 Attachments: HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, 
 HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch


 Currently the version check for DN/NN communication is strict (it checks the 
 exact svn revision or git hash, Storage#getBuildVersion calls 
 VersionInfo#getRevision), which prevents rolling upgrades across any 
 releases. Once we have the PB-base RPC in place (coming soon to branch-23) 
 we'll have the necessary pieces in place to loosen this restriction, though 
 perhaps it takes another 23 minor release or so before we're ready to commit 
 to making the minor versions compatible.

--
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-2983) Relax the build version check to permit rolling upgrades within a release


[ 
https://issues.apache.org/jira/browse/HDFS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251150#comment-13251150
 ] 

Todd Lipcon commented on HDFS-2983:
---

Cool, thanks Konstantin. Aaron, does the above proposal sound good to you too? 
Happy to re-review when you update the patch

 Relax the build version check to permit rolling upgrades within a release
 -

 Key: HDFS-2983
 URL: https://issues.apache.org/jira/browse/HDFS-2983
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Aaron T. Myers
 Attachments: HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, 
 HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch


 Currently the version check for DN/NN communication is strict (it checks the 
 exact svn revision or git hash, Storage#getBuildVersion calls 
 VersionInfo#getRevision), which prevents rolling upgrades across any 
 releases. Once we have the PB-base RPC in place (coming soon to branch-23) 
 we'll have the necessary pieces in place to loosen this restriction, though 
 perhaps it takes another 23 minor release or so before we're ready to commit 
 to making the minor versions compatible.

--
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-2983) Relax the build version check to permit rolling upgrades within a release

2012-04-10 Thread Aaron T. Myers (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HDFS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251152#comment-13251152
]

Aaron T. Myers commented on HDFS-2983:
--

All sounds good to me. I'll go ahead and implement the ctime check and upload a
new patch.

Thanks a lot for the feedback, Konstantin.

Relax the build version check to permit rolling upgrades within a release
-

Key: HDFS-2983
URL: https://issues.apache.org/jira/browse/HDFS-2983
Project: Hadoop HDFS
Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Aaron T. Myers
Attachments: HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch,
HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch

Currently the version check for DN/NN communication is strict (it checks the
exact svn revision or git hash, Storage#getBuildVersion calls
VersionInfo#getRevision), which prevents rolling upgrades across any
releases. Once we have the PB-base RPC in place (coming soon to branch-23)
we'll have the necessary pieces in place to loosen this restriction, though
perhaps it takes another 23 minor release or so before we're ready to commit
to making the minor versions compatible.

[jira] [Commented] (HDFS-3094) add -nonInteractive and -force option to namenode -format command

2012-04-10 Thread Arpit Gupta (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251153#comment-13251153
 ] 

Arpit Gupta commented on HDFS-3094:
---

Todd thanks for committing the patch. I had created HADOOP-8185 for the doc 
changes for this patch. If you can take a look at that and see if it looks good 
to go.


Also have the branch 1.0 patch attached and i kept it in sync when i made 
changes based on reviews. If you can take a look that will be great.

 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Fix For: 2.0.0

 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-3248) bootstrapstanby repeated twice in hdfs namenode usage message


[ 
https://issues.apache.org/jira/browse/HDFS-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251168#comment-13251168
 ] 

Hudson commented on HDFS-3248:
--

Integrated in Hadoop-Mapreduce-trunk-Commit #2059 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2059/])
HDFS-3248. bootstrapStandby repeated twice in hdfs namenode usage message. 
Contributed by Colin Patrick McCabe. (Revision 1312028)

 Result = ABORTED
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312028
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java


 bootstrapstanby repeated twice in hdfs namenode usage message
 -

 Key: HDFS-3248
 URL: https://issues.apache.org/jira/browse/HDFS-3248
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
 Fix For: 2.0.0

 Attachments: HDFS-3248.002.patch


 The HDFS usage message repeats bootstrapStandby twice.
 {code}
 Usage: java NameNode [-backup] | [-checkpoint] | [-format[-clusterid cid ]] | 
 [-upgrade] | [-rollback] | [-finalize] | [-importCheckpoint] | 
 [-bootstrapStandby] | [-initializeSharedEdits] | [-bootstrapStandby] | 
 [-recover [ -force ] ]
 {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-3094) add -nonInteractive and -force option to namenode -format command


[ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251169#comment-13251169
 ] 

Hudson commented on HDFS-3094:
--

Integrated in Hadoop-Mapreduce-trunk-Commit #2059 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2059/])
HDFS-3094. add -nonInteractive and -force option to namenode -format 
command. Contributed by Arpit Gupta. (Revision 1312025)

 Result = ABORTED
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312025
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/HdfsServerConstants.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestClusterId.java


 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Fix For: 2.0.0

 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-3243) TestParallelRead timing out on jenkins


[ 
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251167#comment-13251167
 ] 

Hudson commented on HDFS-3243:
--

Integrated in Hadoop-Mapreduce-trunk-Commit #2059 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2059/])
HDFS-3243. TestParallelRead timing out on jenkins. Contributed by Henry 
Robinson. (Revision 1312029)

 Result = ABORTED
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312029
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestParallelReadUtil.java


 TestParallelRead timing out on jenkins
 --

 Key: HDFS-3243
 URL: https://issues.apache.org/jira/browse/HDFS-3243
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs client, test
Reporter: Todd Lipcon
Assignee: Henry Robinson
 Fix For: 3.0.0

 Attachments: HDFS-3243.0.patch


 Trunk builds have been failing recently due to a TestParallelRead timeout. It 
 doesn't report in the Jenkins failure list because surefire handles timeouts 
 really poorly.

--
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-3094) add -nonInteractive and -force option to namenode -format command

2012-04-10 Thread Todd Lipcon (Reopened) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon reopened HDFS-3094:
---


Ah, sorry, forgot about branch-1. I'll look at that later tonight or tomorrow, 
as well as the docs. Reopening so it doesn't get lost

 add -nonInteractive and -force option to namenode -format command
 -

 Key: HDFS-3094
 URL: https://issues.apache.org/jira/browse/HDFS-3094
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 0.24.0, 1.0.2
Reporter: Arpit Gupta
Assignee: Arpit Gupta
 Fix For: 2.0.0

 Attachments: HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, 
 HDFS-3094.branch-1.0.patch, HDFS-3094.branch-1.0.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, HDFS-3094.patch, 
 HDFS-3094.patch, HDFS-3094.patch


 Currently the bin/hadoop namenode -format prompts the user for a Y/N to setup 
 the directories in the local file system.
 -force : namenode formats the directories without prompting
 -nonInterActive : namenode format will return with an exit code of 1 if the 
 dir exists.

--
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-2696) fuse-dfs build problems

[
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251191#comment-13251191
]

Hadoop QA commented on HDFS-2696:
-

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12522172/HDFS-2696-maven-all.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 eclipse:eclipse. The patch built with eclipse:eclipse.

+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/2245//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2245//console

This message is automatically generated.

fuse-dfs build problems
---

Key: HDFS-2696
URL: https://issues.apache.org/jira/browse/HDFS-2696
Project: Hadoop HDFS
Issue Type: Bug
Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
Labels: bigtop
Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch,
HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch,
HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip

fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches.
Some details on how to compile fuse-dfs on 0.23 is here :
http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
and a wiki page follows.
The attached patch removes some problems (an inexistnant
ivy/library.properties, detecting jni.h location).

[jira] [Created] (HDFS-3249) Use ToolRunner.confirmPrompt in NameNode

Use ToolRunner.confirmPrompt in NameNode


 Key: HDFS-3249
 URL: https://issues.apache.org/jira/browse/HDFS-3249
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial


One of the recent patches in common copied NameNode.confirmPrompt to be part of 
ToolRunner, so it's available as utility code. We should now use this utility 
function from within NameNode.java instead of having two copies.

--
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-3249) Use ToolRunner.confirmPrompt in NameNode


 [ 
https://issues.apache.org/jira/browse/HDFS-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3249:
--

Status: Patch Available  (was: Open)

 Use ToolRunner.confirmPrompt in NameNode
 

 Key: HDFS-3249
 URL: https://issues.apache.org/jira/browse/HDFS-3249
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Attachments: hdfs-3249.txt


 One of the recent patches in common copied NameNode.confirmPrompt to be part 
 of ToolRunner, so it's available as utility code. We should now use this 
 utility function from within NameNode.java instead of having two copies.

--
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-3249) Use ToolRunner.confirmPrompt in NameNode


 [ 
https://issues.apache.org/jira/browse/HDFS-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3249:
--

Attachment: hdfs-3249.txt

trivial patch

 Use ToolRunner.confirmPrompt in NameNode
 

 Key: HDFS-3249
 URL: https://issues.apache.org/jira/browse/HDFS-3249
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Attachments: hdfs-3249.txt


 One of the recent patches in common copied NameNode.confirmPrompt to be part 
 of ToolRunner, so it's available as utility code. We should now use this 
 utility function from within NameNode.java instead of having two copies.

--
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-3249) Use ToolRunner.confirmPrompt in NameNode

2012-04-10 Thread Aaron T. Myers (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251215#comment-13251215
 ] 

Aaron T. Myers commented on HDFS-3249:
--

+1 pending Jenkins.

 Use ToolRunner.confirmPrompt in NameNode
 

 Key: HDFS-3249
 URL: https://issues.apache.org/jira/browse/HDFS-3249
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
 Attachments: hdfs-3249.txt


 One of the recent patches in common copied NameNode.confirmPrompt to be part 
 of ToolRunner, so it's available as utility code. We should now use this 
 utility function from within NameNode.java instead of having two copies.

--
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-3213) JournalDaemon (server) should persist the cluster id and nsid in the storage directory

2012-04-10 Thread Hari Mankude (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hari Mankude updated HDFS-3213:
---

Attachment: hdfs-3213-1.patch

 JournalDaemon (server) should persist the cluster id and nsid in the storage 
 directory
 --

 Key: HDFS-3213
 URL: https://issues.apache.org/jira/browse/HDFS-3213
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: ha, name-node
Reporter: Hari Mankude
Assignee: Hari Mankude
 Attachments: hdfs-3213-1.patch, hdfs-3213.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HDFS-3244) Remove dead writable code from hdfs/protocol


[ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251224#comment-13251224
 ] 

Hudson commented on HDFS-3244:
--

Integrated in Hadoop-Hdfs-trunk-Commit #2121 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2121/])
HDFS-3244. Remove dead writable code from hdfs/protocol. Contributed by Eli 
Collins (Revision 1312061)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312061
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/BlockLocalPathInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientDatanodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/CorruptFileBlocks.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeID.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DirectoryListing.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ExtendedBlock.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/HdfsFileStatus.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/HdfsLocatedFileStatus.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LocatedBlock.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LocatedBlocks.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientDatanodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/GetUserMappingsProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/NamenodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/RefreshAuthorizationPolicyProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/RefreshUserMappingsProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolR23Compatible
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeDescriptor.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/StorageInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/UpgradeStatusReport.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/CheckpointSignature.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockRecoveryCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlocksWithLocations.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeRegistration.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/HeartbeatResponse.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/InterDatanodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NNHAStatusHeartbeat.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeRegistration.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamespaceInfo.java
*

[jira] [Commented] (HDFS-3244) Remove dead writable code from hdfs/protocol


[ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251225#comment-13251225
 ] 

Hudson commented on HDFS-3244:
--

Integrated in Hadoop-Common-trunk-Commit #2047 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2047/])
HDFS-3244. Remove dead writable code from hdfs/protocol. Contributed by Eli 
Collins (Revision 1312061)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312061
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/BlockLocalPathInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientDatanodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/CorruptFileBlocks.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeID.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DirectoryListing.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ExtendedBlock.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/HdfsFileStatus.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/HdfsLocatedFileStatus.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LocatedBlock.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LocatedBlocks.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientDatanodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/GetUserMappingsProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/NamenodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/RefreshAuthorizationPolicyProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/RefreshUserMappingsProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolR23Compatible
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeDescriptor.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/StorageInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/UpgradeStatusReport.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/CheckpointSignature.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockRecoveryCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlocksWithLocations.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeRegistration.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/HeartbeatResponse.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/InterDatanodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NNHAStatusHeartbeat.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeRegistration.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamespaceInfo.java
*

[jira] [Updated] (HDFS-3244) Remove dead writable code from hdfs/protocol


 [ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3244:
--

  Resolution: Fixed
   Fix Version/s: 2.0.0
Target Version/s:   (was: 2.0.0)
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Thanks for the review Todd. I've committed this and merged.

 Remove dead writable code from hdfs/protocol
 

 Key: HDFS-3244
 URL: https://issues.apache.org/jira/browse/HDFS-3244
 Project: Hadoop HDFS
  Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins
 Fix For: 2.0.0

 Attachments: hdfs-3244.txt


 While doing HDFS-3238 I noticed that there's more dead writable code in 
 hdfs/protocol. Let's remove it.

--
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-3247) Improve bootstrapStandby behavior when original NN is not active


 [ 
https://issues.apache.org/jira/browse/HDFS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3247:
--

Attachment: hdfs-3247.txt

Attached patch implements Aaron's idea above.

 Improve bootstrapStandby behavior when original NN is not active
 

 Key: HDFS-3247
 URL: https://issues.apache.org/jira/browse/HDFS-3247
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: ha
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor
 Attachments: hdfs-3247.txt


 Currently, if you run bootstrapStandby while the first NN is in standby mode, 
 it will spit out an ugly StandbyException with a trace. Instead, it should 
 print an explanation that you should transition the first NN to active before 
 bootstrapping.

--
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-3247) Improve bootstrapStandby behavior when original NN is not active


 [ 
https://issues.apache.org/jira/browse/HDFS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon updated HDFS-3247:
--

Status: Patch Available  (was: Open)

 Improve bootstrapStandby behavior when original NN is not active
 

 Key: HDFS-3247
 URL: https://issues.apache.org/jira/browse/HDFS-3247
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: ha
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor
 Attachments: hdfs-3247.txt


 Currently, if you run bootstrapStandby while the first NN is in standby mode, 
 it will spit out an ugly StandbyException with a trace. Instead, it should 
 print an explanation that you should transition the first NN to active before 
 bootstrapping.

--
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-3244) Remove dead writable code from hdfs/protocol

2012-04-10 Thread Uma Maheswara Rao G (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251232#comment-13251232
 ] 

Hudson commented on HDFS-3244:
--

Integrated in Hadoop-Mapreduce-trunk-Commit #2060 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2060/])
HDFS-3244. Remove dead writable code from hdfs/protocol. Contributed by Eli 
Collins (Revision 1312061)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312061
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/BlockLocalPathInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientDatanodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/CorruptFileBlocks.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeID.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DirectoryListing.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ExtendedBlock.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/HdfsFileStatus.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/HdfsLocatedFileStatus.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LocatedBlock.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/LocatedBlocks.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientDatanodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/GetUserMappingsProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/NamenodeProtocolTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/RefreshAuthorizationPolicyProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/RefreshUserMappingsProtocolClientSideTranslatorPB.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolR23Compatible
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeDescriptor.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/StorageInfo.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/UpgradeStatusReport.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/CheckpointSignature.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockRecoveryCommand.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlocksWithLocations.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeRegistration.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/HeartbeatResponse.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/InterDatanodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NNHAStatusHeartbeat.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeProtocol.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamenodeRegistration.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/NamespaceInfo.java
*

[jira] [Commented] (HDFS-3179) Improve the error message: DataStreamer throw an exception, nodes.length != original.length + 1 on single datanode cluster


[ 
https://issues.apache.org/jira/browse/HDFS-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251240#comment-13251240
 ] 

Uma Maheswara Rao G commented on HDFS-3179:
---

+1 looks good to me.
Will commit this patch today.

 Improve the error message: DataStreamer throw an exception, nodes.length != 
 original.length + 1 on single datanode cluster
 

 Key: HDFS-3179
 URL: https://issues.apache.org/jira/browse/HDFS-3179
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: hdfs client
Affects Versions: 0.23.2
Reporter: Zhanwei.Wang
Assignee: Tsz Wo (Nicholas), SZE
 Attachments: h3179_20120403.patch


 Create a single datanode cluster
 disable permissions
 enable webhfds
 start hdfs
 run the test script
 expected result:
 a file named test is created and the content is testtest
 the result I got:
 hdfs throw an exception on the second append operation.
 {code}
 ./test.sh 
 {RemoteException:{exception:IOException,javaClassName:java.io.IOException,message:Failed
  to add a datanode: nodes.length != original.length + 1, 
 nodes=[127.0.0.1:50010], original=[127.0.0.1:50010]}}
 {code}
 Log in datanode:
 {code}
 2012-04-02 14:34:21,058 WARN org.apache.hadoop.hdfs.DFSClient: DataStreamer 
 Exception
 java.io.IOException: Failed to add a datanode: nodes.length != 
 original.length + 1, nodes=[127.0.0.1:50010], original=[127.0.0.1:50010]
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.findNewDatanode(DFSOutputStream.java:778)
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.addDatanode2ExistingPipeline(DFSOutputStream.java:834)
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.setupPipelineForAppendOrRecovery(DFSOutputStream.java:930)
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:461)
 2012-04-02 14:34:21,059 ERROR org.apache.hadoop.hdfs.DFSClient: Failed to 
 close file /test
 java.io.IOException: Failed to add a datanode: nodes.length != 
 original.length + 1, nodes=[127.0.0.1:50010], original=[127.0.0.1:50010]
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.findNewDatanode(DFSOutputStream.java:778)
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.addDatanode2ExistingPipeline(DFSOutputStream.java:834)
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.setupPipelineForAppendOrRecovery(DFSOutputStream.java:930)
   at 
 org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:461)
 {code}
 test.sh
 {code}
 #!/bin/sh
 echo test  test.txt
 curl -L -X PUT http://localhost:50070/webhdfs/v1/test?op=CREATE;
 curl -L -X POST -T test.txt http://localhost:50070/webhdfs/v1/test?op=APPEND;
 curl -L -X POST -T test.txt http://localhost:50070/webhdfs/v1/test?op=APPEND;
 {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-3250) Get the fuse-dfs test running

Get the fuse-dfs test running
-

 Key: HDFS-3250
 URL: https://issues.apache.org/jira/browse/HDFS-3250
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: contrib/fuse-dfs, test
Reporter: Eli Collins


Now that fuse-dfs is building again (HDFS-2696) let's get the test running.

--
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-3251) Mavenize the fuse-dfs build

Mavenize the fuse-dfs build 


 Key: HDFS-3251
 URL: https://issues.apache.org/jira/browse/HDFS-3251
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: build, contrib/fuse-dfs
Reporter: Eli Collins


The fuse-dfs build still uses the old ant-based build, let's integrate it as 
part of the maven build. Looks like we need to introduce sub-directories under 
src/main/native as libhdfs is there (w/o it's own subdirectory).

--
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-3252) Include fuse-dfs in the tarball

Include fuse-dfs in the tarball
---

 Key: HDFS-3252
 URL: https://issues.apache.org/jira/browse/HDFS-3252
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: build, contrib/fuse-dfs
Reporter: Eli Collins


The fuse-dfs binary needs to be included in the binary tarball.

--
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-3251) Mavenize the fuse-dfs build


 [ 
https://issues.apache.org/jira/browse/HDFS-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3251:
--

Target Version/s: 2.0.0

 Mavenize the fuse-dfs build 
 

 Key: HDFS-3251
 URL: https://issues.apache.org/jira/browse/HDFS-3251
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: build, contrib/fuse-dfs
Reporter: Eli Collins

 The fuse-dfs build still uses the old ant-based build, let's integrate it as 
 part of the maven build. Looks like we need to introduce sub-directories 
 under src/main/native as libhdfs is there (w/o it's own subdirectory).

--
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-2696) Fix the fuse-fds build


 [ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-2696:
--

Summary: Fix the fuse-fds build  (was: fuse-dfs build problems)

 Fix the fuse-fds build
 --

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch, 
 HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch, 
 HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-2696) fuse-dfs build problems

2012-04-10 Thread Eli Collins (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251242#comment-13251242
 ] 

Eli Collins commented on HDFS-2696:
---

+1 looks great. I tested that fuse-dfs now build when -Pfuse and -Pnative are 
passed. No new unit test is necessary since this just impacts the build.

Btw I filed HDFS-3250, HDFS-3251, and HDFS-3252 for mavenizing the build, 
including it in the tarball and getting the test running.


 fuse-dfs build problems
 ---

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch, 
 HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch, 
 HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-2696) Fix the fuse-fds build

2012-04-10 Thread Tsz Wo (Nicholas), SZE (Commented) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-2696:
--

  Resolution: Fixed
   Fix Version/s: 2.0.0
Target Version/s:   (was: 2.0.0)
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

I've committed this and merged to branch-2. Thanks Bruno!

 Fix the fuse-fds build
 --

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Fix For: 2.0.0

 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch, 
 HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch, 
 HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-3213) JournalDaemon (server) should persist the cluster id and nsid in the storage directory


[ 
https://issues.apache.org/jira/browse/HDFS-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251249#comment-13251249
 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-3213:
--

- In JournalService.fence(..), should the setupStorage(..) call be after 
verifyFence(..) and verify(..)?
- JournalService.conf is only used in setupStorage(..).  Instead of adding it 
as a field, it is better to replace it with NNStorage since the conf values are 
fixed.  We don't have to create the objects in setupStorage(..).
- Need to add Assert.fail() after fence(..) in the new tests.  Otherwise, the 
test will pass even if fence(..) does not throw exceptions.  I think it is 
better to print out the exception in the catch-blocks instead of leaving them 
empty.

In addition, we need to think about how to synchronize the methods in 
JournalService.  Do you want to do it here or in a separated issue?

 JournalDaemon (server) should persist the cluster id and nsid in the storage 
 directory
 --

 Key: HDFS-3213
 URL: https://issues.apache.org/jira/browse/HDFS-3213
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: ha, name-node
Reporter: Hari Mankude
Assignee: Hari Mankude
 Attachments: hdfs-3213-1.patch, hdfs-3213.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HDFS-2696) Fix the fuse-fds build


[ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251250#comment-13251250
 ] 

Hudson commented on HDFS-2696:
--

Integrated in Hadoop-Hdfs-trunk-Commit #2122 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2122/])
HDFS-2696. Fix the fuse-fds build. Contributed by Bruno Mahé (Revision 
1312068)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312068
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/build-contrib.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/build.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/build-contrib.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/build.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/pom.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/src/Makefile.am
* /hadoop/common/trunk/hadoop-hdfs-project/pom.xml


 Fix the fuse-fds build
 --

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Fix For: 2.0.0

 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch, 
 HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch, 
 HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-2696) Fix the fuse-fds build


[ 
https://issues.apache.org/jira/browse/HDFS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251252#comment-13251252
 ] 

Hudson commented on HDFS-2696:
--

Integrated in Hadoop-Common-trunk-Commit #2048 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2048/])
HDFS-2696. Fix the fuse-fds build. Contributed by Bruno Mahé (Revision 
1312068)

 Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1312068
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/build-contrib.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/build.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/build-contrib.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/build.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/pom.xml
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/fuse-dfs/src/Makefile.am
* /hadoop/common/trunk/hadoop-hdfs-project/pom.xml


 Fix the fuse-fds build
 --

 Key: HDFS-2696
 URL: https://issues.apache.org/jira/browse/HDFS-2696
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build, contrib/fuse-dfs
Affects Versions: 0.23.0
 Environment: linux
Reporter: Petru Dimulescu
Assignee: Bruno Mahé
  Labels: bigtop
 Fix For: 2.0.0

 Attachments: HDFS-2696-complete.patch, HDFS-2696-maven-all.patch, 
 HDFS-2696-maven-part-2.patch, HDFS-2696-maven.patch, HDFS-2696-plus.patch, 
 HDFS-2696-rewrite.patch, dfsfuse-build.patch.zip


 fuse-dfs has some compilation problems on the 0.23 and 0.24(head) branches. 
 Some details on how to compile fuse-dfs on 0.23 is here : 
 http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201112.mbox/%3c4ee23195.7030...@gmail.com%3E
  and a wiki page follows. 
 The attached patch removes some problems (an inexistnant 
 ivy/library.properties, detecting jni.h location).

--
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-3249) Use ToolRunner.confirmPrompt in NameNode

[
https://issues.apache.org/jira/browse/HDFS-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251253#comment-13251253
]

Hadoop QA commented on HDFS-3249:
-

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522182/hdfs-3249.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+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 eclipse:eclipse. The patch built with eclipse:eclipse.

+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/2246//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2246//console

This message is automatically generated.

Use ToolRunner.confirmPrompt in NameNode

Key: HDFS-3249
URL: https://issues.apache.org/jira/browse/HDFS-3249
Project: Hadoop HDFS
Issue Type: Improvement
Components: name-node
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Trivial
Attachments: hdfs-3249.txt

One of the recent patches in common copied NameNode.confirmPrompt to be part
of ToolRunner, so it's available as utility code. We should now use this
utility function from within NameNode.java instead of having two copies.

[jira] [Updated] (HDFS-2983) Relax the build version check to permit rolling upgrades within a release

2012-04-10 Thread Aaron T. Myers (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDFS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron T. Myers updated HDFS-2983:
-

Attachment: HDFS-2983.patch

Here's an updated patch which is rebased on trunk and adds a check for CTime 
being different when the NN and DN versions don't match exactly.

 Relax the build version check to permit rolling upgrades within a release
 -

 Key: HDFS-2983
 URL: https://issues.apache.org/jira/browse/HDFS-2983
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Eli Collins
Assignee: Aaron T. Myers
 Attachments: HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, 
 HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, HDFS-2983.patch, 
 HDFS-2983.patch


 Currently the version check for DN/NN communication is strict (it checks the 
 exact svn revision or git hash, Storage#getBuildVersion calls 
 VersionInfo#getRevision), which prevents rolling upgrades across any 
 releases. Once we have the PB-base RPC in place (coming soon to branch-23) 
 we'll have the necessary pieces in place to loosen this restriction, though 
 perhaps it takes another 23 minor release or so before we're ready to commit 
 to making the minor versions compatible.

--
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-2696) Fix the fuse-fds build