Rohith created YARN-1934:
Summary: Potential NPE in ZKRMStateStore caused by handling
Disconnected event from ZK.
Key: YARN-1934
URL: https://issues.apache.org/jira/browse/YARN-1934
Project: Hadoop YARN
Jira: https://issues.apache.org/jira/browse/YARN-1922
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3562/
###
## LAST 60 LINES OF THE CONSOLE
###
Gang,
With hadoop-2.4 out, it's time to think ahead.
In the short-term hadoop-2.4.1 is in order; particularly with
https://issues.apache.org/jira/browse/MAPREDUCE-5830 (it's a break to @Private
API, unfortunately something Hive is using - sigh!). There are some other fixes
which testing
+1
The proposed content for 2.5 in the roadmap wiki looks good to me.
On Apr 12, 2014 7:26 AM, Arun C Murthy a...@hortonworks.com wrote:
Gang,
With hadoop-2.4 out, it's time to think ahead.
In the short-term hadoop-2.4.1 is in order; particularly with
+1 for starting to think about 2.5. Early June seems a little early to me
- we had talked about a quarterly release cadence and this would be about
half that.
I'm having trouble editing the wiki, but I think Timeline Server stability
(e.g. security and locking down APIs) should go on that list.
+1 for Timeline Server stability. In addition to the security, we may also
want to deal with scalability, generic and per-framework services
integration and MR integration.
Any plan about YARN long running services?
On Sat, Apr 12, 2014 at 10:09 AM, Sandy Ryza sandy.r...@cloudera.comwrote:
+1
