Could we upgrade frontier_client in 5_3_X?

[DrDaveD]

Last night we had a frontier server overload problem that would have been avoided if they were using the latest frontier_client. They were using 5_3_22_patch1 and I've been told it will still be in production use for quite a while. Could we upgrade 5_3_X to frontier_client version 2.8.10 or 2.8.11? They are much more gentle on the frontier servers when there are server-caused errors.

According to the frontier server logs, CMSSW 6_2_X and 7_0_X are also on the too-old 2.8.8, so probably they should also be upgraded if we do 5_3_X. 7_1_X and 7_2_X are 2.8.10 and 7_3_X is 2.8.11.

It would seem strange to have an older release on a newer frontier_client, so I suggest updating 5_3_X, 6_2_X, and 7_0_X to 2.8.10. The only change in 2.8.11 was related to having more than 1024 file descriptors, which is not very likely to happen in the older releases.

[DrDaveD]

Hello, does anybody have any reaction to this?

[davidlange6]

Hi Dave
apologies - was offline/computing week… we'll add to our development cycle this week and back port as needed.

David

On Nov 20, 2014, at 10:51 PM, DrDaveD notifications@github.com wrote:

Hello, does anybody have any reaction to this?

—
Reply to this email directly or view it on GitHub.

[ktf]

@Degano can you start preparing the spec for this?

[ghost]

@ktf ok, I'm on it.

[ktf]

@Degano please close this issue when you are done.

[ghost]

Done in cms-sw/cmsdist#1213 and cms-sw/cmsdist#1214.
Closing this now.

[DrDaveD]

This did only 5_3_X, correct? What about 6_2_X and 7_0_X? They're still in use, do they get new releases?

[ktf]

@davidlange6 might want to pop in, but the plan is to kill them, so we'd
rather avoid yet another release.

On Wed Nov 26 2014 at 6:15:37 PM DrDaveD notifications@github.com wrote:

This did only 5_3_X, correct? What about 6_2_X and 7_0_X? They're still in
use, do they get new releases?

—
Reply to this email directly or view it on GitHub
#6227 (comment).

[davidlange6]

62x is not useful… 62xSLHC would be useful though. 70x can go into the IB and if we ever make a release again,we can include it.

On Nov 26, 2014, at 8:50 PM, Giulio Eulisse notifications@github.com
wrote:

@davidlange6 might want to pop in, but the plan is to kill them, so we'd
rather avoid yet another release.

On Wed Nov 26 2014 at 6:15:37 PM DrDaveD notifications@github.com wrote:

This did only 5_3_X, correct? What about 6_2_X and 7_0_X? They're still in
use, do they get new releases?

—
Reply to this email directly or view it on GitHub
#6227 (comment).

—
Reply to this email directly or view it on GitHub.

[ghost]

I updated it for SLHC and in turns also for all 6_2_X as they uses the same branches.