So when spinning it up on minikube, and then ssh into one of the JobManager
pods shows following for the commands you mentioned:
flink@local-thoros-jobmanager-6l9lz:~$ id
uid=(flink) gid=(flink) groups=(flink)
flink@local-thoros-jobmanager-6l9lz:~$ ls -la
$FLINK_HOME/plugins/s3-fs-pr
Can you check what is the output of those commands
$ id
$ ls -la $FLINK_HOME/plugins/s3-fs-presto/
jonas eyob schrieb am Mi. 25. Aug. 2021 um 16:17:
> The exception is showing up both in TM and JM
>
> This however seemed only to appear when running on my local kubernetes
> setup.
> > I'd also
The exception is showing up both in TM and JM
This however seemed only to appear when running on my local kubernetes
setup.
> I'd also recommend setting "kubernetes.namespace" option, unless you're
using "default" namespace.
Yes, good point - I now see why that was needed.
Den ons 25 aug. 2021
Hi Jonas,
Where does the exception pop-up? In job driver, TM, JM? You need to make
sure that the plugin folder is setup for all of them, because they all may
need to access s3 at some point.
Best,
D.
On Wed, Aug 25, 2021 at 11:54 AM jonas eyob wrote:
> Hey Thms,
>
> tried the s3p:// option as
Hey Thms,
tried the s3p:// option as well - same issue.
> Also check if your user that executes the process is able to read the
jars.
Not exactly sure how to do that? The user "flink" in the docker image is
able to read the contents as far I understand. But maybe that's not how I
would check it?
Hey Jonas,
you could also try to use the ´s3p://´ scheme to directly specify that
presto should be used. Also check if your user that executes the process is
able to read the jars.
Am Mi., 25. Aug. 2021 um 10:01 Uhr schrieb jonas eyob :
> Thanks David for the quick response!
>
> *face palm* - Tha
Thanks David for the quick response!
*face palm* - Thanks a lot, that seems to have addressed the
NullPointerException issue.
May I also suggest that this [1] page be updated, since it says the key is "
high-availability.cluster-id"
This led me to another issue however:
"org.apache.flink.core.fs.
Hi Jonas,
this exception is raised because "kubernetes.cluster-id" [1] is not set.
I'd also recommend setting "kubernetes.namespace" option, unless you're
using "default" namespace.
I've filled FLINK-23961 [2] so we provide more descriptive warning for this
issue next time ;)
[1]
https://ci.apac
Hey, I've been struggling with this problem now for some days - driving me
crazy.
I have a standalone kubernetes Flink (1.12.5) using an application cluster
mode approach.
*The problem*
I am getting a NullPointerException when specifying the FQN of the
Kubernetes HA Service Factory class
i.e.
*or
