Project

General

Profile

Actions

Feature #19564

open

AutoReloadConfig usable in production

Added by Peter Amstutz about 2 years ago. Updated 8 months ago.

Status:
In Progress
Priority:
Normal
Assigned To:
Category:
API
Target version:
Story points:
-
Release:
Release relationship:
Auto

Description

For all services:

If the config file on disk changes, it checks that the config file is valid (config-check), then (if it is valid) restarts the service.

If the config file is not valid, that is reported via health check (possibly already implemented?)

Ideally, restarting the service means allowing existing in-flight requests to complete, while new requests use the config.

When running under "arvados-server boot", this is currently handled by a supervisor process. When not running under "arvados-server boot" services need to monitor the config file & be able to reload/restart themselves.


Related issues

Related to Arvados Epics - Idea #18685: Synchronize configuration on multi-node clusterNewActions
Actions #1

Updated by Peter Amstutz about 2 years ago

  • Description updated (diff)
Actions #2

Updated by Peter Amstutz about 2 years ago

  • Related to Idea #18685: Synchronize configuration on multi-node cluster added
Actions #3

Updated by Tom Clegg almost 2 years ago

  • Assigned To set to Tom Clegg
  • Status changed from New to In Progress
Actions #4

Updated by Peter Amstutz over 1 year ago

  • Release set to 60
Actions #5

Updated by Peter Amstutz 8 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF