New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 704823 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Mar 2017
Cc:
█ dshi@chromium.org
█ shuqianz@chromium.org
dgarr...@chromium.org
ihf@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

hosts moved during shard migration are all locked

Project Member Reported by akes...@chromium.org, Mar 24 2017 
Most or all of the DUTs that were moved during the migration are Locked, by user <null>.

This explains why jobs aint flowin'

dshi@ recommends we just mass unlock hosts locked by that user. Trouble now is figuring out precisely how to do that.

Comment 1 by akes...@chromium.org, Mar 24 2017 

On master:

mysql> UPDATE afe_hosts SET locked=False WHERE locked=True AND locked_by_id IS NULL;
Query OK, 1065 rows affected (0.06 sec)
Rows matched: 1065  Changed: 1065  Warnings: 0


Then the same on the new shards.
That seems to have gotten things moving again.

Comment 2 by ihf@chromium.org, Mar 24 2017 

The workload of the new servers seems to be still a bit on the light side. I never saw the locks, but from looking at the servers not too much changed since this was filed?

Comment 3 by aut...@google.com, Mar 28 2017 

What's the intended behavior here? What work remains?

Comment 4 by akes...@chromium.org, Mar 29 2017

Status: Fixed (was: Untriaged)

Comment 5 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 6 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 7 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)
►

Sign in to add a comment