Skip to main content
added 512 characters in body
Source Link
Ta Mu
  • 6.8k
  • 5
  • 42
  • 83

AFAIK you cannot influence the order how Docker Swarm starts containers for services.

Is that possible with:

  • Mesos?
  • K8s (Kubernetes)?
  • Rancher?
  • Other?

This question is not about specific orchestration of dependent services but the problem that if you run 10 services each with one JVM this creates a load peak. The system slows down and you need complex loops to wait for other services. Are there any mechanisms known in other orchestration concepts to manage the startup somehow?

For example, in completely other domain, in JMeter you can tell a timeframe in which a thread group will start. So could I say "try to start this service with some offset"?

AFAIK you cannot influence the order how Docker Swarm starts containers for services.

Is that possible with:

  • Mesos?
  • K8s (Kubernetes)?
  • Rancher?
  • Other?

AFAIK you cannot influence the order how Docker Swarm starts containers for services.

Is that possible with:

  • Mesos?
  • K8s (Kubernetes)?
  • Rancher?
  • Other?

This question is not about specific orchestration of dependent services but the problem that if you run 10 services each with one JVM this creates a load peak. The system slows down and you need complex loops to wait for other services. Are there any mechanisms known in other orchestration concepts to manage the startup somehow?

For example, in completely other domain, in JMeter you can tell a timeframe in which a thread group will start. So could I say "try to start this service with some offset"?

Source Link
Ta Mu
  • 6.8k
  • 5
  • 42
  • 83

Defined start sequence of containers

AFAIK you cannot influence the order how Docker Swarm starts containers for services.

Is that possible with:

  • Mesos?
  • K8s (Kubernetes)?
  • Rancher?
  • Other?