-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tiup cluster check also support Chrony as NTP implementation #1696
Comments
Some history on this: pingcap/docs#5283 Isn't RHEL using Chrony starting with RHEL8 and not RHEL7? |
I have created a new EC2 instance using "Red Hat Enterprise Linux 7 with High Availability" at AWS Marketplace AMI. It installs and starts up [ec2-user@ip-172-31-43-69 ~]$ more /etc/redhat-release
Red Hat Enterprise Linux Server release 7.9 (Maipo) [ec2-user@ip-172-31-43-69 ~]$ rpm -qa |grep ntp
fontpackages-filesystem-1.44-8.el7.noarch
[ec2-user@ip-172-31-43-69 ~]$ rpm -qa |grep chro
chrony-3.4-1.el7.x86_64
[ec2-user@ip-172-31-43-69 ~]$ sudo systemctl status chrony
Unit chrony.service could not be found.
[ec2-user@ip-172-31-43-69 ~]$ sudo systemctl status chronyd
● chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-01-05 01:21:38 UTC; 2min 19s ago
Docs: man:chronyd(8)
man:chrony.conf(5)
Main PID: 624 (chronyd)
CGroup: /system.slice/chronyd.service
└─624 /usr/sbin/chronyd
Jan 05 01:21:37 localhost.localdomain systemd[1]: Starting NTP client/server...
Jan 05 01:21:38 localhost.localdomain chronyd[624]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVD...EBUG)
Jan 05 01:21:38 localhost.localdomain systemd[1]: Started NTP client/server.
Jan 05 01:21:45 ip-172-31-43-69.us-east-2.compute.internal chronyd[624]: Selected source 169.254.169.123
Hint: Some lines were ellipsized, use -l to show in full.
[ec2-user@ip-172-31-43-69 ~]$ |
tiup uses tidb-insight inside. So we need to implement tidb-insight for checking |
@yahonda from https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-configuring_ntp_using_the_chrony_suite : "The chrony suite is installed by default on some versions of Red Hat Enterprise Linux 7" This means our tools and documentation should include details about and support for Chrony. https://docs.pingcap.com/tidb/stable/check-before-deployment#check-and-install-the-ntp-service already included details about Chrony, no follow up needed for the docs. |
Indeed, we have added support for |
Thanks for the update. I'm looking for the future version of tiup supporting Chrony implementation. |
Feature Request
"tiup cluster check" command to support
Chrony
as NTP implementation in addition tontpd
Why the featue is needed:
Starting from Red Hat Enterprise 7 and Ubuntu 18.04, both Linux distributions added support Chrony as NTP as well as ntpd.
In some cases Chronyd is better than ntpd as described in these documentations.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-configuring_ntp_using_the_chrony_suite
https://ubuntu.com/blog/ubuntu-bionic-using-chrony-to-configure-ntp
Describe alternatives you've considered:
Use current
ntpd
.Teachability, Documentation, Adoption, Migration Strategy:
It looks like
checkNTP
depends onntpd
implementation, does not look like supportingchrony
.tiup/pkg/cluster/operation/check.go
Lines 194 to 210 in c925128
The text was updated successfully, but these errors were encountered: