Re: [Continued] [Release thread] 2.8.0 release activities

[Junping Du]

Hi all Hadoopers,
 I just commit YARN-3866 which is the last blocker for branch-2.8, so since 
tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. 
This release will include at least 2374 commits that never landed before in 
previous 2.x releases. Please check https://s.apache.org/RW5k for details. 
There are also 352 fixes marked in 2.7.1, 2.7.2 and 2.7.3 but not marked with 
2.8 (https://s.apache.org/RKti) that I need to double check all are landed in 
branch-2.8 and fix the versions before kicking off the first RC.
 Our progress is slightly behind my estimation weeks ago. However, 
considering we just go through holidays and Jenkins cleanup issues linger on 
for several projects (YARN, etc.), our achievement here is still great! Thanks 
everyone for keep calm and carry on the help for the release. Kudos to Wangda, 
Jian, Akira, Jason, Sangjin, Karthik and all for pushing hard on blockers 
during this time. Also, special thanks to Vinod and Andrew for sharing 
knowledge and practice (include scripts for auto version check) for releasing 
effort.
 Will try to prepare RC0 of 2.8 release for vote within this week. Stay 
tuned!

Thanks,

Junping


From: Junping Du 
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for 
several runs before last weekend, but it get failed for latest several runs, 
probably affected by recently Jenkins down.
However, from my recent manual kick off, it seems to be good again: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/9/. I will 
keep an eye for today's nightly run to see if it back to normal.


Thanks,

Junping


From: Akira Ajisaka 
Sent: Wednesday, December 07, 2016 12:12 AM
To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to
compare 2.8 with 2.7.3.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html

Regards,
Akira

On 2016/12/02 2:08, Junping Du wrote:
> Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 
> and kick off several runs manually. Will monitor incompatible status from 
> there.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Andrew Wang 
> Sent: Wednesday, November 30, 2016 4:18 PM
> To: Junping Du
> Cc: Sangjin Lee; common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> I recommend giving the JACC report another look. I set up a parameterized 
> jenkins job which you can trigger manually for branch-2.8:
>
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/
>
> On Wed, Nov 30, 2016 at 4:06 PM, Junping Du 
> mailto:j...@hortonworks.com>> wrote:
> Hi Sangjin and all,
>
>  That sounds good. If anyone have priority fix to backport , please 
> nominate it by following this email thread or ping me on JIRA directly. And I 
> agree that we should keep in mind that our bar for 2.8 release should be high 
> now as we want to move quickly on this release. Non-critical fixes can wait 
> for next one.
>
>   Any other comments and suggestions?
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: sjl...@gmail.com 
> mailto:sjl...@gmail.com>> on behalf of Sangjin Lee 
> mailto:sj...@apache.org>>
> Sent: Wednesday, November 30, 2016 3:24 PM
> To: Junping Du
> Cc: common-dev@hadoop.apache.org; 
> hdfs-...@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; 
> yarn-...@hadoop.apache.org; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Thanks for picking this up Junping!
>
> I heard on email threads and offline discussions that there may be interests 
> in porting some fixes from branch-2 to branch-2.8. I still feel that the bar 
> should be pretty high to do that, but it might be good to have folks suggest 
> some critical fixes that need to be released sooner. Thoughts?
>
> On Tue, Nov 29, 2016 at 8:50 PM, Junping Du 
> mai

[jira] [Created] (HADOOP-13949) Hadoop could provide IP instead of hostname to represent the node, which can reduce the DNS hostname resolution consumption

[DENG FEI (JIRA)]

DENG FEI created HADOOP-13949:
-

 Summary: Hadoop could provide IP instead of hostname to represent 
the node, which can reduce the DNS hostname resolution consumption
 Key: HADOOP-13949
 URL: https://issues.apache.org/jira/browse/HADOOP-13949
 Project: Hadoop Common
  Issue Type: Improvement
  Components: common
Reporter: DENG FEI


Normally,Hadoop use hostname represent the node,such as 
datanode,nodemanager,will lookup nameserver at rack resolve or connnect rpc.
May be could provide a chance use ip walk around dns resolution.




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

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

[jira] [Resolved] (HADOOP-13949) Hadoop could provide IP instead of hostname to represent the node, which can reduce the DNS hostname resolution consumption

[Steve Loughran (JIRA)]

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

Steve Loughran resolved HADOOP-13949.
-
Resolution: Won't Fix

Closing as a WONTFIX, as this has been discussed in the past, and rejected then.

Why? Kerberos

Kerberos likes hostnames, not IP addresses, and likes to do reverse DNS too.

If you want security, you need Kerberos, so you need hostnames. And if you 
aren't running Kerberos, your Hadoop cluster and all data on it is available to 
everyone on the network. Which is generally considered a bad thing.

Generally, unless you run a DNS service, you can edit /etc/hosts for sharing 
the host tables. 

* If you are creating virtual clusters with short livespans, your config 
tooling (chef, puppet, ansible) can do this.
* if you have physical clusters, embrace DNS

We do recognise that sometimes it would seem useful to use IPAddrs, but its not 
something anyone should be doing in production. By not supporting it, we avoid 
people starting off with deployments which work during development/setup, but 
which can't go live.

Sorry

> Hadoop could provide IP instead of hostname to represent the node, which can 
> reduce the DNS hostname resolution consumption
> ---
>
> Key: HADOOP-13949
> URL: https://issues.apache.org/jira/browse/HADOOP-13949
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: common
>Reporter: DENG FEI
>
> Normally,Hadoop use hostname represent the node,such as 
> datanode,nodemanager,will lookup nameserver at rack resolve or create  rpc 
> connnect .
> May be could provide a chance use ip walk around dns resolution.



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

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

[jira] [Resolved] (HADOOP-13856) FileSystem.rename(final Path src, final Path dst, final Rename... options) to become public; specified, tested

[Steve Loughran (JIRA)]

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

Steve Loughran resolved HADOOP-13856.
-
Resolution: Duplicate

I've noticed that HADOOP-11452 duplicates this; moving work there

> FileSystem.rename(final Path src, final Path dst, final Rename... options) to 
> become public; specified, tested
> --
>
> Key: HADOOP-13856
> URL: https://issues.apache.org/jira/browse/HADOOP-13856
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: fs
>Affects Versions: 2.8.0
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>
> A lot of code within Hadoop (e.g. committers, filesystem) and downstream 
> (Hive, spark), don't know what to do when rename() returns false, as it can 
> be a sign of nothing important, or something major.
> In contrast, {{rename(final Path src, final Path dst, final Rename... 
> options)}} has stricter semantics and throws up all exceptions to be caught 
> or relayed by callers. Yet it cannot be used as its scoped at {{protected}} 
> and tagged as {{@Deprected}}. 
> If it was made public then it could be used in committers and elsewhere; if 
> we backport the making of it public, then life will be even better



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

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-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/276/

[Jan 3, 2017 1:49:29 PM] (brahma) Revert "HDFS-11280. Allow WebHDFS to reuse 
HTTP connections to NN.
[Jan 3, 2017 5:58:00 PM] (wang) HDFS-11156. Add new op GETFILEBLOCKLOCATIONS to 
WebHDFS REST API.
[Jan 3, 2017 8:13:32 PM] (rkanter) YARN-5529. Create new DiskValidator class 
with metrics (yufeigu via
[Jan 3, 2017 9:08:38 PM] (liuml07) HADOOP-13946. Document how HDFS updates 
timestamps in the FS spec;
[Jan 3, 2017 9:16:06 PM] (cnauroth) HADOOP-13922. Some modules have 
dependencies on hadoop-client jar
[Jan 3, 2017 10:44:26 PM] (liuml07) Revert "HADOOP-13946. Document how HDFS 
updates timestamps in the FS
[Jan 3, 2017 10:46:41 PM] (wangda) Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate and its
[Jan 3, 2017 10:53:13 PM] (wangda) Revert "Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate
[Jan 3, 2017 10:53:36 PM] (wangda) YARN-6025. Fix synchronization issues of
[Jan 3, 2017 11:03:38 PM] (jdu) YARN-5923. Unable to access logs for a running 
application if
[Jan 4, 2017 2:25:46 AM] (xyao) HDFS-11279. Cleanup unused 
DataNode#checkDiskErrorAsync(). Contributed
[Jan 4, 2017 5:10:36 AM] (aajisaka) HADOOP-12733. Remove references to obsolete 
io.seqfile configuration
[Jan 4, 2017 6:39:29 AM] (rohithsharmaks) YARN-5988. RM unable to start in 
secure setup. Contributed by Ajith S.




-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.timeline.webapp.TestTimelineWebServices 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
  

   cc:

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

   javac:

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

   checkstyle:

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

   pylint:

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

   shellcheck:

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

   shelldocs:

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

   whitespace:

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

   javadoc:

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

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/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/276/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
  [56K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt
  [324K]

   asflicense:

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

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



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

Re: Planning for 3.0.0-alpha2

[Andrew Wang]

Hi folks,

Thanks to the hard work of many contributors, we've been steadily burning
down alpha2 blockers. There are only 4 remaining, three of which are PA and
likely to be committed shortly.

Once those three go in (hopefully this week), I'm going to cut the alpha2
branch and wait for that last blocker. Normal development activity can
continue on trunk and branch-2, and doesn't need to be committed to the
alpha2 branch.

Since we still have some significant code to wrap up (Tomcat->Jetty
conversion, EC work, rolling upgrade compatibility), it's likely there will
also be an alpha3 before we freeze for beta1. I've updated the Hadoop 3
wiki page [1] to reflect this.

Thanks,
Andrew

[1]: https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0.0+release

On Mon, Oct 17, 2016 at 1:57 PM, Andrew Wang 
wrote:

> Hi folks,
>
> It's been a month since 3.0.0-alpha1, and we've been incorporating fixes
> based on downstream feedback. Thus, it's getting to be time for
> 3.0.0-alpha2. I'm using this JIRA query to track open issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20in%
> 20(HADOOP%2C%20HDFS%2C%20MAPREDUCE%2C%20YARN)%20AND%
> 20%22Target%20Version%2Fs%22%20in%20(3.0.0-alpha2%2C%203.0.
> 0-beta1%2C%202.8.0)%20AND%20statusCategory%20not%20in%
> 20(Complete)%20ORDER%20BY%20priority
>
> If alpha2 goes well, we can declare feature freeze, cut branch-3, and move
> onto beta1. My plan for the 3.0.0 release timeline looks like this:
>
> * alpha2 in early November
> * beta1 in early Jan
> * GA in early March
>
> I'd appreciate everyone's help in resolving blocker and critical issues on
> the above JIRA search.
>
> Thanks,
> Andrew
>

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

[Apache Jenkins Server]

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

[Jan 3, 2017 1:49:29 PM] (brahma) Revert "HDFS-11280. Allow WebHDFS to reuse 
HTTP connections to NN.
[Jan 3, 2017 5:58:00 PM] (wang) HDFS-11156. Add new op GETFILEBLOCKLOCATIONS to 
WebHDFS REST API.
[Jan 3, 2017 8:13:32 PM] (rkanter) YARN-5529. Create new DiskValidator class 
with metrics (yufeigu via
[Jan 3, 2017 9:08:38 PM] (liuml07) HADOOP-13946. Document how HDFS updates 
timestamps in the FS spec;
[Jan 3, 2017 9:16:06 PM] (cnauroth) HADOOP-13922. Some modules have 
dependencies on hadoop-client jar
[Jan 3, 2017 10:44:26 PM] (liuml07) Revert "HADOOP-13946. Document how HDFS 
updates timestamps in the FS
[Jan 3, 2017 10:46:41 PM] (wangda) Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate and its
[Jan 3, 2017 10:53:13 PM] (wangda) Revert "Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate
[Jan 3, 2017 10:53:36 PM] (wangda) YARN-6025. Fix synchronization issues of
[Jan 3, 2017 11:03:38 PM] (jdu) YARN-5923. Unable to access logs for a running 
application if
[Jan 4, 2017 2:25:46 AM] (xyao) HDFS-11279. Cleanup unused 
DataNode#checkDiskErrorAsync(). Contributed
[Jan 4, 2017 5:10:36 AM] (aajisaka) HADOOP-12733. Remove references to obsolete 
io.seqfile configuration
[Jan 4, 2017 6:39:29 AM] (rohithsharmaks) YARN-5988. RM unable to start in 
secure setup. Contributed by Ajith S.




-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.fs.viewfs.TestViewFileSystemLocalFileSystem 
   hadoop.fs.viewfs.TestViewFileSystemWithAuthorityLocalFileSystem 
   hadoop.hdfs.TestEncryptionZones 
   hadoop.hdfs.TestReadStripedFileWithMissingBlocks 
   hadoop.hdfs.security.TestDelegationTokenForProxyUser 
   hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer 
   hadoop.hdfs.TestDFSRSDefault10x4StripedOutputStreamWithFailure 
   hadoop.hdfs.server.mover.TestStorageMover 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure080 
   hadoop.hdfs.web.TestWebHdfsTimeouts 
   hadoop.yarn.server.timeline.TestRollingLevelDB 
   hadoop.yarn.server.timeline.TestTimelineDataManager 
   hadoop.yarn.server.timeline.TestLeveldbTimelineStore 
   hadoop.yarn.server.timeline.webapp.TestTimelineWebServices 
   hadoop.yarn.server.timeline.recovery.TestLeveldbTimelineStateStore 
   hadoop.yarn.server.timeline.TestRollingLevelDBTimelineStore 
   
hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer 
   hadoop.yarn.server.resourcemanager.TestRMEmbeddedElector 
   hadoop.yarn.server.resourcemanager.recovery.TestLeveldbRMStateStore 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.client.TestApplicationMasterServiceProtocolOnHA 
   hadoop.yarn.server.timeline.TestLevelDBCacheTimelineStore 
   hadoop.yarn.server.timeline.TestOverrideTimelineStoreYarnClient 
   hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore 
   hadoop.yarn.applications.distributedshell.TestDistributedShell 
   hadoop.mapred.TestShuffleHandler 
   hadoop.mapreduce.v2.app.rm.TestRMCommunicator 
   hadoop.mapreduce.v2.app.TestMRAppComponentDependencies 
   hadoop.mapreduce.v2.app.launcher.TestContainerLauncher 
   hadoop.mapreduce.v2.hs.TestHistoryServerLeveldbStateStoreService 
   hadoop.mapreduce.v2.TestMRJobsWithProfiler 
   hadoop.hdfs.TestNNBench 
   hadoop.mapred.gridmix.TestResourceUsageEmulators 

Timed out junit tests :

   
org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting 
   org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache 
   org.apache.hadoop.mapreduce.v2.TestUberAM 
   org.apache.hadoop.mapreduce.v2.TestMRJobs 
  

   compile:

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

   cc:

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

   javac:

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

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt
  [132K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [1.3M]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-ser

[jira] [Resolved] (HADOOP-13839) Fix outdated tracing documentation

[Masatake Iwasaki (JIRA)]

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

Masatake Iwasaki resolved HADOOP-13839.
---
  Resolution: Fixed
   Fix Version/s: 2.7.4
Target Version/s: 2.7.4

I committed this to only branch-2.7.

branch-2.8 and above uses htrace-4 and the documentation has been already 
updated.

> Fix outdated tracing documentation
> --
>
> Key: HADOOP-13839
> URL: https://issues.apache.org/jira/browse/HADOOP-13839
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: documentation, tracing
>Affects Versions: 2.7.3
>Reporter: Masatake Iwasaki
>Assignee: Elek, Marton
>Priority: Minor
> Fix For: 2.7.4
>
> Attachments: HADOOP-13839-branch-2.7.001.patch
>
>
> Sample code in tracing doc is based on older version of SpanReceiverHost. The 
> doc in branch-2 and trunk seems to be good.



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

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