Project

General

Profile

Bug #10812

Frontend could be queering all/more job schedds rather than global+group schedds

Added by Parag Mhashilkar over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Parag Mhashilkar
Category:
-
Target version:
Start date:
11/05/2015
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Krista pointed this out based on the info she got from logs for group nova. We need to confirm this issue and address it. There will be performance issues if we indeed doing this

[2015-11-05 11:43:49,247] DEBUG: glideinFrontendElement:315: 3 child query processes started
[2015-11-05 11:43:49,653] DEBUG: glideinFrontendElement:750: Schedd cmssrv272.fnal.gov has 0 running with max 5225
[2015-11-05 11:43:49,653] DEBUG: glideinFrontendElement:750: Schedd cmssrv273.fnal.gov has 0 running with max 19000
[2015-11-05 11:43:49,653] DEBUG: glideinFrontendElement:750: Schedd cmssrv271.fnal.gov has 1 running with max 19000

History

#1 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from New to Feedback
  • Assignee changed from Parag Mhashilkar to Marco Mambelli

There wasnt much performance overhead but all schedds were considered when creating a blacklist. However log messages were confusing and gave an impression that frontend was looking for jobs in all the schedds. Rest of the code looks for jobs only in the global and group specific schedds. Fixed both these issues in v3/10812

#2 Updated by Marco Mambelli over 4 years ago

  • Assignee changed from Marco Mambelli to Parag Mhashilkar

#3 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from Feedback to Resolved

Merged to branch_v3_2 and master

#4 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF