[jira] [Created] (YARN-5534) Prevent arbitrary volume mounts

[luhuichun (JIRA)]

luhuichun created YARN-5534:
---

 Summary: Prevent arbitrary volume mounts 
 Key: YARN-5534
 URL: https://issues.apache.org/jira/browse/YARN-5534
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: luhuichun
Assignee: luhuichun


Mounting arbitrary volumes into a Docker container can be a security risk. One 
approach to provide safe volume mounts is to allow the cluster administrator to 
configure a set of parent directories in the yarn-site.xml from which volume 
mounts are allowed.  only these directories and sub-directories are allowed to 
mount.



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[VOTE] Release Apache Hadoop 2.7.3 RC2

[Vinod Kumar Vavilapalli]

Hi all,

I've created a new release candidate RC2 for Apache Hadoop 2.7.3.

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

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


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

The maven artifacts are available via repository.apache.org 
 at 
https://repository.apache.org/content/repositories/orgapachehadoop-1046 


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://home.apache.org/~vinodkv/hadoop-2.7.3-RC2/releasenotes.html 
 for your 
quick perusal.

As you may have noted,
 - few issues with RC0 forced a RC1 [1]
 - few more issues with RC1 forced a RC2 [2]
 - a very long fix-cycle for the License & Notice issues (HADOOP-12893) caused 
2.7.3 (along with every other Hadoop release) to slip by quite a bit. This 
release's related discussion thread is linked below: [3].

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

Thanks,
Vinod

[1] [VOTE] Release Apache Hadoop 2.7.3 RC0: 
https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/index.html#26106 

[2] [VOTE] Release Apache Hadoop 2.7.3 RC1: 
https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/msg26336.html 

[3] 2.7.3 release plan: 
https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/msg24439.html 

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

[Vinod Kumar Vavilapalli]

Canceling the release vote for this and other issues reported.

+Vinod

> On Aug 16, 2016, at 10:01 PM, Akira Ajisaka  
> wrote:
> 
> -1 (binding)
> 
> HADOOP-13434 and HADOOP-11814, committed between RC0 and RC1, are not 
> reflected in the release note.
> 
> -Akira
> 
> On 8/17/16 13:29, Allen Wittenauer wrote:
>> 
>> 
>> -1
>> 
>> HDFS-9395 is an incompatible change:
>> 
>> a) Why is not marked as such in the changes file?
>> b) Why is an incompatible change in a micro release, much less a minor?
>> c) Where is the release note for this change?
>> 
>> 
>>> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli  
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.3.
>>> 
>>> As discussed before, this is the next maintenance release to follow up 
>>> 2.7.2.
>>> 
>>> The RC is available for validation at: 
>>> http://home.apache.org/~vinodkv/hadoop-2.7.3-RC1/ 
>>> 
>>> 
>>> The RC tag in git is: release-2.7.3-RC1
>>> 
>>> The maven artifacts are available via repository.apache.org 
>>>  at 
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1045/ 
>>> 
>>> 
>>> The release-notes are inside the tar-balls at location 
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I 
>>> hosted this at home.apache.org/~vinodkv/hadoop-2.7.3-RC1/releasenotes.html 
>>>  for 
>>> your quick perusal.
>>> 
>>> As you may have noted,
>>> - few issues with RC0 forced a RC1 [1]
>>> - a very long fix-cycle for the License & Notice issues (HADOOP-12893) 
>>> caused 2.7.3 (along with every other Hadoop release) to slip by quite a 
>>> bit. This release's related discussion thread is linked below: [2].
>>> 
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>> 
>>> Thanks,
>>> Vinod
>>> 
>>> [1] [VOTE] Release Apache Hadoop 2.7.3 RC0: 
>>> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/index.html#26106 
>>> 
>>> [2]: 2.7.3 release plan: 
>>> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/msg24439.html 
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
>> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
> 
> 


-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

[Vinod Kumar Vavilapalli]

I always look at CHANGES.txt entries for incompatible-changes and this JIRA 
obviously wasn’t there.

Anyways, this shouldn’t be in any of branch-2.* as committers there clearly 
mentioned that this is an incompatible change.

I am reverting the patch from branch-2* .

Thanks
+Vinod

> On Aug 16, 2016, at 9:29 PM, Allen Wittenauer  
> wrote:
> 
> 
> 
> -1
> 
> HDFS-9395 is an incompatible change:
> 
> a) Why is not marked as such in the changes file?
> b) Why is an incompatible change in a micro release, much less a minor?
> c) Where is the release note for this change?
> 
> 
>> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli  
>> wrote:
>> 
>> Hi all,
>> 
>> I've created a release candidate RC1 for Apache Hadoop 2.7.3.
>> 
>> As discussed before, this is the next maintenance release to follow up 2.7.2.
>> 
>> The RC is available for validation at: 
>> http://home.apache.org/~vinodkv/hadoop-2.7.3-RC1/ 
>> 
>> 
>> The RC tag in git is: release-2.7.3-RC1
>> 
>> The maven artifacts are available via repository.apache.org 
>>  at 
>> https://repository.apache.org/content/repositories/orgapachehadoop-1045/ 
>> 
>> 
>> The release-notes are inside the tar-balls at location 
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I 
>> hosted this at home.apache.org/~vinodkv/hadoop-2.7.3-RC1/releasenotes.html 
>>  for 
>> your quick perusal.
>> 
>> As you may have noted,
>> - few issues with RC0 forced a RC1 [1]
>> - a very long fix-cycle for the License & Notice issues (HADOOP-12893) 
>> caused 2.7.3 (along with every other Hadoop release) to slip by quite a bit. 
>> This release's related discussion thread is linked below: [2].
>> 
>> Please try the release and vote; the vote will run for the usual 5 days.
>> 
>> Thanks,
>> Vinod
>> 
>> [1] [VOTE] Release Apache Hadoop 2.7.3 RC0: 
>> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/index.html#26106 
>> 
>> [2]: 2.7.3 release plan: 
>> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/msg24439.html 
>> 
> 
> 
> -
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
> 
> 


-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Created] (YARN-5533) Jmx AM Used metrics for queue wrong when app submited to parition

[Bibin A Chundatt (JIRA)]

Bibin A Chundatt created YARN-5533:
--

 Summary: Jmx AM Used metrics for queue wrong when app submited to 
parition
 Key: YARN-5533
 URL: https://issues.apache.org/jira/browse/YARN-5533
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bibin A Chundatt
Assignee: Bibin A Chundatt


# Configure cluster with node label 
# Configure default and root queue with label capacity 100
# Submit application to labelx and default queue
# Wait for application completion
# Check queue jmx metrics

{noformat}
 "name" : "Hadoop:service=ResourceManager,name=QueueMetrics,q0=root,q1=default",
"modelerType" : "QueueMetrics,q0=root,q1=default",
"tag.Queue" : "root.default",
"tag.Context" : "yarn",
"tag.Hostname" : "localhost",
"running_0" : 0,
"running_60" : 0,
"running_300" : 0,
"running_1440" : 0,
"AMResourceLimitMB" : 512,
"AMResourceLimitVCores" : 1,
"UsedAMResourceMB" : 3072,
"UsedAMResourceVCores" : 2,
{noformat}





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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Re: Short peaks in container memory usage

[Karthik Kambatla]

Jan,

As part of YARN-1011 (oversubscription work), we are looking at better
(faster) ways of monitoring and enforcement and considering putting all
YARN containers under a cgroup with hard limit so YARN as a whole does not
go over a limit, but let the individual containers run over. The details
are not clear yet, but hopefully that will help you.

On Tue, Aug 16, 2016 at 12:53 AM, Jan Lukavský  wrote:

> Hi Ravi,
>
> sorry for late answer. :) We are on hadoop 2.6-cdh5.7.
>
> Cheers,
>  Jan
>
> On 12.8.2016 01:57, Ravi Prakash wrote:
>
>> Hi Jan!
>>
>> Yes! Makes sense. I'm sure there were bigger changes for the
>> ResourceHandler. Which version are you on?
>>
>> Cheers
>> Ravi
>>
>> On Thu, Aug 11, 2016 at 7:48 AM, Jan Lukavský <
>> jan.lukav...@firma.seznam.cz >
>> wrote:
>>
>> Hi Ravi,
>>
>> I don't think cgroups will help us, because, we don't want to
>> impose a hard limit on the memory usage, we just want to allow for
>> short time periods, when container can consume more memory than
>> its limit. We don't want to put the limit too high, because that
>> causes underutilization of our cluster, but setting it
>> "reasonable" causes applications to fail (because of random
>> containers being killed because of spikes). That's why we created
>> the time-window averaging resource calculator, and I was trying to
>> find out, if anybody else is having similar kind of issues. If so,
>> I could contribute our extension (and therefore we will not have
>> to maintain it ourselves in a separate repository :)). The
>> resource calculator is for hadoop 2.6, and I suppose there might
>> be larger changes around this in higher versions?
>>
>> Cheers,
>>  Jan
>>
>> On 10.8.2016 19:23, Ravi Prakash wrote:
>>
>>> Hi Jan!
>>>
>>> Thanks for your explanation. I'm glad that works for you! :-)
>>> https://issues.apache.org/jira/browse/YARN-5202
>>>  is something
>>> that Yahoo! talked about at the Hadoop Summit, (and it seems the
>>> community may be going in a similar direction, although not
>>> exactly the same.) There's also
>>> https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-proj
>>> ect/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-
>>> nodemanager/src/main/java/org/apache/hadoop/yarn/server/
>>> nodemanager/containermanager/linux/resources/CGroupsHandler.java
>>> >> ject/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-
>>> nodemanager/src/main/java/org/apache/hadoop/yarn/server/
>>> nodemanager/containermanager/linux/resources/CGroupsHandler.java>
>>> . Ideally at my company we'd like memory limits also to be
>>> imposed by Cgroups because we have had the OOM-killer wreak havoc
>>> a couple of times, but from what I know, that is not an option yet.
>>>
>>> Cheers
>>> Ravi
>>>
>>> On Wed, Aug 10, 2016 at 1:54 AM, Jan Lukavský
>>> >> > wrote:
>>>
>>> Hi Ravi,
>>>
>>> we don't run into situation where memory used > RAM, because
>>> memory configured to be used by all containers on a node is
>>> less than the total amount on memory (by a factor of say
>>> 10%). The spikes of container memory usage, that are
>>> tolerated due to the averaging don't happen on all containers
>>> at once, but are more of a random nature and therefore mostly
>>> only single running container "spikes", which therefore
>>> doesn't cause any issues. To fully answer your question, we
>>> have overcommit enabled and therefore, if we would run out of
>>> memory, bad things would happen. :) We are aware of that. The
>>> risk of running into OOM-killer can be controlled by the
>>> averaging window length - as the length grows, the more and
>>> more spikes are tolerated. Setting the averaging window
>>> length to 1 switches this feature off, turning it back into
>>> the "standard" behavior, which is why I see it as a extension
>>> of the current approach, which could be interesting to other
>>> people as well.
>>>
>>>   Jan
>>>
>>>
>>> On 10.8.2016 02:48, Ravi Prakash wrote:
>>>
 Hi Jan!

 Thanks for your contribution. In your approach what happens
 when a few containers on a node are using "excessive" memory
 (so that total memory used > RAM available on the machine).
 Do you have overcommit enabled?

 Thanks
 Ravi

 On Tue, Aug 9, 2016 at 1:31 AM, Jan Lukavský
 >>> > wrote:

 Hello community,

 I have a question about container resource calculation
   

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

[Allen Wittenauer]

Touching the audit log is *extremely* dangerous from a compatibility 
perspective.  It is easily the most machine processed log in Hadoop (with the 
second likely being the fsck log).  In particular, this comment tells me that 
we are almost certainly going to break users:

"Some audit logs ( for non-ACE failures ) will go missing. So this 
change needs to be marked as Incompatible, for heads-up."

If that means what I think it means (the ordering of checks is going to 
make previously logged errors disappear in lieu of other, new messages showing 
up first), that is going to cause massive problems for users who are looking 
for a particular entry. Worse, while the JIRA was marked incompatible, there 
are absolutely zero hints to end users (changes file, release notes) that this 
could potentially break their universe without digging into the comments of 
said JIRA.  That's not a heads up, that's a landmine.

It's also arguable that this is actually a bug fix.  A lot of the 
assumptions made in that JIRA about the audit logs original intent are 
completely wrong. Better yet, a lot of the justification is around another 
unmarked, incompatible change that was introduced in the 2.x timeline.

Even if one disagrees and still views this as a bug fix:  it's still an 
incompatible change.  Users are justifiably angry when we don't warn them about 
breakages and this is a great example of that.  

> On Aug 17, 2016, at 6:15 AM, Junping Du  wrote:
> 
> From my quick understanding, HDFS-9395 is more like a bug fix and improvement 
> for audit logging instead of incompatible changes. We mark incompatible 
> probably because the audit log behavior could be corrected/updated in some 
> exception cases. I think it still belongs to 2.7.3 scope. 
> Kuhu and Kihwal, any comments here?
> 
> 
> Thanks,
> 
> Junping 
> 
> From: Allen Wittenauer 
> Sent: Wednesday, August 17, 2016 5:29 AM
> To: common-...@hadoop.apache.org
> Cc: hdfs-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1
> 
> -1
> 
> HDFS-9395 is an incompatible change:
> 
> a) Why is not marked as such in the changes file?
> b) Why is an incompatible change in a micro release, much less a minor?
> c) Where is the release note for this change?
> 
> 
>> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli  
>> wrote:
>> 
>> Hi all,
>> 
>> I've created a release candidate RC1 for Apache Hadoop 2.7.3.
>> 
>> As discussed before, this is the next maintenance release to follow up 2.7.2.
>> 
>> The RC is available for validation at: 
>> http://home.apache.org/~vinodkv/hadoop-2.7.3-RC1/ 
>> 
>> 
>> The RC tag in git is: release-2.7.3-RC1
>> 
>> The maven artifacts are available via repository.apache.org 
>>  at 
>> https://repository.apache.org/content/repositories/orgapachehadoop-1045/ 
>> 
>> 
>> The release-notes are inside the tar-balls at location 
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I 
>> hosted this at home.apache.org/~vinodkv/hadoop-2.7.3-RC1/releasenotes.html 
>>  for 
>> your quick perusal.
>> 
>> As you may have noted,
>> - few issues with RC0 forced a RC1 [1]
>> - a very long fix-cycle for the License & Notice issues (HADOOP-12893) 
>> caused 2.7.3 (along with every other Hadoop release) to slip by quite a bit. 
>> This release's related discussion thread is linked below: [2].
>> 
>> Please try the release and vote; the vote will run for the usual 5 days.
>> 
>> Thanks,
>> Vinod
>> 
>> [1] [VOTE] Release Apache Hadoop 2.7.3 RC0: 
>> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/index.html#26106 
>> 
>> [2]: 2.7.3 release plan: 
>> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/msg24439.html 
>> 
> 
> 
> -
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
> 


-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/

[Aug 16, 2016 8:35:41 AM] (varunsaxena) YARN-5514. Clarify 
DecommissionType.FORCEFUL comment (Vrushali C via
[Aug 16, 2016 2:54:53 PM] (varunsaxena) YARN-5475. Fix test failure of
[Aug 16, 2016 5:20:08 PM] (aengineer) HDFS-10560. DiskBalancer: Reuse 
ObjectMapper instance to improve the
[Aug 16, 2016 7:13:22 PM] (rchiang) MAPREDUCE-6751. Add debug log message when 
splitting is not possible due
[Aug 16, 2016 10:01:18 PM] (wang) HADOOP-13494. ReconfigurableBase can log 
sensitive information.
[Aug 16, 2016 11:25:37 PM] (liuml07) Revert "HADOOP-13470. 
GenericTestUtils$LogCapturer is flaky.
[Aug 17, 2016 12:05:52 AM] (cnauroth) HADOOP-13324. s3a tests don't 
authenticate with S3 frankfurt (or other
[Aug 17, 2016 12:33:04 AM] (liuml07) HADOOP-13470. GenericTestUtils$LogCapturer 
is flaky. (Contributed by




-1 overall


The following subsystems voted -1:
asflicense unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

Failed junit tests :

   hadoop.contrib.bkjournal.TestBootstrapStandbyWithBKJM 
   hadoop.hdfs.server.datanode.TestLargeBlockReport 
   hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.client.api.impl.TestYarnClient 
   hadoop.contrib.bkjournal.TestBootstrapStandbyWithBKJM 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-compile-javac-root.txt
  [172K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-checkstyle-root.txt
  [16M]

   pylint:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-patch-pylint.txt
  [16K]

   shellcheck:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-patch-shellcheck.txt
  [20K]

   shelldocs:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-patch-shelldocs.txt
  [16K]

   whitespace:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/whitespace-eol.txt
  [12M]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/whitespace-tabs.txt
  [1.3M]

   javadoc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/diff-javadoc-javadoc-root.txt
  [2.2M]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [144K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt
  [268K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-nativetask.txt
  [124K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs_src_contrib_bkjournal.txt
  [8.0K]

   asflicense:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/136/artifact/out/patch-asflicense-problems.txt
  [4.0K]

Powered by Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org



-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

[Junping Du]

>From my quick understanding, HDFS-9395 is more like a bug fix and improvement 
>for audit logging instead of incompatible changes. We mark incompatible 
>probably because the audit log behavior could be corrected/updated in some 
>exception cases. I think it still belongs to 2.7.3 scope. 
Kuhu and Kihwal, any comments here?


Thanks,

Junping 

From: Allen Wittenauer 
Sent: Wednesday, August 17, 2016 5:29 AM
To: common-...@hadoop.apache.org
Cc: hdfs-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

-1

HDFS-9395 is an incompatible change:

a) Why is not marked as such in the changes file?
b) Why is an incompatible change in a micro release, much less a minor?
c) Where is the release note for this change?


> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli  
> wrote:
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.3.
>
> As discussed before, this is the next maintenance release to follow up 2.7.2.
>
> The RC is available for validation at: 
> http://home.apache.org/~vinodkv/hadoop-2.7.3-RC1/ 
> 
>
> The RC tag in git is: release-2.7.3-RC1
>
> The maven artifacts are available via repository.apache.org 
>  at 
> https://repository.apache.org/content/repositories/orgapachehadoop-1045/ 
> 
>
> The release-notes are inside the tar-balls at location 
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted 
> this at home.apache.org/~vinodkv/hadoop-2.7.3-RC1/releasenotes.html 
>  for 
> your quick perusal.
>
> As you may have noted,
> - few issues with RC0 forced a RC1 [1]
> - a very long fix-cycle for the License & Notice issues (HADOOP-12893) caused 
> 2.7.3 (along with every other Hadoop release) to slip by quite a bit. This 
> release's related discussion thread is linked below: [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1] [VOTE] Release Apache Hadoop 2.7.3 RC0: 
> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/index.html#26106 
> 
> [2]: 2.7.3 release plan: 
> https://www.mail-archive.com/hdfs-dev%40hadoop.apache.org/msg24439.html 
> 


-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org


-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org