Open the database → Configuration tab in my.cubepath.com.
Lists the engine's tunable parameters with their current value, their default and allowed range, and their apply mode. Changes are staged and applied as a batch, so you review everything before anything restarts.
Apply modes
Every parameter is one of two kinds, and the difference decides when you should apply:
| Mode | What happens |
|---|---|
| Hot reload | Applied with no downtime. The engine picks the value up in place |
| Rolling restart | Replicas restart first, then the primary fails over. Connections briefly reconnect |
The confirmation dialog splits your pending changes into the two lists, so you can see at a glance whether you're about to cause a failover.
TipBatch your rolling-restart changes and apply them once, in a quiet window. Applying three restart-mode parameters separately means three failovers for no reason.
Making a change
Edit the values you want, watch the pending changes counter, and click Apply changes. Values are validated against the parameter's type and allowed range before anything is sent.
NoteConfiguration can only be changed while the database is active. If another operation is running (a scale, a credential rotation), wait for it to settle and try again.
What your application should expect
Even a hot reload can change behaviour mid-flight, and a rolling restart will break open connections. Applications need a connection pool that reconnects — that's true for every managed database, and it's the single most common cause of "the failover broke my app".
NoteIf the tab says there are no tunable parameters, that engine doesn't expose configuration yet.