[
https://issues.apache.org/jira/browse/KUDU-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888996#comment-15888996
]
Todd Lipcon commented on KUDU-1902:
-----------------------------------
I think this is expected behavior since ntp is returning 'UNSYNC'. Even if NTP
is running, this means that it isn't in sync and can't provide error estimates.
Running without system-provided NTP synchronization would be nice to have but
at this point I think it would be considered an improvement instead of a bug.
> NTP issue cause Server can not start
> ------------------------------------
>
> Key: KUDU-1902
> URL: https://issues.apache.org/jira/browse/KUDU-1902
> Project: Kudu
> Issue Type: Bug
> Components: master, tserver
> Affects Versions: 1.2.0
> Environment: Kudu1.2、CDH5.10.0、rhel7.2
> Reporter: YulongZ
> Priority: Critical
> Attachments: kudu-master.INFO
>
>
> First，all the node in the kudu cluster are NTP synchronised ，but
> ntp_gettime() and ntp_adjtime() return code error. All server can not start.
> [deployer@ZRR-POC419-39 ~]$ ntpq -p
> remote refid st t when poll reach delay offset jitter
> ==============================================================================
> *ZRR-POC419-36 LOCAL(0) 9 u 85 256 377 0.060 -0.209 0.041
> [deployer@ZRR-POC419-39 ~]$ ntpstat
> synchronised to NTP server (10.162.158.36) at stratum 10
> time correct to within 42 ms
> polling server every 256 s
> [deployer@ZRR-POC419-39 ~]$ ntptime
> ntp_gettime() returns code 5 (ERROR)
> time dc60206a.9f32acc0 Wed, Mar 1 2017 0:14:34.621, (.621867536),
> maximum error 16000000 us, estimated error 16 us, TAI offset 0
> ntp_adjtime() returns code 5 (ERROR)
> modes 0x0 (),
> offset 0.000 us, frequency 8.545 ppm, interval 1 s,
> maximum error 16000000 us, estimated error 16 us,
> status 0x6041 (PLL,UNSYNC,NANO,MODE),
> time constant 3, precision 0.001 us, tolerance 500 ppm,
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
