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
When a container (Jubatus server) become Wait status, it reports its status to ApplicationMaster. In changeWait method of ApplicationMaster, if status of all (currently two) containers become Wait, status of AM become Wait and reports the status to Jubatus-on-Yarn client.
However, as changeWait may be called asynchronously (from two Containers), there is a race condition around L99-L102 that AM status change be notified twice to Jubatus-on-Yarn client. The second status notification will fail, because state cannot be changed from Wait to Wait. As a consequence, 1 of Jubatus server container will occasionally go down.
We should make changeWait synchronized.
The text was updated successfully, but these errors were encountered:
When a container (Jubatus server) become Wait status, it reports its status to ApplicationMaster. In
changeWait
method of ApplicationMaster, if status of all (currently two) containers become Wait, status of AM become Wait and reports the status to Jubatus-on-Yarn client.However, as
changeWait
may be called asynchronously (from two Containers), there is a race condition around L99-L102 that AM status change be notified twice to Jubatus-on-Yarn client. The second status notification will fail, because state cannot be changed from Wait to Wait. As a consequence, 1 of Jubatus server container will occasionally go down.We should make
changeWait
synchronized.The text was updated successfully, but these errors were encountered: