Member since
11-14-2018
4
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2795 | 09-24-2021 06:32 AM |
09-24-2021
06:32 AM
As it turns out, it seems like it was a combination of things that caused this job to fail. First, we installed a minor java version update: went from jdk8u242-b08 to openjdk-8u292-b10. Second, the developer changed the way the files were being written from asynchronous to synchronous. They were using the CompletableFuture.runAsync class before, and took that out to use just normal writes.
... View more
09-15-2021
08:01 AM
Sorry... I've been working with cloudera support - no real answer yet. Anyway, it's a spark job, and we have proven it can work with 7.1.6 in 2 different clusters, so we have 2 that work and 2 that don't. All running CDP 7.1.6. Here's the perms for the /user/yarn directory on the cluster that doesn't work: varneyg@hdadmgw01mxm1:~$ hdfs dfs -ls -d /user/yarn drwxr-xr-x - yarn yarn 0 2021-08-25 14:08 /user/yarn varneyg@hdadmgw01mxm1:~$ hdfs dfs -ls /user/yarn Found 3 items drwx------ - yarn yarn 0 2021-09-15 10:12 /user/yarn/.staging drwxr-xr-x - yarn yarn 0 2021-09-13 10:32 /user/yarn/google-links drwxr-xr-x - hdfs yarn 0 2021-02-21 13:15 /user/yarn/mapreduce The job runs as a "googleops" user - same code running in both 7.1.4 and 7.1.6 I will attach the part of the job that does the writes, and job job logs.
... View more
08-27-2021
06:30 AM
We have a job that was running fine in 7.1.4, but is now failing after we went to 7.1.6. It fails with permission issues writing to a directory in /user/yarn. The job runs as a different user, and we are wondering why it started writing what looks like temporary output to a directory under /user/yarn, that the user running job doesn't have access to?
... View more
Labels: