-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-12927. Update netty-all to 4.0.34.Final #84
Conversation
Please can you file a separate JIRA for these two changes, link to HADOOP-9991 and include justification. Version updates are a traumatic issue in Hadoop and done fairly reluctantly. FWIW, updating netty-all from beta to final makes sense just from a release perspective; updating the other jetty less so |
@steveloughran This pull request now only updates netty-all (minor version update). |
depends on zookeeper 3.4.6 which depends on netty 3.7.x. Related to apache#84
sorry, I should have been clearer |
@steveloughran created HADOOP-12927 |
Can one of the admins verify this patch? |
Duplicated and fixed by HADOOP-13866. Closing. |
After migration from `yarn.container.*` properties to `cluster-manager.container.*` properties we have to use either of them and `ClusterManagerConfig` provides backward compatibility for these properties. But in `YarnClusterResourceManage`r only old properties are used (from `YarnConfig`), hence if job config migrated to new `cluster-manager.*` properties names then check will be evaluated against default values, not against actual values. Author: Maksim Logvinenko <[email protected]> Reviewers: Jagadish <[email protected]> Closes apache#84 from logarithm/yarn-properties-fix
…r_improvements Stop producer thread when consumer fails due to irrecoverable exception.
… use credentials of logged in user (apache#84) Co-authored-by: Hector Sandoval Chaverri <[email protected]>
ZooKeeper 3.4.6 uses netty 3.7.0.Final