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 similar to issue #223. We can check the list of available nodes and only try to fetch a replica if it is known to disco.
This has also caused the GC to faile with the following message.
GC: stopping, unable to get tag <<"test">>: {error,timeout}
This is similar to issue #223. We can check the list of available nodes and only try to fetch a replica if it is known to disco.
This has also caused the GC to faile with the following message.
GC: stopping, unable to get tag <<"test">>: {error,timeout}
Therefore, it is not just a UX issue.
ddfs blobs test
yields the following:
disco://dev02/ddfs/vol0/blob/e5/test-0$57f-ea20f-9fd7f disco://dev01/ddfs/vol0/blob/e5/test-0$57f-ea20f-9fd7f disco://devdisco01/ddfs/vol0/blob/e5/test-0$57f-ea20f-9fd7f
And in this case, we had 6 nodes but we reduced it to only three nodes which means only devdisco01 is in the cluster now.
The text was updated successfully, but these errors were encountered: