Hi Team, after completing the sql code and executing the cell for exercise 1, it is taking too long to complete and there is error message.
Please kindly check, as I still facing this issue after attempting this lab for 3 times.
Hello @arrancarr,
Could you show a screenshot of your error in the exercise 1. You could try getting a new notebook if you follow these instructions or try a different browser. Thank you
I am experiencing similar issues for the C3W3 Assignment on Advanced SQL Queries. Iâve tried it in multiple versions on three different browsers - it seems effectively unusable
Hello @cormacbr,
I am sorry your notebook doesnât load, not sure what error you are getting but could you provide more details. If you need to update your notebook try these instructions. Since it persists in different browsers could you check the following, thanks:
- Making sure your ad-blocking software is turned off on your browser or network
- Clearing your cache and cookies
- Using a different browser or new browser window
Thanks @Georgios - no problems with connecting today!
1 Like
Hello @arrancarr,
Sorry I misunderstood the practice lab you have the issue. I think there is a typo in Exercise 1 as well with orders table JOIN. Apart from that you should get 15 rows in the output (if you exclude %%timeit -n1 -r1 in the cell). Could you share a screenshot of the error if that happen in other cells also. Thanks in advance
Hi @Georgios, thanks for checking in. I have managed to complete the exercise.
1 Like
I have almost reached the 2 hour limit and exercise 1 cell still has not returned a result. In the meantime I filled in exercise 2 and 3 also in cloud9 I tried to download the solution book but it seems that the cloud9 environment is also slow to even download, which make sense since the juniper notebook waiting for a return result. Also of note this is my first try on this lab. I was almost 15 minutes in before the lab was ready to start.
Hello @bclark,
I am not sure how all those three connect. Running a sql query to find its running time which takes less than 1 second to give 15 rows output. Then the cloud9 is slow to download the solution file and finally the Vocareum that shouldnât load in 15 minutes.
It took me less than 13 minutes to start the lab (since it isnât the first time to run the lab). I could try to reproduce the issues but could you try check one more time to see any files didnât set up correctly the first time. Thanks
I just restarted the lab. I noticed that there were 3 VPCs in the list 2 had at quick glance had the same name. One of the 2 only had a private subnet, so I switched to the second and pick a public subnet.
When I tired to open the juniper notebook link I got site can not be reached.
Hello @bclark,
Yes sometimes there could be more than one VPC in the dropdown. Its not good but I think its good sign in this case since it narrows down things.
Long story short you can always fill up this form which takes about 3 working days to refresh the lab. You could always check the lab and preferably use a different browser. Hope it helps
Hi all,
I am having similar issues with this lab - after executing the initial query on Redshift, the Cloud9 environment and the notebook become unresponsive. At first I thought I might have messed up the query in some way but even simple ones donât work after deleting and recreating the Cloud9 console.
Here is a screenshot of the error:
Any help would be appreciated.
Thank you,
Matt
Hi Matt,
I couldnât reproduce your issue with AWS environment. I created and deleted my environment and run the notebook queries without issues. The query in Exercise 1 had the correct runtime, 1 second and output 15 rows.
This lab uses two different databases to compare how long it takes for the queries, and uses two different endpoints might be an issue.
As you can see other people had similar errors and there is this form to refresh the lab. Thank you
1 Like
Thank you for your help, appreciate it!
1 Like
I was able to get through exercises involving redshift however when trying to connect to the rdbs for section 3 I got a juniper can not connect issue. I noticed in cloud formation that the connection string has this:
jdbc:mysql://de-c3w3lab1-rds.cpiuqeamk7e3.us-east-1.rds.amazonaws.com:5432
Hello @bclark,
Yes I had some issues with the jupyter notebook also and tried to refresh it. Could you check if you are disconnected in Cloud 9 then rerun
source scripts/setup_jupyter_env.sh to get a new url and continue your notebook. Thanks
I got the connection now, however I had to use the initial jupter string, but switched browsers. I was able to complete the lab.
1 Like
Hi @Georgios, now itâs my turn to have this issue⌠I tried to reboot my lab several times and used two different browsers, getting the same error roughly 2 minutes after this query started to run:
- redshift+psycopg2://defaultuser:***@redshiftcluster-âŚ-east-1.redshift.amazonaws.com:5439/dev
Canceled future for execute_request message before replies were done
The Kernel crashed while executing code in the the current cell or a previous cell. Please review the code in the cell(s) to identify a possible cause of the failure. Click here for more info. View Jupyter log for further details.
What can I do? Fill the reset form?
Hello @nmsleal, I guess you are in the first sql query. That shouldnât take more than a few seconds since the lab compares row to columnar storage. Perhaps a new lab session could fix the issue, since the post is outdated from the old lab version use this link form. Thank you
Hi @Georgios , yes, youâre right. I filled the form, as Iâm really stuck. I tried all sorts of workarounds, but without any success⌠Today, after a few reboots and the last kernel crash, I restarted it and re-run all code to the one failing, then I created a new code cell and executed the plain query using the %%sql magic feature: It crashed after 2mâŚ
The output log is this (from the kernel restart):
info 12:37:01.382: Restart requested file:///home/coder/project/C3_W3_Lab_1_Row_vs_Column_Storage.ipynb
info 12:37:01.383: Restart kernel execution
info 12:37:01.384: Restarting undefined
info 12:37:01.394: Launching Raw Kernel & not daemon Python (base) # /home/coder/miniconda/bin/python
info 12:37:01.395: No custom variables nor do we have a conda environment
info 12:37:01.409: Process Execution: > ~/miniconda/bin/python -Xfrozen_modules=off -m ipykernel_launcher --ip=127.0.0.1 --stdin=9004 --control=9002 --hb=9000 --Session.signature_scheme=âhmac-sha256â --Session.key=b"aacf3bb8-a9f4-4789-bc1a-d4a89f2608c6" --shell=9003 --transport=âtcpâ --iopub=9005 --f=/home/coder/.local/share/jupyter/runtime/kernel-v2-96391Dd4Ifd9Y8z.json
~/miniconda/bin/python -Xfrozen_modules=off -m ipykernel_launcher --ip=127.0.0.1 --stdin=9004 --control=9002 --hb=9000 --Session.signature_scheme=âhmac-sha256â --Session.key=b"aacf3bb8-a9f4-4789-bc1a-d4a89f2608c6" --shell=9003 --transport=âtcpâ --iopub=9005 --f=/home/coder/.local/share/jupyter/runtime/kernel-v2-96391Dd4Ifd9Y8z.json
info 12:37:01.409: Process Execution: cwd: ~/project
cwd: ~/project
info 12:37:02.680: Kernel Output: To connect another client to this kernel, use: --existing kernel-v2-96391Dd4Ifd9Y8z.json
info 12:37:03.080: Got new session dd008ebd-39ca-4823-85a8-5aa20d14be86
info 12:37:03.080: Started new restart session
info 12:37:03.084: UpdateWorkingDirectoryAndPath in Kernel
error 12:41:50.074: Disposing session as kernel process died ExitCode: undefined, Reason:
info 12:41:50.081: Dispose Kernel process 2174.
error 12:41:50.084: Raw kernel process exited code: undefined
error 12:41:50.171: Error in waiting for cell to complete [Error: Canceled future for execute_request message before replies were done
at t.KernelShellFutureHandler.dispose (/home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:17:427328)
at /home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:17:446380
at Map.forEach ()
at y._clearKernelState (/home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:17:446365)
at y.dispose (/home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:17:439847)
at /home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:2:593313
at t.swallowExceptions (/home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:7:167240)
at p.dispose (/home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:2:593291)
at t.RawSession.dispose (/home/coder/.local/share/code-server/extensions/ms-toolsai.jupyter-2022.10.110-universal/out/extension.node.js:2:598289)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)]
warn 12:41:50.183: Cell completed with errors {
message: âCanceled future for execute_request message before replies were doneâ
}
info 12:41:50.192: Cancel all remaining cells true || Error || undefined