Scope/document those configurations requires process restart and those not

[wey-gu]

Introduction

Restart is expansive, and in many cases(like most of the time?) the user cannot afford a restart in online services, we have the capability to live update conf with the HTTP interface already, could we scope and document them on which could be updated and which cannot?

With this scope being defined and explicitly documented, more precisely control could be done by users, and the benefit is obviously worthy to be pursued.

And it could enable the nebula operator to reconcile with lower downtime when the configuration is being changed: vesoft-inc/nebula-operator#136

Contents

Related work