So, according to Eron's suggestion I tried *security.ssl.verify-hostname:
false *configuration and that does the trick. I no longer get the
classloader error even with *blob.service.ssl.enabled: true *configuration.
Do you think the hostname verification fails because we are running flink
jobmanage
I don't think this is a configuration problem, but a bug in Flink. But
we'll have to dig a little deeper to be sure.
Besides the actual SSL problem, what concerns me is that we didn't fail
earlier. If a bug in the SSL setup prevents
the up- or download of jars then we should fail earlier. Loopi
Hi Chesnay,
Thanks for the reply. After your suggestion, I found out that setting
*blob.service.ssl.enabled:
false* solved the issue and now all the pipelines run as expected.
So, the issue is kinda narrowed down to blob service ssl now.
I also checked the jobmanager logs when blob ssl is enabled a
By following Chesney's recommendation we will hopefully uncover an SSL
error that is being masked. Another thing to try is to disable hostname
verification (it is enabled by default) to see whether the certificate is
being rejected.
On Wed, Oct 4, 2017 at 5:15 AM, Chesnay Schepler wrote:
> some
something that would also help us narrow down the problematic area is to
enable SSL for one component at a time and see
which one causesd the job to fail.
On 04.10.2017 14:11, Chesnay Schepler wrote:
The configuration looks reasonable. Just to be sure, are the paths
accessible by all nodes?
A
The configuration looks reasonable. Just to be sure, are the paths
accessible by all nodes?
As a first step, could you set the logging level to DEBUG (by modifying
the 'conf/log4j.properties' file), resubmit the job (after a cluster
restart) and check the Job- and TaskManager logs for any exce
