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

Upgrade to netty 3.10.6.Final #19235

Merged
merged 2 commits into from
Jul 5, 2016
Merged

Upgrade to netty 3.10.6.Final #19235

merged 2 commits into from
Jul 5, 2016

Conversation

s1monw
Copy link
Contributor

@s1monw s1monw commented Jul 3, 2016

This upgrades to the latest netty release. @rjernst I ran gradle check on the distribution project and nothing failed even when I had not yet upgraded the sha1. Running gradle dependencyLicenses did it, maybe something is broken here?

@s1monw s1monw added review :Distributed/Network Http and internode communication implementations >upgrade v2.4.0 v5.0.0-alpha5 labels Jul 3, 2016
@jasontedor
Copy link
Member

LGTM.

@rjernst
Copy link
Member

rjernst commented Jul 3, 2016

@s1monw I made the same change and it failed for me as expected...

[11:22:48][~/Code/elasticsearch/distribution]$ git diff
diff --git a/core/build.gradle b/core/build.gradle
index 88c5cc2..2231880 100644
--- a/core/build.gradle
+++ b/core/build.gradle
@@ -75,7 +75,7 @@ dependencies {
   compile "com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:${versions.jackson}"

   // network stack
-  compile 'io.netty:netty:3.10.5.Final'
+  compile 'io.netty:netty:3.10.6.Final'
   // percentiles aggregation
   compile 'com.tdunning:t-digest:3.0'
   // precentil ranks aggregation
[11:22:29][~/Code/elasticsearch/distribution]$ gradle check
...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':distribution:dependencyLicenses'.
> Missing SHA for netty-3.10.6.Final.jar. Run 'gradle updateSHAs' to create

@s1monw s1monw merged commit a4ec0ac into elastic:master Jul 5, 2016
@s1monw s1monw deleted the upgrade_netty branch July 5, 2016 09:11
jasontedor added a commit that referenced this pull request Jul 6, 2016
* master: (192 commits)
  [TEST] Fix rare OBOE in AbstractBytesReferenceTestCase
  Reindex from remote
  Rename writeThrowable to writeException
  Start transport client round-robin randomly
  Reword Refresh API reference (#19270)
  Update fielddata.asciidoc
  Fix stored_fields message
  Add missing footer notes in mapper size docs
  Remote BucketStreams
  Add doc values support to the _size field in the mapper-size plugin
  Bump version to 5.0.0-alpha5.
  Update refresh.asciidoc
  Update shrink-index.asciidoc
  Change Debian repository for Vagrant debian-8 box
  [TEST] fix test to account for internal empyt reference optimization
  Upgrade to netty 3.10.6.Final (#19235)
  [TEST] fix histogram test when extended bounds overlaps data
  Remove redundant modifier
  Simplify TcpTransport interface by reducing send code to a single send method (#19223)
  Fix style violation in InstallPluginCommand.java
  ...
@salyh
Copy link
Contributor

salyh commented Jul 6, 2016

Netty 3 is EOL and 3.10.6.Final would be the last release. Looking into #3226 it does not look like an update to 4.0 or 4.1 is considered for ES 5?

@s1monw
Copy link
Contributor Author

s1monw commented Jul 8, 2016

Netty 3 is EOL and 3.10.6.Final would be the last release. Looking into #3226 it does not look like an update to 4.0 or 4.1 is considered for ES 5?

There is no issue yet but we are working on the future of networking. In a nutshell the plan is to modularize netty3 (build it as a plugin) and have a second module with netty4 such that we can do an experimental phase with the new networking. It's such a crucial part of the system that we want a safety net for the new version since a rather large portion of netty has changed fundamentally and we first need to learn how it affects ES. As a sideeffect this will allow us to do much better code isolation also in terms of security permissions etc. Yet, netty4 might not come with 5.0GA but I am confident it will come soon after.

There is work under way related to this like #19196 #19129 #19125 #19096 so we are actively working on this. I hope that helps... I will open a modularization issue soon too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Network Http and internode communication implementations >upgrade v2.4.0 v5.0.0-alpha5
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants