During segmentation with antares segment errors appear in the workers like the following:
2019-02-26 16:18:26,393 - fiona._env - collection __init__: Unable to open /shared_volume/temp/segmentation_results/39cbab_sentinel_2_25_-33_2017.shp or /shared_volume/temp/segmentation_results/39cbab_sentinel_2_25_-33_2017.SHP.
2019-02-26 16:18:26,393 - fiona._env - collection __init__: Failed to open file /shared_volume/temp/segmentation_results/39cbab_sentinel_2_25_-33_2017.shp.It may be corrupt or read-only file accessed in update mode.
2019-02-26 16:18:27,838 - fiona._env - collection __init__: Unable to open /shared_volume/temp/segmentation_results/efe77b_sentinel_2_22_-30_2017.shp or /shared_volume/temp/segmentation_results/efe77b_sentinel_2_22_-30_2017.SHP.
2019-02-26 16:18:27,838 - fiona._env - collection __init__: Failed to open file /shared_volume/temp/segmentation_results/efe77b_sentinel_2_22_-30_2017.shp.It may be corrupt or read-only file accessed in update mode.
distributed.core - INFO - Event loop was unresponsive in Worker for 4.21s. This is often caused by long-running GIL-holding functions or moving large chunks of data. This can cause timeouts and instability.
We checked some of them and they are in the bucket and their paths are in the db.
During segmentation with
antares segment
errors appear in the workers like the following:We checked some of them and they are in the bucket and their paths are in the db.