Hi, most of dbreps's jobs have been waiting for more than a month with:
| scheduling info: queue instance "medium...@mayapple.toolserver.org" dropped because it is temporarily not available | queue instance "longrun2-...@hawthorn.toolserver.org" dropped because it is disabled | queue instance "longrun2-...@clematis.toolserver.org" dropped because it is disabled | queue instance "longrun3-...@willow.toolserver.org" dropped because it is disabled | queue instance "short-...@willow.toolserver.org" dropped because it is full | (-l arch=linux-x64,h_rt=12300,mem_free=2070M,sql-s1-rr=1,sqlprocs-s1=1,virtual_free=2070M) cannot run globally because it offers only gc:sql-s1-rr=0.000000 Does that mean that the resource sql-s1-rr is depleted? Are the database servers really that congested? I see that /sge/scripts/sensor/sqlslots2.pl was changed on October 17th. Could the calculation of the DB slots be wrong, or would changes in that file not affect the resource sql-s1-rr? Tim _______________________________________________ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette