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
A tool would be needed to check AppStorage data consistency, and to fix it in case of problems.
Such a problem is orphan nodes. In some circumstances, it may happen that some node has an invalid parent identifier (identifier of a node which has been deleted). At the moment, we don't have proper tools to detect and fix it.
That problem has happened in a real life situation where a service using the remote implementation of AFS has not been restarted while the database was cleaned up. That led to the service using an obsolete identifier for the root node (root id is kept on client side in the AppFileSystem class).
The text was updated successfully, but these errors were encountered:
Answering 2 years later :) : the database had been plainly deleted. For sure this particular situation will not happen in a managed production environment, but other situations may occur
A tool would be needed to check AppStorage data consistency, and to fix it in case of problems.
Such a problem is orphan nodes. In some circumstances, it may happen that some node has an invalid parent identifier (identifier of a node which has been deleted). At the moment, we don't have proper tools to detect and fix it.
That problem has happened in a real life situation where a service using the remote implementation of AFS has not been restarted while the database was cleaned up. That led to the service using an obsolete identifier for the root node (root id is kept on client side in the AppFileSystem class).
The text was updated successfully, but these errors were encountered: