Hello,
Some pods got not to work well.
---------
disco-watson-discovery-data-prep-agent-c47cf49bf-8mqk8 0/1 Init:0/1 0 22h
disco-watson-discovery-dfs-induction-5fb744c787-gffsk 0/1 Init:0/5 0 1d
disco-watson-discovery-elastic-0 0/1 CrashLoopBackOff 24 20h
disco-watson-discovery-haywire-7cfcf5bc68-2lv4r 0/1 Init:0/1 0 22h
disco-watson-discovery-project-data-prep-agent-c4d4ffc6d-bt5tk 0/1 Init:0/1 0 22h
disco-watson-discovery-training-agents-7776695c7b-hhw8x 0/2 Init:0/1 0 22h
disco-watson-discovery-training-data-crud-74cb89cf6c-vgkdz 0/1 Init:0/3 0 1d
dv-0 2/3 Running 62 21h
dv-caching-5f4f4fdd6c-hlrlw 0/1 Init:0/1 2 21h
---------
As I checked the log of the container in disco-watson-discovery-elastic-0, I found the message below.
"Caused by: java.io.IOException: No space left on device"
I attached the results of df -Th on one of master/worker nodes.
I just concerned about the USE percentage of / on worker nodes (sometimes points 84% at maximum), and I wonder I should add another worker node. *df -i seems to be not problem.
And, in the first place, I do not know which space(/ or ohter one?) the message points.
I appreciate if someone help me out.
Thank you,
Chris
------------------------------
Chris
------------------------------
#CloudPakforDataGroup