Hi,
Im trying to execute step 4.10 here:
4.10. Go back into the AWS Glue console and enter in the *ETL jobs* link.
Now you will see a job created with the name `de-c1w2-etl-job` that you have just created with IaC!
4.11. Start the AWS Glue job:
``` bash
aws glue start-job-run --job-name de-c1w2-etl-job | jq -r '.JobRunId'
You should get `JobRunID` in the output.
however i ran into a exit code 3 and my terminal crashed.
After opening a new terminal and going backk to the same command, I’m now receiving this message:
An error occurred (ConcurrentRunsExceededException) when calling the StartJobRun operation: Concurrent runs exceeded.
is there a way to cancel the previous run so i can retry the above?
Hello @kaineThng
Please, wait for the previous runs to either succeed or fail and make new runs afterwards. You can search for AWS Glue in the AWS console, go to ETL jobs, select the job you want to perform actions on. There you can see the previous runs and their statuses.
somehow i wasn’t able retry even after waiting for some time. might be because the Lab instances was terminated.
I rebooted the Lab and restarted the steps again successfully.
Thank you
Hi,
the same issue here. I did refresh my lab and still does not work for me. I tried this step 8 times and the glue jobs failed each with the following error:
An error occurred while calling o138.pyWriteDynamicFrame. Insufficient Lake Formation permission(s) on dim_customers (Service: AWSGlue; Status Code: 400; Error Code: AccessDeniedException; Request ID: xxxx; Proxy: xxx)
Hi KaineThang,
how did you rebot the Lab? I just restarted the LAB, however the resources provisioned by terraform are not deleted after the refresh step and then the etl job fails again …
I did it by rebooting via the “?” at the top right corner of the screen. did you do the same?
Your errorcode looks different from mine however, might want to start a new thread to get attention of the Experts
Thanks a lot for your quick reply! I could not find the “?” on vocareum lab UI. However, after 2 hours the lab will reboot automatically and this solved somehow the issue.
Best regards Mo