date:20160116

[jira] [Created] (HDFS-9654) Code refactoring for HDFS-8578

2016-01-16 Thread Tsz Wo Nicholas Sze (JIRA)

Tsz Wo Nicholas Sze created HDFS-9654:
-

 Summary: Code refactoring for HDFS-8578
 Key: HDFS-9654
 URL: https://issues.apache.org/jira/browse/HDFS-9654
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: datanode
Reporter: Tsz Wo Nicholas Sze
Assignee: Tsz Wo Nicholas Sze
Priority: Minor


This is a code refactoring JIRA in order to change Datanode to process all 
storage/data dirs in parallel; see also HDFS-8578.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HDFS-9655) NN should start JVM pause monitor before loading fsimage

2016-01-16 Thread John Zhuge (JIRA)

John Zhuge created HDFS-9655:


 Summary: NN should start JVM pause monitor before loading fsimage
 Key: HDFS-9655
 URL: https://issues.apache.org/jira/browse/HDFS-9655
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: John Zhuge
Assignee: John Zhuge
Priority: Critical


We have seen many cases of NameNode startup either extremely slow or even hung. 
Most of them were caused by insufficient heap size with regard to the metadata 
size. Those cases were resolved by increasing the heap size.

However it did take support team some time to root cause. JVM pause warning 
messages would greatly assist in such diagnosis, but NN starts JVM pause 
monitor after fsimage/edits loading.

Propose to start JVM pause monitor before loading fsimage/edits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-16 Thread Akira AJISAKA

Hi Xiao,

>  From a quick comparison between the releasenotes.html and the 
CHANGES.txt

> files in source tarball, the number of total JIRAs is quite different.

In CHANGES.txt, JIRAs fixed in 2.6.1/2.6.2 are not in 2.7.2.
That is why the number of JIRAs are different.

Regards,
Akira

On 1/16/16 09:11, Xiao Chen wrote:

Thanks Vinod for preparing the release package.

+1 (non-binding).

I verified the following:

- Successfully downloaded source tarball, verified md5
- Ran `mvn apache-rat:check` on source tarball, passed
- Successfully built from source tarball
- Successfully started a pseudo distributed cluster
- Ran some basic hdfs operations, then successfully ran a distcp

1 question:
 From a quick comparison between the releasenotes.html and the CHANGES.txt
files in source tarball, the number of total JIRAs is quite different.
Seems like CHANGES.txt misses some of the fixes, because Searching

'project
in (HDFS, HADOOP, MAPREDUCE, YARN) AND resolution = Fixed AND fixVersion =
2.7.2' from JIRA agrees with releasenotes.html (count=155).

Here is how I did the check:

-  cat ~/Downloads/releasenotes.html |grep "
https://issues.apache.org/jira/"; | awk -F ">" '{print $3}'|awk -F "<"
'{print $1}' |wc -l

  returns 155

- for f in `find . -name CHANGES.txt |grep -v target`; do cat $f |grep
-B 1 "Release 2.7.1" |grep .*-[0-9] |grep -v "Release 2.7" ; done|wc -l

 returns 103

I'm not sure whether this is a problem or not.
Best,
-Xiao

On Thu, Jan 14, 2016 at 8:57 PM, Vinod Kumar Vavilapalli 
wrote:

Hi all,

I've created an updated release candidate RC2 for Apache Hadoop 2.7.2.

As discussed before, this is the next maintenance release to follow up
2.7.1.

The RC is available for validation at:
http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/

The RC tag in git is: release-2.7.2-RC2

The maven artifacts are available via repository.apache.org <
http://repository.apache.org/> at
https://repository.apache.org/content/repositories/orgapachehadoop-1027 <
https://repository.apache.org/content/repositories/orgapachehadoop-1027>

The release-notes are inside the tar-balls at location
hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
hosted this at
http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/releasenotes.html <
http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html> for
your quick perusal.

As you may have noted,
  - I terminated the RC1 related voting thread after finding out that we
didn’t have a bunch of patches that are already in the released 2.6.3
version. After a brief discussion, we decided to keep the parallel 2.6.x
and 2.7.x releases incremental, see [4] for this discussion.
  - The RC0 related voting thread got halted due to some critical issues.
It took a while again for getting all those blockers out of the way. See
the previous voting thread [3] for details.
  - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
quite a bit. This release's related discussion threads are linked below:
[1] and [2].

Please try the release and vote; the vote will run for the usual 5 days.

Thanks,
Vinod

[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2
http://markmail.org/message/iktqss2qdeykgpqk <
http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
http://markmail.org/message/5txhvr2qdiqglrwc <
http://markmail.org/message/5txhvr2qdiqglrwc>
[4] Retracted [VOTE] Release Apache Hadoop 2.7.2 RC1:
http://markmail.org/thread/n7ljbsnquihn3wlw

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #799

2016-01-16 Thread Apache Jenkins Server

See 

Changes:

[szetszwo] In CHANGES.txt, move HDFS-9294 to Release 2.6.4.

[cnauroth] HADOOP-12691. Move files to correct location.

--
[...truncated 5767 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.568 sec - in 
org.apache.hadoop.hdfs.TestHDFSTrash
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestClientReportBadBlock
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.788 sec - in 
org.apache.hadoop.hdfs.TestClientReportBadBlock
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestWriteRead
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.066 sec - in 
org.apache.hadoop.hdfs.TestWriteRead
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestClientProtocolForPipelineRecovery
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 44.215 sec - in 
org.apache.hadoop.hdfs.TestClientProtocolForPipelineRecovery
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestBalancerBandwidth
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.256 sec - in 
org.apache.hadoop.hdfs.TestBalancerBandwidth
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestDFSUpgrade
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.084 sec - in 
org.apache.hadoop.hdfs.TestDFSUpgrade
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestBlockStoragePolicy
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 52.606 sec - 
in org.apache.hadoop.hdfs.TestBlockStoragePolicy
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestFileLengthOnClusterRestart
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.51 sec - in 
org.apache.hadoop.hdfs.TestFileLengthOnClusterRestart
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestLeaseRecoveryStriped
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 39 sec - in 
org.apache.hadoop.hdfs.TestLeaseRecoveryStriped
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.TestBlockReaderFactory
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.901 sec - in 
org.apache.hadoop.hdfs.TestBlockReaderFactory
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.TestSecureNNWithQJM
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.061 sec - in 
org.apache.hadoop.hdfs.qjournal.TestSecureNNWithQJM
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.TestNNWithQJM
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.829 sec - in 
org.apache.hadoop.hdfs.qjournal.TestNNWithQJM
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.server.TestJournalNodeMXBean
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.158 sec - in 
org.apache.hadoop.hdfs.qjournal.server.TestJournalNodeMXBean
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.server.TestJournal
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.189 sec - in 
org.apache.hadoop.hdfs.qjournal.server.TestJournal
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.server.TestJournalNode
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.078 sec - in 
org.apache.hadoop.hdfs.qjournal.server.TestJournalNode
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.client.TestIPCLoggerChannel
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.929 sec - in 
org.apache.hadoop.hdfs.qjournal.client.TestIPCLoggerChannel
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.hdfs.qjournal.client.TestQJMWithFaults
Tests run: 2, Failures: 0, Errors: 0,

Hadoop-Hdfs-trunk-Java8 - Build # 799 - Still Failing

2016-01-16 Thread Apache Jenkins Server

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/799/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 5960 lines...]
[INFO] --- maven-antrun-plugin:1.7:run (create-testdirs) @ hadoop-hdfs-project 
---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk-Java8/hadoop-hdfs-project/target/test-dir
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-source-plugin:2.3:jar-no-fork (hadoop-java-sources) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-source-plugin:2.3:test-jar-no-fork (hadoop-java-sources) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (dist-enforce) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.8.1:jar (module-javadocs) @ 
hadoop-hdfs-project ---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable 
package
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (depcheck) @ hadoop-hdfs-project 
---
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.15:checkstyle (default-cli) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.0:findbugs (default-cli) @ 
hadoop-hdfs-project ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop HDFS Client . SUCCESS [04:05 min]
[INFO] Apache Hadoop HDFS  FAILURE [  04:03 h]
[INFO] Apache Hadoop HDFS Native Client .. SKIPPED
[INFO] Apache Hadoop HttpFS .. SKIPPED
[INFO] Apache Hadoop HDFS BookKeeper Journal . SKIPPED
[INFO] Apache Hadoop HDFS-NFS  SKIPPED
[INFO] Apache Hadoop HDFS Project  SUCCESS [  0.067 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 04:07 h
[INFO] Finished at: 2016-01-16T20:54:02+00:00
[INFO] Final Memory: 56M/412M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project hadoop-hdfs: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk-Java8/hadoop-hdfs-project/hadoop-hdfs/target/surefire-reports
 for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :hadoop-hdfs
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: hdfs-dev@hadoop.apache.org
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  
org.apache.hadoop.hdfs.TestDFSUpgradeFromImage.testUpgradeFromRel1BBWImage

Error Message:
Cannot obtain block length for 
LocatedBlock{BP-760889174-67.195.81.152-1452974709374:blk_7162739548153522810_1020;
 getBlockSize()=1024; corrupt=false; offset=0; 
locs=[DatanodeInfoWithStorage[127.0.0.1:36501,DS-adcaa2e2-c5ab-49af-a09f-767738b94ade,DISK]]}

Stack Trace:
java.io.IOException: Cannot obtain block length for 
LocatedBlock{BP-760889174-67.195.81.152-1452974709374:blk_7162739548153522810_1020;
 getBlockSize()=1024; corrupt=false; offset=0; 
locs=[DatanodeInfoWithStorage[127.0.0.1:36501,DS-adcaa2e2-c5ab-49af-a09f-767738b94ade,DISK]]}
at 
org.apache.hadoop.hdfs.DFSInputStream.readBlockLength(DFSInputStream.java:436)
at 
org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:346)
at 
org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:279)
at org.apache.hadoop.hdfs.DFSInputStream.(DFSInputStream.java:268)
at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1046)
at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1011)
at 
org.apache.hadoop.hdfs.TestDFSUpgradeFromImage.dfsOpenFileWithRetries(TestDFSUpgradeFromImage.java:178)
at 
org.apache.hadoop.hdfs.TestDFSUpgradeFromImage.verifyDir(TestDFSU

Jenkins build is back to normal : Hadoop-Hdfs-trunk #2736

2016-01-16 Thread Apache Jenkins Server

See

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-16 Thread Xiao Chen

Got it, makes sense. Thanks Akira for answering!

-Xiao

On Sat, Jan 16, 2016 at 11:39 AM, Akira AJISAKA 
wrote:

> Hi Xiao,
>
> >  From a quick comparison between the releasenotes.html and the
> CHANGES.txt
> > files in source tarball, the number of total JIRAs is quite different.
>
> In CHANGES.txt, JIRAs fixed in 2.6.1/2.6.2 are not in 2.7.2.
> That is why the number of JIRAs are different.
>
> Regards,
> Akira
>
> On 1/16/16 09:11, Xiao Chen wrote:
>
>> Thanks Vinod for preparing the release package.
>>
>>
>> +1 (non-binding).
>>
>> I verified the following:
>>
>>
>> - Successfully downloaded source tarball, verified md5
>> - Ran `mvn apache-rat:check` on source tarball, passed
>> - Successfully built from source tarball
>> - Successfully started a pseudo distributed cluster
>> - Ran some basic hdfs operations, then successfully ran a distcp
>>
>>
>> 1 question:
>>  From a quick comparison between the releasenotes.html and the CHANGES.txt
>> files in source tarball, the number of total JIRAs is quite different.
>> Seems like CHANGES.txt misses some of the fixes, because Searching
>> <
>> https://issues.apache.org/jira/browse/YARN-4434?jql=project%20in%20(HDFS%2C%20HADOOP%2C%20MAPREDUCE%2C%20YARN)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%202.7.2
>> >
>> 'project
>> in (HDFS, HADOOP, MAPREDUCE, YARN) AND resolution = Fixed AND fixVersion =
>> 2.7.2' from JIRA agrees with releasenotes.html (count=155).
>>
>> Here is how I did the check:
>>
>>
>> -  cat ~/Downloads/releasenotes.html |grep "
>> https://issues.apache.org/jira/"; | awk -F ">" '{print $3}'|awk -F "<"
>> '{print $1}' |wc -l
>>
>>   returns 155
>>
>>
>> - for f in `find . -name CHANGES.txt |grep -v target`; do cat $f |grep
>>
>> -B 1 "Release 2.7.1" |grep .*-[0-9] |grep -v "Release 2.7" ;
>> done|wc -l
>>
>>  returns 103
>>
>> I'm not sure whether this is a problem or not.
>> Best,
>> -Xiao
>>
>> On Thu, Jan 14, 2016 at 8:57 PM, Vinod Kumar Vavilapalli <
>> vino...@apache.org
>>
>>> wrote:
>>>
>>
>> Hi all,
>>>
>>> I've created an updated release candidate RC2 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow up
>>> 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/
>>>
>>> The RC tag in git is: release-2.7.2-RC2
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1027
>>> <
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1027>
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>> hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/releasenotes.html <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html>
>>> for
>>> your quick perusal.
>>>
>>> As you may have noted,
>>>   - I terminated the RC1 related voting thread after finding out that we
>>> didn’t have a bunch of patches that are already in the released 2.6.3
>>> version. After a brief discussion, we decided to keep the parallel 2.6.x
>>> and 2.7.x releases incremental, see [4] for this discussion.
>>>   - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way. See
>>> the previous voting thread [3] for details.
>>>   - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>> quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc <
>>> http://markmail.org/message/5txhvr2qdiqglrwc>
>>> [4] Retracted [VOTE] Release Apache Hadoop 2.7.2 RC1:
>>> http://markmail.org/thread/n7ljbsnquihn3wlw
>>>
>>
>>
>

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-16 Thread Junping Du

In addition, all new fixes backport from 2.6.3 doesn't listed in 2.7.2 entry of 
CHANGES.txt but keep listed as 2.6.3. I think this is fine no matter we have 
multiple entries to track the same commit or a single entry to track the 
earliest commit. The only thing matter is the commits in release notes (coming 
from JIRA's Fix Versions) are matching with commits that actually land on the 
branch and each commit is tracked in some entry on CHANGES.txt. I did manually 
check that all 155 fixes are existing in commit log and we have entry in 
CHANGES.txt to track each commit on 2.7.2. 
Let's keep focusing on deployment test of 2.7.2. Thanks!

Thanks,

Junping

From: Akira AJISAKA 
Sent: Saturday, January 16, 2016 7:39 PM
To: common-...@hadoop.apache.org
Cc: hdfs-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

Hi Xiao,

 >  From a quick comparison between the releasenotes.html and the
CHANGES.txt
 > files in source tarball, the number of total JIRAs is quite different.

In CHANGES.txt, JIRAs fixed in 2.6.1/2.6.2 are not in 2.7.2.
That is why the number of JIRAs are different.

Regards,
Akira

On 1/16/16 09:11, Xiao Chen wrote:
> Thanks Vinod for preparing the release package.
>
>
> +1 (non-binding).
>
> I verified the following:
>
>
> - Successfully downloaded source tarball, verified md5
> - Ran `mvn apache-rat:check` on source tarball, passed
> - Successfully built from source tarball
> - Successfully started a pseudo distributed cluster
> - Ran some basic hdfs operations, then successfully ran a distcp
>
>
> 1 question:
>  From a quick comparison between the releasenotes.html and the CHANGES.txt
> files in source tarball, the number of total JIRAs is quite different.
> Seems like CHANGES.txt misses some of the fixes, because Searching
> 
> 'project
> in (HDFS, HADOOP, MAPREDUCE, YARN) AND resolution = Fixed AND fixVersion =
> 2.7.2' from JIRA agrees with releasenotes.html (count=155).
>
> Here is how I did the check:
>
>
> -  cat ~/Downloads/releasenotes.html |grep "
> https://issues.apache.org/jira/"; | awk -F ">" '{print $3}'|awk -F "<"
> '{print $1}' |wc -l
>
>   returns 155
>
>
> - for f in `find . -name CHANGES.txt |grep -v target`; do cat $f |grep
> -B 1 "Release 2.7.1" |grep .*-[0-9] |grep -v "Release 2.7" ; done|wc 
> -l
>
>  returns 103
>
> I'm not sure whether this is a problem or not.
> Best,
> -Xiao
>
> On Thu, Jan 14, 2016 at 8:57 PM, Vinod Kumar Vavilapalli > wrote:
>
>> Hi all,
>>
>> I've created an updated release candidate RC2 for Apache Hadoop 2.7.2.
>>
>> As discussed before, this is the next maintenance release to follow up
>> 2.7.1.
>>
>> The RC is available for validation at:
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/
>>
>> The RC tag in git is: release-2.7.2-RC2
>>
>> The maven artifacts are available via repository.apache.org <
>> http://repository.apache.org/> at
>> https://repository.apache.org/content/repositories/orgapachehadoop-1027 <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1027>
>>
>> The release-notes are inside the tar-balls at location
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> hosted this at
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/releasenotes.html <
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html> for
>> your quick perusal.
>>
>> As you may have noted,
>>   - I terminated the RC1 related voting thread after finding out that we
>> didn’t have a bunch of patches that are already in the released 2.6.3
>> version. After a brief discussion, we decided to keep the parallel 2.6.x
>> and 2.7.x releases incremental, see [4] for this discussion.
>>   - The RC0 related voting thread got halted due to some critical issues.
>> It took a while again for getting all those blockers out of the way. See
>> the previous voting thread [3] for details.
>>   - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> quite a bit. This release's related discussion threads are linked below:
>> [1] and [2].
>>
>> Please try the release and vote; the vote will run for the usual 5 days.
>>
>> Thanks,
>> Vinod
>>
>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> http://markmail.org/message/oozq3gvd4nhzsaes>
>> [2]: Planning Apache Hadoop 2.7.2
>> http://markmail.org/message/iktqss2qdeykgpqk <
>> http://markmail.org/message/iktqss2qdeykgpqk>
>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> http://markmail.org/message/5txhvr2qdiqglrwc <
>> http://markmail.org/message/5txhvr2qdiqglrwc>
>> [4] Retracted [VOTE] Release Apache Hadoop 2.7.2 RC1:
>> http://markmail.org/thread/n7ljbsnqui

[jira] [Created] (HDFS-9654) Code refactoring for HDFS-8578

[jira] [Created] (HDFS-9655) NN should start JVM pause monitor before loading fsimage

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #799

Hadoop-Hdfs-trunk-Java8 - Build # 799 - Still Failing

Jenkins build is back to normal : Hadoop-Hdfs-trunk #2736

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

8 matches

Site Navigation

Mail list logo

Footer information