Bulk actions fail altogether (nothing happens) if too many machines are selected

Bug #1434736 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Raphaël Badin

Bug Description

When selecting 12 nodes to perform a bulk action in them, nothing really happens. The UI does not provide any feedback and the nodes don't seem to start commissioning.

However, when selecting only 5, this works just fine.

It seems that when many nodes are used for a bulk action, the bulk action might be failing altogether.

Related branches

Changed in maas:
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Andres Rodriguez (andreserl) wrote :

There's nothing at the logs that give us an idea of what might be going wrong!

tags: added: isolation-level
Revision history for this message
Raphaël Badin (rvb) wrote :

As discussed during the stand-up today, this is probably related to the fact that MAAS uses a thread pool (of 10) to deal with async calls.

Revision history for this message
Raphaël Badin (rvb) wrote :

When changing the number of threads, things definitely improve… but this doesn't explain what the core problem is: even with a limited number of threads things should just be slow but work: it seems that when more actions than the number of threads are started, things deadlock. When commissioning 11 nodes (with the default thread poll of 10 threads), things would deadlock and the last query in the DB's log is UPDATE "metadataserver_nodeuserdata" SET "node_id" = 4, "data" = '<blah>'; after this things came to a halt

Raphaël Badin (rvb)
Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Confirmed → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.