>
> * For YARN-6050, there's a bit here:
> https://developers.google.com/protocol-buffers/docs/proto that says
> "optional is compatible with repeated", so I think we should be OK there.
> - Optional is compatible with repeatable over the wire such that
> protobuf won't blow up, but does that
Looks like there's two that weren't updated:
>> [115] 16:32 : hadoop-common (trunk) :: grep "3.2.0-SNAPSHOT" . -r
--include=pom.xml
./hadoop-project/pom.xml:
3.2.0-SNAPSHOT
./pom.xml:3.2.0-SNAPSHOT
I've just pushed in an addendum commit to fix those.
In the future, please make sure to do a
+1 (binding)
- verified signatures and checksums
- setup pseudo cluster using Fair Scheduler from binary tarball
- ran some of the example jobs, clicked around the UI a bit
By the way, ASF recommends using a 4096 bit key for signing, though 2048 is
fine for now.
+1 (binding)
+ Downloaded the binary release
+ Deployed on a 3 node cluster on CentOS 7.3
+ Ran some MR jobs, clicked around the UI, etc
+ Ran some CLI commands (yarn logs, etc)
Good job everyone on Hadoop 3!
- Robert
On Tue, Dec 12, 2017 at 1:56 PM, Arun Suresh wrote:
>
Thanks Andrew!
- Deployed binary artifacts in a pseudo-distributed cluster (MacOS Sierra,
Java 1.8.0_91)
- Ran pi job
- Clicked around the web UIs
- Tried log aggregation
- Played a bit with HDFS
- Tried yarn top
+1 (binding)
- Robert
On Thu, Jul 6, 2017 at 4:21 PM, Hanisha Koneru
+1 (binding)
- Downloaded binary tarball
- verified signatures
- setup pseudo cluster
- ran some of the example jobs, clicked around the UI a bit
- Robert
On Mon, Jul 25, 2016 at 3:28 PM, Jason Lowe
wrote:
> +1 (binding)
> - Verified signatures and digests-
+1 (binding)
- Verified md5
- Deployed single node cluster from binary tarball
- Ran some sample jobs, a few of the CLI commands, and the web UIs
- Ran some Oozie jobs
- Robert
On Fri, Jan 22, 2016 at 5:53 PM, Rohith Sharma K S wrote:
> +1(non binding)
>
The only problem with trying to get the JDK 8 trunk builds green (or blue I
guess) is that it's like trying to hit a moving target because of how many
new commits keep coming in. I was looking at fixing these a while ago, and
managed to at least make them compile and fixed (or worked with others
[
https://issues.apache.org/jira/browse/HDFS-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter resolved HDFS-8514.
-
Resolution: Invalid
Nevermind. It was bash. If you put quotes around the {{*}} it works
Robert Kanter created HDFS-8514:
---
Summary: hadoop archive command looks at local files when using
wildcard
Key: HDFS-8514
URL: https://issues.apache.org/jira/browse/HDFS-8514
Project: Hadoop HDFS
You're absolutely right Steve. We should get the jobs under control.
At the very least, before we move to JDK 8 in Jenkins, we should get the
Java8 nightly builds working. I didn't realize we had these, and I had
thought all compiling and most test issues with JDK8 were already fixed
based on
+ yarn-dev, hdfs-dev, mapred-dev
On Tue, Apr 21, 2015 at 3:14 PM, Robert Kanter rkan...@cloudera.com wrote:
Hi all,
Moving forward on some of the discussions on Hadoop 3, I've created
HADOOP-11858 to set the minimum version of Hadoop 3 to JDK 8. I just
wanted to let everyone know in case
to do in any case since it'll still target 1.7.
I'll note that HADOOP-10530 details the pain Steve went through switching
us to JDK7. Might be some lessons learned about how to do this transition
more smoothly.
Thanks,
Andrew
On Tue, Apr 21, 2015 at 3:15 PM, Robert Kanter rkan
+1 (non-binding)
+ verified checksum
+ Deployed binary tarball, ran some examples, clicked around in the Web UIs
thanks
- Robert
On Tue, Apr 14, 2015 at 10:22 AM, Masatake Iwasaki
iwasak...@oss.nttdata.co.jp wrote:
+1 (non-binding)
+ verified signature and mds of source and binary tarball
+1 Happy to help too
On Mon, Mar 2, 2015 at 3:57 PM, Yongjun Zhang yzh...@cloudera.com wrote:
Thanks Andrew for the proposal.
+1, and I will be happy to help.
--Yongjun
On Mon, Mar 2, 2015 at 3:19 PM, Andrew Wang andrew.w...@cloudera.com
wrote:
Hi devs,
It's been a year and a
Hi Arun,
We were testing the RC and ran into a problem with the recent fixes that
were done for POODLE for Tomcat (HADOOP-11217 for KMS and HDFS-7274 for
HttpFS). Basically, in disabling SSLv3, we also disabled SSLv2Hello, which
is required for older clients (e.g. Java 6 with openssl 0.9.8x) so
Robert Kanter created HDFS-7391:
---
Summary: Renable SSLv2Hello in HttpFS
Key: HDFS-7391
URL: https://issues.apache.org/jira/browse/HDFS-7391
Project: Hadoop HDFS
Issue Type: Bug
Robert Kanter created HDFS-7274:
---
Summary: Disable SSLv3 (POODLEbleed vulnerability) in HttpFS
Key: HDFS-7274
URL: https://issues.apache.org/jira/browse/HDFS-7274
Project: Hadoop HDFS
Issue
Robert Kanter created HDFS-7275:
---
Summary: Add TLSv1.2 to HttpFS
Key: HDFS-7275
URL: https://issues.apache.org/jira/browse/HDFS-7275
Project: Hadoop HDFS
Issue Type: Bug
Components
Robert Kanter created HDFS-4969:
---
Summary: TestHttpFSFWithWebhdfsFileSystem has two test failures
Key: HDFS-4969
URL: https://issues.apache.org/jira/browse/HDFS-4969
Project: Hadoop HDFS
Issue
Robert Kanter created HDFS-4951:
---
Summary: FsShell commands using secure httpfs throw exceptions due
to missing TokenRenewer
Key: HDFS-4951
URL: https://issues.apache.org/jira/browse/HDFS-4951
Project
21 matches
Mail list logo