Closed igorpisarev closed 4 years ago
This happens when the flatfield images are broadcasted to all Spark executors. Even though it works fine when the flatfield images are loaded from the filesystem, it breaks somewhere in Kryo internals when trying to serialize the images loaded from S3.
Some debugging showed that ImagePlus
has an inner field fileInfo
where it stores a reference to the underlying InputStream
. For S3 there is a lot more going on in the stream object hierarchy than for the filesystem, which causes errors in Kryo serialization.
A reasonable solution would be to create a copy of the flatfield images, so that there are no hidden object references stored internally.
The following error occurs when trying to run stitching and export steps when data is stored in AWS S3: