+1 ( non-binding)
-Built from the source
-Installed 3 Node HA cluster and a pseudo cluster
-Verified through hdfs shell commands
-Verified HDFS router federation
-Ran sample jobs like pi,Slive
--Brahma Reddy
On Tue, Nov 14, 2017 at 5:40 AM, Arun Suresh wrote:
> Hi
>> We did not allow a backport of ADLS to branch-2.7 when it was released in
>> 2.8.0. There were technical reasons-...
Ok, I'm clear now branch-2.7 is already in maintenance mode and allows none of
new features to be included.
>> Moreover, one should be able to use a jar compiled for 2.9 in
[
https://issues.apache.org/jira/browse/HADOOP-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SammiChen resolved HADOOP-15041.
Resolution: Fixed
> XInclude support in .xml configuration file is broken after
>
There was some discussion about backporting OSS module to branch 2.x and per
Chris's suggestion we should do it in the dev list.
-Original Message-
From: Chris Douglas [mailto:cdoug...@apache.org]
Sent: Thursday, November 16, 2017 1:20 AM
To: Zheng, Kai
Rajesh Balamohan created HADOOP-15042:
-
Summary: Azure::PageBlobInputStream::skip can return -ve value
when numberOfPagesRemaining is 0
Key: HADOOP-15042
URL:
+1 (non-binding)
Deployed in a cluster with 48 nodes and 8 subclusters:
- YARN federation
- HDFS Router-based federation
- Yarn UI 2
Executed a few Pi job using both HDFS and YARN federation.
Everything worked correctly.
The YARN UI 2 showed the jobs, etc.
On Wed, Nov 15, 2017 at 2:05
+1 (binding)
Verified source tarball. Checksum and signature match, built from
source, ran some unit tests. Skimmed NOTICE/LICENSE. -C
On Mon, Nov 13, 2017 at 4:10 PM, Arun Suresh wrote:
> Hi Folks,
>
> Apache Hadoop 2.9.0 is the first release of Hadoop 2.9 line and will be
> From recent classpath isolation work, I was surprised to find out that
many of our downstream projects (HBase, Tez, etc.) are still consuming many
non-public, server side APIs of Hadoop, not saying the projects/products
outside of hadoop ecosystem. Our API compatibility test does not (and
should
+1 (non-binding)
1. Built from source.
2. Deployed to pseudo node cluster
3. Ran sample jobs.
Regards,
Kuhu
On Wed, Nov 15, 2017 at 1:07 PM, Eric Badger
wrote:
> +1 (non-binding)
>
> - Verified all hashes and checksums
> - Built from source on macOS 10.12.6, Java
On 11/15/17 10:34 AM, Andrew Wang wrote:
Hi Junping,
On Wed, Nov 15, 2017 at 1:37 AM, Junping Du wrote:
3. Beside incompatibilities, there is also possible to have performance
regressions (lower throughput, higher latency, slower job running, bigger
memory footprint or
On 15 Nov 2017, at 09:37, Junping Du
> wrote:
2. From recent classpath isolation work, I was surprised to find out that many
of our downstream projects (HBase, Tez, etc.) are still consuming many
non-public, server side APIs of Hadoop, not
[
https://issues.apache.org/jira/browse/HADOOP-14723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-14723.
-
Resolution: Duplicate
> reinstate URI parameter in AWSCredentialProvider constructors
>
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.12.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Thanks,
Eric
On Wed, Nov 15, 2017 at 10:24 AM, Carlo Aldo Curino
wrote:
> +1 (binding)
>
> On Nov 15, 2017 8:23
Hi Junping,
On Wed, Nov 15, 2017 at 1:37 AM, Junping Du wrote:
> Thanks Vinod to bring up this discussion, which is just in time.
>
> I agree with most responses that option C is not a good choice as our
> community bandwidth is precious and we should focus on very limited
+1 (binding)
On Nov 15, 2017 8:23 AM, "Mukul Kumar Singh" wrote:
> +1 (non-binding)
>
> I built from source on Mac OS X 10.13.1 Java 1.8.0_111
>
> - Deployed on a single node cluster.
> - Deployed a ViewFS cluster with two hdfs mount points.
> - Performed basic sanity
+1 (non-binding)
I built from source on Mac OS X 10.13.1 Java 1.8.0_111
- Deployed on a single node cluster.
- Deployed a ViewFS cluster with two hdfs mount points.
- Performed basic sanity checks.
- Performed DFS operations(put, ls, mkdir, touch)
Thanks,
Mukul
> On 14-Nov-2017, at 5:40 AM,
+1.
Built from source.
- Deployed a 2-node non-secure cluster.
- Ran a few sample MR jobs with ATSv2 enabled. Also verified job submission
across RM and NM restarts.
- Tested ATSv2 with HBase as backend.Checked few of the REST endpoints.
- Verified new YARN UI and accessed a few pages.
SammiChen created HADOOP-15041:
--
Summary: XInclude support in .xml configuration file is broken
after "5eb7dbe9b31a45f57f2e1623aa1c9ce84a56c4d1" commit
Key: HADOOP-15041
URL:
Thanks Vinod to bring up this discussion, which is just in time.
I agree with most responses that option C is not a good choice as our community
bandwidth is precious and we should focus on very limited mainstream branches
to develop, test and deployment. Of course, we should still follow
+1 (binding)
Built from source.
- Tested few cases in an HA cluster and tried to do failover by using
rmadmin commands etc. This seems works fine including submitting apps.
- I also tested many MR apps and all are running fine w/o any issues.
- Majorly tested below feature sanity
+1(binding)
* Downloaded source and verified for checksum. Built from source and
deployed RM HA Non-Secure cluster along with Atsv2 and yarn-ui enabled!
* Tested for
** RM HA/Restart/Work-preserving restart and NM work preserving
restart scenarios
** Application priority and
21 matches
Mail list logo