Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

2016-10-05 Thread Akira Ajisaka

Hi Sangjin,

When using binary tarball, I'm seeing
"2016-09-27T18:26Z by sjlee from branch-2.6.5" in Web UI.
Can we rename it?

AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to 
jenkins.


* 
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3CCAJs-t7NiJAJceO=6L8vr1uOr-Es=z1y-ufkqxr8ya5hq3-d...@mail.gmail.com%3E

* https://issues.apache.org/jira/browse/HADOOP-10313

Regards,
Akira

On 10/3/16 09:12, Sangjin Lee wrote:

Hi folks,

I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (the next maintenance release in the 2.6.x release line). RC1
contains fixes to CHANGES.txt, and is otherwise identical to RC0.

Below are the details of this release candidate:

The RC is available for validation at:
http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.

The RC tag in git is release-2.6.5-RC1 and its git commit is
e8c9fe0b4c252caf2ebf1464220599650f119997.

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

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.

Please try the release and vote. The vote will run for the usual 5 days. I
would greatly appreciate your timely vote. Thanks!

Regards,
Sangjin




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



[jira] [Created] (HDFS-10969) Fix typos in hdfs-default.xml

2016-10-05 Thread Yiqun Lin (JIRA)
Yiqun Lin created HDFS-10969:


 Summary: Fix typos in hdfs-default.xml
 Key: HDFS-10969
 URL: https://issues.apache.org/jira/browse/HDFS-10969
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: documentation
Reporter: Yiqun Lin
Assignee: Yiqun Lin
Priority: Minor


There are three typos in file {{hdfs-default.xml}}:

* In {{dfs.datanode.transferTo.allowed}}: tranfers->transfers
* In {{dfs.block.local-path-access.user}}: allowd->allowed
* In {{dfs.datanode.directoryscan.throttle.limit.ms.per.sec}}: disbled->disabled




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

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



Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

2016-10-05 Thread Brahma Reddy Battula
Thanks Sangjin!


+1 ( non- binding)


--Downloaded the source and complied

--Installed HA cluster

--Verified basic fsshell commands

--Ran pi,terasort Slive jobs, all works fine.



--Brahma Reddy Battula

On Mon, Oct 3, 2016 at 5:42 AM, Sangjin Lee  wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>



-- 



--Brahma Reddy Battula


[jira] [Created] (HDFS-10968) BlockManager#isNewRack should consider decommissioning nodes

2016-10-05 Thread Jing Zhao (JIRA)
Jing Zhao created HDFS-10968:


 Summary: BlockManager#isNewRack should consider decommissioning 
nodes
 Key: HDFS-10968
 URL: https://issues.apache.org/jira/browse/HDFS-10968
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: erasure-coding, namenode
Affects Versions: 3.0.0-alpha1
Reporter: Jing Zhao
Assignee: Jing Zhao


For an EC block, it is possible we have enough internal blocks but without 
enough racks. The current reconstruction code calls {{BlockManager#isNewRack}} 
to check if the target node can increase the total rack number for the case, 
which compares the target node's rack with source node racks:
{code}
for (DatanodeDescriptor src : srcs) {
  if (src.getNetworkLocation().equals(target.getNetworkLocation())) {
return false;
  }
}
{code}
However here the {{srcs}} may include a decommissioning node, in which case we 
should allow the target node to be in the same rack with it.

For e.g., suppose we have 11 nodes: h1 ~ h11, which are located in racks r1, 
r1, r2, r2, r3, r3, r4, r4, r5, r5, r6, respectively. In case that an EC block 
has 9 live internal blocks on (h1~h8 + h11), and one internal block on h9 which 
is to be decommissioned. The current code will not choose h10 for 
reconstruction because isNewRack thinks h10 is on the same rack with h9.



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

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



[jira] [Created] (HDFS-10967) Add configuration for BlockPlacementPolicy to deprioritize near-full DataNodes

2016-10-05 Thread Zhe Zhang (JIRA)
Zhe Zhang created HDFS-10967:


 Summary: Add configuration for BlockPlacementPolicy to 
deprioritize near-full DataNodes
 Key: HDFS-10967
 URL: https://issues.apache.org/jira/browse/HDFS-10967
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: namenode
Reporter: Zhe Zhang


Large production clusters are likely to have heterogeneous nodes in terms of 
storage capacity, memory, and CPU cores. It is not always possible to 
proportionally ingest data into DataNodes based on their remaining storage 
capacity. Therefore it's possible for a subset of DataNodes to be much closer 
to full capacity than the rest.

Notice that this heterogeneity is most likely rack-by-rack -- i.e. _m_ whole 
racks with low-storage nodes and _n_ whole racks with high-storage nodes. So 
It'd be very useful if we can deprioritize those near-full DataNodes as 
destinations for the 2nd and 3rd replicas.



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

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



[jira] [Created] (HDFS-10966) Enhance Dispatcher logic on deciding when to give up a source DataNode

2016-10-05 Thread Zhe Zhang (JIRA)
Zhe Zhang created HDFS-10966:


 Summary: Enhance Dispatcher logic on deciding when to give up a 
source DataNode
 Key: HDFS-10966
 URL: https://issues.apache.org/jira/browse/HDFS-10966
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: balancer & mover
Reporter: Zhe Zhang
Assignee: Mark Wagner


When a {{Dispatcher}} thread works on a source DataNode, in each iteration it 
tries to execute a {{PendingMove}}. If no block is moved after 5 iterations, 
this source (over-utlized) DataNode is given up for this Balancer iteration (20 
mins). This is problematic if the source DataNode was heavily loaded in the 
beginning of the iteration. It will quickly encounter 5 unsuccessful moves and 
be abandoned.

We should enhance this logic by e.g. using elapsed time instead of number of 
iterations.
{code}
// Check if the previous move was successful
} else {
  // source node cannot find a pending block to move, iteration +1
  noPendingMoveIteration++;
  // in case no blocks can be moved for source node's task,
  // jump out of while-loop after 5 iterations.
  if (noPendingMoveIteration >= MAX_NO_PENDING_MOVE_ITERATIONS) {
LOG.info("Failed to find a pending move "  + noPendingMoveIteration
+ " times.  Skipping " + this);
resetScheduledSize();
  }
}
{code}



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

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



[jira] [Created] (HDFS-10965) Add unit test for DFSAdmin#printTopology

2016-10-05 Thread Xiaobing Zhou (JIRA)
Xiaobing Zhou created HDFS-10965:


 Summary: Add unit test for DFSAdmin#printTopology
 Key: HDFS-10965
 URL: https://issues.apache.org/jira/browse/HDFS-10965
 Project: Hadoop HDFS
  Issue Type: Sub-task
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou


DFSAdmin#printTopology should also be tested. This proposes adding it in 
TestDFSAdmin.



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

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



[jira] [Resolved] (HDFS-10950) Add unit tests to verify ACLs in safemode

2016-10-05 Thread Xiaobing Zhou (JIRA)

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

Xiaobing Zhou resolved HDFS-10950.
--
Resolution: Invalid

Essentially, test_resetacl calls setAcl, getacl_recursive calls get 
getAclStatus recursively, and setfacl_default calls setAcl again. They can be 
all covered by setAcl and getAclStatus. There' no point to verify them. 
Resolved this as invalid.

> Add unit tests to verify ACLs in safemode
> -
>
> Key: HDFS-10950
> URL: https://issues.apache.org/jira/browse/HDFS-10950
> Project: Hadoop HDFS
>  Issue Type: Sub-task
>  Components: fs, test
>Reporter: Xiaobing Zhou
>Assignee: Xiaobing Zhou
>
> This proposes adding unit tests to validate that getting Acls works when 
> namende is in safemode, while setting Acls fails. Specifically, the following 
> needs being covered in newly added tests.
> test_getfacl_recursive
> test_resetacl
> test_setfacl_default



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

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



[jira] [Created] (HDFS-10964) Add more unit tests for ACLs

2016-10-05 Thread Namit Maheshwari (JIRA)
Namit Maheshwari created HDFS-10964:
---

 Summary: Add more unit tests for ACLs
 Key: HDFS-10964
 URL: https://issues.apache.org/jira/browse/HDFS-10964
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: test
Reporter: Namit Maheshwari
Assignee: Namit Maheshwari


This Jira proposes to add more unit tests to validate ACLs.



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

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



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

2016-10-05 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/

[Oct 4, 2016 1:03:22 PM] (brahma) HDFS-10944. Correct the javadoc of 
dfsadmin#disallowSnapshot.
[Oct 4, 2016 1:16:42 PM] (brahma) HDFS-10947. Correct the API name for truncate 
in webhdfs document.
[Oct 4, 2016 4:09:03 PM] (kihwal) HDFS-10878. 
TestDFSClientRetries#testIdempotentAllocateBlockAndClose
[Oct 4, 2016 5:36:58 PM] (cnauroth) HADOOP-13674. S3A can provide a more 
detailed error message when
[Oct 4, 2016 8:05:09 PM] (kihwal) HDFS-10956. Remove rename/delete performance 
penalty when not using
[Oct 5, 2016 12:23:13 AM] (jianhe) YARN-3139. Improve locks in
[Oct 5, 2016 10:01:38 AM] (vvasudev) YARN-5704. Provide config knobs to control 
enabling/disabling new/work
[Oct 5, 2016 11:41:08 AM] (aajisaka) HADOOP-13685. Document -safely option of 
rm command. Contributed by
[Oct 5, 2016 11:44:39 AM] (aajisaka) HADOOP-13681. Reduce Kafka dependencies in 
hadoop-kafka module.




-1 overall


The following subsystems voted -1:
compile unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc javac


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


Specific tests:

Failed junit tests :

   hadoop.hdfs.TestWriteReadStripedFile 
   hadoop.hdfs.TestWriteRead 
   hadoop.hdfs.server.namenode.TestDecommissioningStatus 
   hadoop.hdfs.server.datanode.TestDataNodeLifeline 
   hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer 
   hadoop.hdfs.web.TestWebHdfsTimeouts 
   hadoop.yarn.server.nodemanager.recovery.TestNMLeveldbStateStoreService 
   hadoop.yarn.server.nodemanager.TestNodeManagerShutdown 
   hadoop.yarn.server.timeline.TestRollingLevelDB 
   hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices 
   hadoop.yarn.server.timeline.TestTimelineDataManager 
   hadoop.yarn.server.timeline.TestLeveldbTimelineStore 
   hadoop.yarn.server.timeline.recovery.TestLeveldbTimelineStateStore 
   hadoop.yarn.server.timeline.TestRollingLevelDBTimelineStore 
   
hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer 
   hadoop.yarn.server.timelineservice.storage.common.TestRowKeys 
   hadoop.yarn.server.timelineservice.storage.common.TestKeyConverters 
   hadoop.yarn.server.timelineservice.storage.common.TestSeparator 
   hadoop.yarn.server.resourcemanager.recovery.TestLeveldbRMStateStore 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.resourcemanager.TestResourceTrackerService 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.client.api.impl.TestDistributedScheduling 
   hadoop.yarn.server.timeline.TestLevelDBCacheTimelineStore 
   hadoop.yarn.server.timeline.TestOverrideTimelineStoreYarnClient 
   hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore 
   hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorage 
   
hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRunCompaction
 
   hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun 
   
hadoop.yarn.server.timelineservice.storage.TestPhoenixOfflineAggregationWriterImpl
 
   
hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
 
   
hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity 
   hadoop.yarn.applications.distributedshell.TestDistributedShell 
   hadoop.mapred.TestShuffleHandler 
   hadoop.mapreduce.v2.app.webapp.TestAMWebApp 
   hadoop.mapreduce.v2.hs.TestHistoryServerLeveldbStateStoreService 

Timed out junit tests :

   org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache 
  

   compile:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-compile-root.txt
  [316K]

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-compile-root.txt
  [316K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-compile-root.txt
  [316K]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [200K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
  [52K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt
  [52K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/115/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-se

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

2016-10-05 Thread Chris Trezzo
+1 (non-binding)

Thanks for cutting another release candidate Sangjin!

1. Diff'ed the CHANGES-*.txt files against the branch-2.6.5 git log and
verified the set of listed issues matches.
2. Verified md5 checksums and signature on src and binary tar.gz.
3. Built from source.
4. Started up a pseudo distributed cluster.
5. Successfully ran a PI job.
6. Ran the balancer.
7. Inspected UI for RM, NN, JobHistory.

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee  wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


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

2016-10-05 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/185/

[Oct 4, 2016 1:03:22 PM] (brahma) HDFS-10944. Correct the javadoc of 
dfsadmin#disallowSnapshot.
[Oct 4, 2016 1:16:42 PM] (brahma) HDFS-10947. Correct the API name for truncate 
in webhdfs document.
[Oct 4, 2016 4:09:03 PM] (kihwal) HDFS-10878. 
TestDFSClientRetries#testIdempotentAllocateBlockAndClose
[Oct 4, 2016 5:36:58 PM] (cnauroth) HADOOP-13674. S3A can provide a more 
detailed error message when
[Oct 4, 2016 8:05:09 PM] (kihwal) HDFS-10956. Remove rename/delete performance 
penalty when not using
[Oct 5, 2016 12:23:13 AM] (jianhe) YARN-3139. Improve locks in




-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.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.mapreduce.v2.app.webapp.TestAMWebApp 
  

   cc:

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

   javac:

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

   checkstyle:

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

   pylint:

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

   shellcheck:

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

   shelldocs:

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

   whitespace:

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

   javadoc:

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

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/185/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/185/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/185/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-app.txt
  [28K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/185/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-nativetask.txt
  [124K]

   asflicense:

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

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



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

Re: Updation of Change.txt in branch-2.7

2016-10-05 Thread Brahma Reddy Battula

To track this, I raised HADOOP-13670..Thanks Akira Ajisaka for review.


2.7.4 having incompatible and new feature:

===


I found one incompatible (HDFS-7933) and one new feature(HDFS-9804) are there..


As per versioning rule, we should not include incompatible and new features.


http://hadoop.apache.org/versioning.html


I think, we should revert this..


2.7.3 release notes broken:

==


HADOOP-13434 issue is missed from 2.7.3 release notes.



Please let me know, your views on this..


Apache Hadoop Release Versioning
hadoop.apache.org
Apache Hadoop uses a version format of .., where each version component is a 
numeric value. Versions can also have additional suffixes like ...













Thanks And Regards
Brahma Reddy Battula



From: Brahma Reddy Battula 
Sent: Friday, September 30, 2016 12:58 PM
To: common-...@hadoop.apache.org
Subject: Updation of Change.txt in branch-2.7

Dear All,

Recently I had seen some commits are not having  CHANGE.txt updation in 
branch-2.7.

Most of the committers are aware of updation of  CHANGE.txt, but somehow 
missed. But we should take care.


As of now, going to raise jira to track this.



--Brahma Reddy Battula