Hi,
Do you have more information about the error? It is hard to tell what is going on.
When you say there is a broken package, you mean PyRDF? How do you know it is PyRDF? No new version should have been published on bleeding edge for PyRDF, no update has happened in the past few weeks.
Brian has Caused by: java.io.EOFException which is essentially meaning some stage in the middle exploded and did not return result, I get some crazy segmentation faults from ROOT
*** Break *** segmentation violation
Generating stack trace...
0x00007f45df11bcfc in <unknown> from /cvmfs/sft-nightlies.cern.ch/lcg/views/dev3/Mon/x86_64-centos7-gcc8-opt/lib/libCling.so
0x00007f45df11c3f6 in <unknown> from /cvmfs/sft-nightlies.cern.ch/lcg/views/dev3/Mon/x86_64-
....
/cvmfs/sft-nightlies.cern.ch/lcg/views/dev3/Mon/x86_64-centos7-gcc8-opt/lib/libpython2.7.so.1.0
0x00007f45fc3a1445 in __libc_start_main + 0xf5 from /lib64/libc.so.6
0x000000000040066e in <unknown> from python
I can give to some developer detailed logs of what happened if needed. We can maybe take this offline.
@vbrian did the quickfix with additional source unblock you? Probably the one from Thursday/Friday will also work Yes, as soon as we know the root-cause probably we will post here.
Hi Brian,
We are deploying a new container image for the k8s Spark clusters that should solve the issue. We’ll let you know when you can try again.
Cheers,
Enric
Thanks a lot, good news ! At least Piotr’s workaround is working fine (and I have no urgent time constraint right now…). By curiosity, have you spotted the issue ?
The new image (swan:v2) for spark executors with glibc-headers is deployed now. Please can you give it a try without the workaround and my recreating your spark session. Thank you