Skip to content

Conversation

@aishwarya24
Copy link
Collaborator

@netlify /stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem/#modify-the-configuration-file

@aishwarya24 aishwarya24 self-assigned this Dec 1, 2025
@aishwarya24 aishwarya24 added the area/documentation Documentation needed label Dec 1, 2025
@github-project-automation github-project-automation bot moved this to In progress in Documentation Dec 1, 2025
@netlify
Copy link

netlify bot commented Dec 1, 2025

Deploy Preview for infallible-bardeen-164bc9 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 72e80f6
🔍 Latest deploy log https://app.netlify.com/projects/infallible-bardeen-164bc9/deploys/6939ff6f8c0b780008ddb083
😎 Deploy Preview https://deploy-preview-29545--infallible-bardeen-164bc9.netlify.app/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem/#modify-the-configuration-file
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.


### Configure ClockBound (optional)

[ClockBound](https://github.com/aws/clock-bound) improves clock accuracy by several orders of magnitude and significantly reduces read-restart errors in YSQL. To enable ClockBound for cloud provider universes, set the provider runtime configuration flag `yb.provider.configure_clockbound_cloud_provisioning` to `true` before creating the universe. Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"cloud provider universes" - does this mean all universes created using any cloud provider configuration (and not on-premises?) Why is this not a provider setting?

@ddhodge ddhodge changed the title [DOC-1057] Configure ClockBound for YBA [DOC-1057][2025.2] Configure ClockBound for YBA Dec 8, 2025
| `node_ip` | The fully-qualified domain name or IP address of the node you are provisioning. Must be accessible to other nodes. |
| `tmp_directory` | The directory on the node to use for storing temporary files during provisioning. |
| `is_configure_clockbound` | Set to `true` to configure [ClockBound](https://github.com/aws/clock-bound) during provisioning. ClockBound improves clock accuracy by several orders of magnitude and significantly reduces read-restart errors in YSQL. ClockBound requires [chrony](https://chrony-project.org/) to be configured. <br/>When enabled, the provisioning script installs ClockBound as a systemd unit and configures it to communicate with chronyd. <br/> For new universes, the universe creation task automatically sets the [time_source](../../../reference/configuration/yb-master/#time-source) flag to `clockbound`. |
| `is_configure_clockbound` | Set to `true` to configure [ClockBound](https://github.com/aws/clock-bound) during provisioning. ClockBound improves clock accuracy by several orders of magnitude and significantly reduces read-restart errors in YSQL. ClockBound requires [chrony](https://chrony-project.org/) to be configured. <br/>When enabled, the provisioning script installs ClockBound as a systemd unit and configures it to communicate with chronyd. <br/>**For on-prem deployments:** When set to `true` and the node agent creates or updates the on-premises provider (using the YBA configuration options below), the provider is configured with `useClockbound: true`. This enables the universe creation task to automatically set the [time_source](../../../reference/configuration/yb-master/#time-source) flag to `clockbound` for new universes. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page is exclusively for on premises, so why are we making this distinction

Copy link
Contributor

@kv83821-yb kv83821-yb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Documentation needed

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

3 participants