Project

General

Profile

Bug #5414

Multiple proxies not being handled correctly - numbers too low

Added by Igor Sfiligoi over 5 years ago. Updated 15 days ago.

Status:
New
Priority:
Low
Assignee:
Parag Mhashilkar
Category:
-
Target version:
Start date:
02/11/2014
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:

CMS

Duration:

Description

CMS just found out that in v3, using multiple proxies results in all numbers being divided by the number of proxies.

This includes at least max_idle and max_running.

This is very different than in v2, where those numbers went whole to each proxy.

This is definitely a problem for max_running, since there is no guarantee that all proxies will get the same amount out of a site.
I believe CMS is hurting due to this.

Not sure how problematic is the max_idle...
it definitely was a surprise for CMS, but at least it can be controlled to a certain degree at the FE config level.


Related issues

Related to GlideinWMS - Bug #5239: Factory monitoring broken - significantly scaled upClosed03/25/2014

History

#1 Updated by Igor Sfiligoi over 5 years ago

  • Assignee changed from Igor Sfiligoi to Parag Mhashilkar

Does #5239 cover this one as well?

#2 Updated by Parag Mhashilkar over 4 years ago

  • Priority changed from High to Low

#3 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_2_x to v3_4_x

#4 Updated by Marco Mambelli about 1 year ago

  • Target version changed from v3_4_x to v3_5_x

#5 Updated by Marco Mambelli 15 days ago

  • Target version changed from v3_5_x to v3_6_x


Also available in: Atom PDF