[ 
https://issues.apache.org/jira/browse/KUDU-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grant Henke updated KUDU-3172:
------------------------------
    Description: 
Currently the docker entrypoint sets `--use_hybrid_clock=false` by default. 
This can cause unusual issues when snapshot scans are needed. Now that the 
built-in client is available we should switch to use that by default in the 
docker image by setting `--time_source=auto`.

For the quickstart cluster we can use `--time_source=system_unsync` given we 
expect all nodes will be on the same machine. 

  was:Currently the docker entrypoint sets `--use_hybrid_clock=false` by 
default. This can cause unusual issues when snapshot scans are needed. Now that 
the built-in client is available we should switch to use that by default in the 
docker image by setting `--time_source=auto`.


> Enable hybrid clock and built-in NTP client in Docker by default
> ----------------------------------------------------------------
>
>                 Key: KUDU-3172
>                 URL: https://issues.apache.org/jira/browse/KUDU-3172
>             Project: Kudu
>          Issue Type: Improvement
>    Affects Versions: 1.12.0
>            Reporter: Grant Henke
>            Assignee: Grant Henke
>            Priority: Minor
>
> Currently the docker entrypoint sets `--use_hybrid_clock=false` by default. 
> This can cause unusual issues when snapshot scans are needed. Now that the 
> built-in client is available we should switch to use that by default in the 
> docker image by setting `--time_source=auto`.
> For the quickstart cluster we can use `--time_source=system_unsync` given we 
> expect all nodes will be on the same machine. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to