Project

General

Profile

Actions

User story #14333

open

Remote run should optionnaly honor splay time in async mode

Added by François ARMAND almost 6 years ago. Updated about 4 years ago.

Status:
New
Priority:
N/A
Category:
Relay server or API
Target version:
-
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Name check:
Fix check:
Regression:

Description

On a big infra, asking for a remote run trigger the run every where at once. We should honore splay time on nodes for remote run in async mode. Or even better: we should had an option to ask to the node to honore it.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #14331: Trigger agent update and run after policy server has finished policy generationReleasedAlexis MoussetActions
Actions #1

Updated by François ARMAND almost 6 years ago

  • Related to Bug #14330: By default, no group are supervised and new group are not supervised added
Actions #2

Updated by François ARMAND almost 6 years ago

  • Related to deleted (Bug #14330: By default, no group are supervised and new group are not supervised )
Actions #3

Updated by François ARMAND almost 6 years ago

  • Related to Bug #14331: Trigger agent update and run after policy server has finished policy generation added
Actions #4

Updated by Benoît PECCATTE almost 6 years ago

Complying with a splay time means waiting for it, ie not running remote run.

Actions #5

Updated by François ARMAND almost 6 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions #6

Updated by Benoît PECCATTE almost 6 years ago

  • Subject changed from Remote run should honore splay time to Remote run should honor splay time
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 52
Actions #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
  • Priority changed from 52 to 51
Actions #8

Updated by François ARMAND over 5 years ago

  • Subject changed from Remote run should honor splay time to Remote run should optionnaly honor splay time in async mode
  • Priority changed from 51 to 50
Actions #9

Updated by François ARMAND over 5 years ago

I'm setting to "major" because for the given use case (ie big infra), it may really be disruptive.

Actions #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
Actions #11

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions #12

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 50 to 49
Actions #13

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 49 to 47
Actions #14

Updated by Alexis Mousset about 5 years ago

  • Tracker changed from Bug to User story
  • Severity deleted (Major - prevents use of part of Rudder | no simple workaround)
  • Priority deleted (47)
Actions #15

Updated by Alexis Mousset about 5 years ago

This is not actually a bug.

Actions #16

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #17

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #18

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #19

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #20

Updated by Benoît PECCATTE over 4 years ago

  • Target version changed from 5.0.18 to 6.2.0~beta1
Actions #21

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.2.0~beta1 to 6.2.0~rc1
Actions #22

Updated by François ARMAND about 4 years ago

  • Target version deleted (6.2.0~rc1)
Actions

Also available in: Atom PDF