Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

ceefour
Copy link

@ceefour ceefour commented Mar 15, 2016

ZooKeeper 3.4.6 uses netty 3.7.0.Final

@steveloughran
Copy link
Contributor

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

@ceefour ceefour changed the title Update netty to 3.7.1.Final and netty-all to 4.0.34.Final Update netty-all to 4.0.34.Final Mar 16, 2016
@ceefour ceefour changed the title Update netty-all to 4.0.34.Final HADOOP-9991. Update netty-all to 4.0.34.Final Mar 16, 2016
@ceefour
Copy link
Author

ceefour commented Mar 16, 2016

@steveloughran This pull request now only updates netty-all (minor version update).

ceefour added a commit to ceefour/hadoop that referenced this pull request Mar 16, 2016
depends on zookeeper 3.4.6 which depends on netty 3.7.x. Related to
apache#84
@steveloughran
Copy link
Contributor

sorry, I should have been clearer
-create a new Hadoop JIRA for this, mark it as a dependency of HADOOP-9991. thanks

@ceefour
Copy link
Author

ceefour commented Mar 16, 2016

@steveloughran created HADOOP-12927

@ceefour ceefour changed the title HADOOP-9991. Update netty-all to 4.0.34.Final HADOOP-12927. Update netty-all to 4.0.34.Final Mar 16, 2016
@elek
Copy link
Member

elek commented Jan 10, 2019

Can one of the admins verify this patch?

@aajisaka
Copy link
Member

Duplicated and fixed by HADOOP-13866. Closing.

@aajisaka aajisaka closed this Jan 23, 2019
shanthoosh pushed a commit to shanthoosh/hadoop that referenced this pull request Oct 15, 2019
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 <mlogvinenko@gmail.com>

Reviewers: Jagadish <jagadish@apache.org>

Closes apache#84 from logarithm/yarn-properties-fix
saxenapranav added a commit to saxenapranav/hadoop that referenced this pull request Jul 25, 2023
…r_improvements

Stop producer thread when consumer fails due to irrecoverable exception.
NyteKnight pushed a commit to NyteKnight/hadoop that referenced this pull request Jun 25, 2024
… use credentials of logged in user (apache#84)

Co-authored-by: Hector Sandoval Chaverri <hchaverr@linkedin.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants