Best practice during mass data updating
Posted: 28 Sep 2021, 02:43
If a client tries to access OPC UA Server when the server is in the progress of mass data updating, the retrieved data may not be reliable. In this case, what is the best practice to block the Client access temporarily?
One such example is that when the Address Space hierarchy is changing drastically due to some maintenance work, Client may run into inconsistent data. The time to complete the updating may range from a few seconds to 2 minutes. So it is better to block the access until the updating is completed.
However, simply setting server state to Suspended or other values than Running does not work. Client can still access the Server functions even if Server State is not Running. Could you give some advise?
Thank you!
One such example is that when the Address Space hierarchy is changing drastically due to some maintenance work, Client may run into inconsistent data. The time to complete the updating may range from a few seconds to 2 minutes. So it is better to block the access until the updating is completed.
However, simply setting server state to Suspended or other values than Running does not work. Client can still access the Server functions even if Server State is not Running. Could you give some advise?
Thank you!