You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page will also be used to communicate important information during dry-runs. To get notified of any changes to this page, please log in and click on  in the upper right.

What to expect during a dry-run

In preparation of the DHS move we will conduct a number of general dry-runs. During these system sessions read access to the main DHS in Reading will be closed and instead essential data necessary to continue all critical activities during the move will be provided by a temporary DHS in Bologna. 

Archive/Store operations will not be impacted and will continue as normal. Data archived during this period will be retrievable as normal.

At the start of the system session, all active retrieve requests (MARS) or get operations (ECFS) will fail. This is to switch MARS & ECFS to the dry-run configuration. After such failure, we encourage users to re-run scripts once, to experience the behaviour expected during the DHS Move:

  • Requests for essential/recent data should be satisfied from the temporary DHS.
  • Requests for historical data should fail with an explanatory message. We encourage users to re-run those requests after the system session is over.

Timetable of System Session on  

Time (UTC)ActionExpected impact
8:00Change configuration of all services using MARS/ECFS to use the temporary DHS in Bologna 
8:00 - 8:30Drain all MARS/ECFS activity in ReadingAll active/queued requests on the DHS in Reading will fail
8:30Dry-run mode
8:30 - 17:30Behaviour to expect during the DHS Move
18:00Revert to use DHS infrastructure in Reading

Short interruption

Re-run all failed requests/scripts

Example of execution


How to report a problem

If your activity is critical and we have missed to identify it as such, please, do get in touch with User Services and we will look at your specific requirements.

If your request does not behave as explained above, please, provide as much information as possible so analysts can investigate, for example:

  • Service/Tool you are using (mars client, metview, web api, verify, etc...)
  • Version of the tool you are using
  • Host (ecgb, ATOS, cca, your workstation, ...)

Temporary DHS 

MARS

During a dry-run, access will be limited to essential data. The available data is listed in the Catalogue of the temporary DHS

To monitor the status of your requests, please, visit the Temporary DHS server activity  

ECFS

Add Relevant user information/commands re temporary DHS for ECFS




  • No labels