[
https://issues.apache.org/jira/browse/STORM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400888#comment-15400888
]
ASF GitHub Bot commented on STORM-1038:
---------------------------------------
Github user hsun-cnnxty commented on the issue:
https://github.com/apache/storm/pull/1591
Seems the Travis CI build will fail at random places which are not related
to this PR.
For example the last build failed due to
`[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.2.1:process (default)
on project flux-examples: Error resolving project artifact: Could not transfer
artifact io.confluent:kafka-schema-registry-client:pom:1.0 from/to
sonatype-apache (https://repository.apache.org/releases/): Connect to
repository.apache.org:443 [repository.apache.org/207.244.88.143] failed:
Connection timed out for project
io.confluent:kafka-schema-registry-client:jar:1.0 -> [Help 1]
`
Any way to manually trigger a new CI build w/o code change?
-thanks
> Upgrade netty transport from 3.x to 4.x
> ---------------------------------------
>
> Key: STORM-1038
> URL: https://issues.apache.org/jira/browse/STORM-1038
> Project: Apache Storm
> Issue Type: Dependency upgrade
> Components: storm-core
> Reporter: Hang Sun
> Priority: Minor
> Labels: performance
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> It will be nice to upgrade netty to 4.x to take advantage of its more
> efficient memory usage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
