You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a very rare condition which occurred once only.
mwax02 was processing a file (1332129440_20220324035702_ch110_000.fits). It had transferred it to mwacache01 with a temp filename (as it should). It was then about to issue an ssh 'mv' command on mwacache01, but before it could complete the remote mv command, the mwax_subfile_distributor was told to shutdown. This somehow caused the result of the mv to be counted as successful and so the file was deleted from the mwax host. For several months the partial file sat on mwacache01. Then at some point mwacache01 was restarted, causing it to see the partial file and, seeing it was so old, deleting it (this is expected behaviour).
So this issue is to ensure an interruption does not result in success and a delete, but instead a fail, and this should leave the file on the mwax02 server, and upon restart it will be archived again successfully. The old partial file will stay on mwacache01 until it is removed upon restart.
This is a very rare condition which occurred once only.
mwax02 was processing a file (1332129440_20220324035702_ch110_000.fits). It had transferred it to mwacache01 with a temp filename (as it should). It was then about to issue an ssh 'mv' command on mwacache01, but before it could complete the remote mv command, the mwax_subfile_distributor was told to shutdown. This somehow caused the result of the mv to be counted as successful and so the file was deleted from the mwax host. For several months the partial file sat on mwacache01. Then at some point mwacache01 was restarted, causing it to see the partial file and, seeing it was so old, deleting it (this is expected behaviour).
So this issue is to ensure an interruption does not result in success and a delete, but instead a fail, and this should leave the file on the mwax02 server, and upon restart it will be archived again successfully. The old partial file will stay on mwacache01 until it is removed upon restart.
Later... when mwacache_archiver gets restarted...
The text was updated successfully, but these errors were encountered: