Reloader icon indicating copy to clipboard operation
Reloader copied to clipboard

Simulteous Reloads maxing out cluster resources

Open nerney opened this issue 4 years ago • 2 comments

Is there any way to not have the reloader try to do all the reloading simultaneously, and, instead work it's way through the list with different concurrency?

nerney avatar Nov 25 '20 16:11 nerney

Currently, there is no such way. If there are concurrent events happening, the reloader will try to resolve those events concurrently as well. If you are running reloader in cluster scope, then you can try to run reloader on namespace scope where it's needed to mitigate the issue.

faizanahmad055 avatar Nov 25 '20 18:11 faizanahmad055

@nerney nice suggestion!

Possible options:

  1. reloader per namespace
  2. add support in reloader to run multiple instances in HA mode
  3. add support of some sort of queuing

any other thoughts?

rasheedamir avatar Nov 28 '20 13:11 rasheedamir

Marking it as stale and closing it. Please reopen if required.

faizanahmad055 avatar Jan 05 '23 21:01 faizanahmad055