docs: document dedicated-nodes and do-not-disrupt deployment options#2165
docs: document dedicated-nodes and do-not-disrupt deployment options#2165velo wants to merge 5 commits into
Conversation
Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
|
Related PRs — ship together:
|
|
I'm wondering about if it's a good thing in general to include cloud-specific things to the doc? Technically these options are orthogonal to SQRL, at this point cloud processes and validates them. I guess it makes sense to keep documentation centralized, but then I think it would make sense to restructure the docs and separate Cloud-specific things to their own page or something. |
…sql.parameters passthrough) Signed-off-by: Marvin Froeder <velo.br@gmail.com>
|
|
||
| ## Create Indexes (`create-indexes`) | ||
|
|
||
| Controls whether the PostgreSQL table indexes are created for the deployment. Defaults to `true`. PostgreSQL only. |
There was a problem hiding this comment.
it only applies to secondary indexes, right? Not the primary key indexes that are defined on the table itself. Those are needed even during replay, otherwise Postgres cannot effectively upsert and every upsert becomes a full table scan.
There was a problem hiding this comment.
Correct, we only strip the CREATE INDEX statements
no PKs are hurt on this process
Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
velo
changed the title
3 participants
Documents two cloud-deployment options in
documentation/docs/configuration-engine/cloud-deployment.md:*-node-groups— pins a component's pods onto dedicated nodes (hard requirement → Pending if unavailable). Each name derives a node selector (N=true) + a toleration for taint keyN; infra labels+taints the node group. Coverstaskmanager-node-groups/jobmanager-node-groups(Flink),node-groups(Postgres, Vert.x).do-not-disrupt— protects pods from voluntary autoscaler consolidation. Documents per-engine defaults (Flink false, Postgres true, Vert.x false).Matches the implementation in cloud-compilation (per-service deployment config passthrough).