Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/2787
I've actually found out the reason for
`HttpConnectionParams.setSoKeepalive` error, noted in the last comment in JIRA.
Cross-posting it here so we don't need to jump around two places:
It seems like that the `flink-dist` jar that comes natively with EMR 5.1.0
hasn't shaded `httpclient` / `httpcore` properly (it contains the wrong
unshaded classes). On other EMR versions where we need to download the Flink
binaries ourselves, the class `HttpConnectionParams` was correctly loaded from
user jars (this is the expected behaviour because our distributed Flink
binaries has the classes shaded in the Hadoop dependency; see [1]). However, on
EMR 5.1.0, it was loading the wrong unshaded class from their own shipped
`flink-dist` jar.
Is it possible that AWS have built Flink themselves for EMR 5.1.0, and used
Maven 3.3.x which lead to incorrect shading of the apache http classes?
[1]
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Kinesis-connector-classpath-issue-when-running-Flink-1-1-SNAPSHOT-on-YARN-td7611.html
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
