-
Notifications
You must be signed in to change notification settings - Fork 587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConcurrentModificationException in ReadsPipelineSparkIntegrationTest #5680
Comments
We've seen this at least twice now. Seems like something we should investigate. |
Saw it again here (now restarted). If I'm reading the serialization stack in the right order:
it looks like we're trying to serialize a ClassLoader. The FieldSerializer does appear to use a ClassLoader to load classes during serialization. |
Seems like I'm getting this in almost 50% of my builds. Master is failing because of it---will restart. |
I haven't been able to reproduce this locally by running Another oddity: Also, we shouldn't be serializing Has anyone seen this running locally on their machine, or only on Travis? |
I think this is happening because were trying to serialize the class loader sun.misc.Launcher$AppClassLoader), which appears to be reached through the graph by way of via https://github.com/damiencarol/jsr203-hadoop/blob/master/src/main/java/hdfs/jsr203/HadoopFileSystem.java#L82. We probably need to short circuit that with a custom serializer for one of these: Serialization trace: See, for instance, dbpedia/distributed-extraction-framework#9. |
We've seen at least 1 non-deterministically occurring instance of ConcurrentModificationException while running the
ReadsPipelineSparkIntegrationTest.testReadsPipelineSpark[5]
It seems like there is a race condition somewhere.
@jamesemery @tomwhite I've seen this once, so it may be a super rare one that we're just hitting now, or something newly introduced. Not sure there's anything to do until we see it more often, but thought I'd record it in case it keeps coming back.
The text was updated successfully, but these errors were encountered: