[jira] [Updated] (KUDU-3173) Document time source options and recommendations
[
https://issues.apache.org/jira/browse/KUDU-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3173:
Description:
It's necessary to document existing time source options and recommendations for
Kudu. Since the introduction of the [built-in NTP
client|https://github.com/apache/kudu/commit/c103d51a52d00c3a9d062e06e20a5cc8c98df9a0]
and the [{{auto}} time
source|https://github.com/apache/kudu/commit/bd8e8f8b805bec5673590dffa67e48fbc9cfe208],
more options are available while deploying Kudu clusters, but these are not
properly documented yet.
Probably, the best place to add that information is at the [configuration
page|https://kudu.apache.org/docs/configuration.html].
was:
It's necessary to document existing time source options and recommendations for
Kudu. Since the introduction of the built-in NTP client and the {{auto}} time
source, more options are available, but those are not documented.
Probably, the proper place to add that information is at the [configuration
page|https://kudu.apache.org/docs/configuration.html].
> Document time source options and recommendations
>
>
> Key: KUDU-3173
> URL: https://issues.apache.org/jira/browse/KUDU-3173
> Project: Kudu
> Issue Type: Task
> Components: documentation
>Reporter: Alexey Serbin
>Priority: Major
>
> It's necessary to document existing time source options and recommendations
> for Kudu. Since the introduction of the [built-in NTP
> client|https://github.com/apache/kudu/commit/c103d51a52d00c3a9d062e06e20a5cc8c98df9a0]
> and the [{{auto}} time
> source|https://github.com/apache/kudu/commit/bd8e8f8b805bec5673590dffa67e48fbc9cfe208],
> more options are available while deploying Kudu clusters, but these are not
> properly documented yet.
> Probably, the best place to add that information is at the [configuration
> page|https://kudu.apache.org/docs/configuration.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3173) Document time source options and recommendations
[
https://issues.apache.org/jira/browse/KUDU-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-3173:
--
Component/s: documentation
> Document time source options and recommendations
>
>
> Key: KUDU-3173
> URL: https://issues.apache.org/jira/browse/KUDU-3173
> Project: Kudu
> Issue Type: Task
> Components: documentation
>Reporter: Alexey Serbin
>Priority: Major
>
> It's necessary to document existing time source options and recommendations
> for Kudu. Since the introduction of the built-in NTP client and the {{auto}}
> time source, more options are available, but those are not documented.
> Probably, the proper place to add that information is at the [configuration
> page|https://kudu.apache.org/docs/configuration.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KUDU-3173) Document time source options and recommendations
Alexey Serbin created KUDU-3173:
---
Summary: Document time source options and recommendations
Key: KUDU-3173
URL: https://issues.apache.org/jira/browse/KUDU-3173
Project: Kudu
Issue Type: Task
Reporter: Alexey Serbin
It's necessary to document existing time source options and recommendations for
Kudu. Since the introduction of the built-in NTP client and the {{auto}} time
source, more options are available, but those are not documented.
Probably, the proper place to add that information is at the [configuration
page|https://kudu.apache.org/docs/configuration.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3172) Enable hybrid clock and built-in NTP client in Docker by default
[ 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)
[jira] [Commented] (KUDU-3172) Enable hybrid clock and built-in NTP client in Docker by default
[
https://issues.apache.org/jira/browse/KUDU-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162899#comment-17162899
]
Alexey Serbin commented on KUDU-3172:
-
Another option is to set {{\-\-time_source=system_unsync}} if all the
dockerized Kudu cluster runs at a single host.
> 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`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KUDU-3172) Enable hybrid clock and built-in NTP client in Docker by default
Grant Henke created KUDU-3172: - Summary: 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 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`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (KUDU-3170) testSlowWriterDoesntBlockQueues is flaky in the ARM builds
[
https://issues.apache.org/jira/browse/KUDU-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-3170.
---
Fix Version/s: 1.13.0
Resolution: Fixed
> testSlowWriterDoesntBlockQueues is flaky in the ARM builds
> --
>
> Key: KUDU-3170
> URL: https://issues.apache.org/jira/browse/KUDU-3170
> Project: Kudu
> Issue Type: Bug
>Reporter: Grant Henke
>Assignee: Andrew Wong
>Priority: Major
> Fix For: 1.13.0
>
>
> It looks like testSlowWriterDoesntBlockQueues is flaky in the ARM builds. It
> has failed with the below in a few recent runs:
> {code}
> org.apache.kudu.subprocess.echo.TestEchoSubprocess >
> testSlowWriterDoesntBlockQueues FAILED java.lang.AssertionError: expected:<1>
> but was:<0> at org.junit.Assert.fail(Assert.java:89) at
> org.junit.Assert.failNotEquals(Assert.java:835) at
> org.junit.Assert.assertEquals(Assert.java:647) at
> org.junit.Assert.assertEquals(Assert.java:633) at
> org.apache.kudu.subprocess.echo.TestEchoSubprocess.testSlowWriterDoesntBlockQueues(TestEchoSubprocess.java:291)
> {code}
> *
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/20ae949/
> *
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/87eac39/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3090) Add owner concept in Kudu
[
https://issues.apache.org/jira/browse/KUDU-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162712#comment-17162712
]
ASF subversion and git services commented on KUDU-3090:
---
Commit 4fbfbcdda3005200b6570a48379c43bedfa0618b in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=4fbfbcd ]
[python] KUDU-3090 Add support for table ownership
Change-Id: I1c1e12a94459e0f04c769d38d96bffb12f337bda
Reviewed-on: http://gerrit.cloudera.org:8080/16217
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke
Reviewed-by: Andrew Wong
> Add owner concept in Kudu
> -
>
> Key: KUDU-3090
> URL: https://issues.apache.org/jira/browse/KUDU-3090
> Project: Kudu
> Issue Type: New Feature
> Components: authz, security
>Reporter: Hao Hao
>Assignee: Attila Bukor
>Priority: Major
> Labels: roadmap-candidate
>
> As mentioned in the Ranger integration design doc, Ranger supports ownership
> privilege by creating a default policy that allows \{OWNER} of a resource to
> access it without creating additional policy manually. Unless Kudu actually
> has a full support for owner, ownership privilege is not possible with Ranger
> integration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3170) testSlowWriterDoesntBlockQueues is flaky in the ARM builds
[
https://issues.apache.org/jira/browse/KUDU-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162711#comment-17162711
]
ASF subversion and git services commented on KUDU-3170:
---
Commit fd381f19f3bee14a25962f67f3bf3e6188d78af0 in kudu's branch
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=fd381f1 ]
KUDU-3170: deflake testSlowWriterDoesntBlockQueues
Previously the test would block the writer thread for 1s, expect a
timeout to happen within 1s, and check that the slow writer still
allowed for the outbound queue to be inserted to.
This led to some flakiness, as the first write may have sometimes
completed within 1s and allowed the second request to leave the outbound
queue and begin writing. This patch addresses this by extending the time
with which we block writes to extend past the execution deadline.
Without this patch, we saw frequent failures in ARM runs of the test,
and I saw 4/400 failures in dist-test. With the patch, the test passed
in dist-test 1600/1600 times.
Change-Id: I8b322782630b3ef935fb0264b6195d2ed72cc58c
Reviewed-on: http://gerrit.cloudera.org:8080/16221
Reviewed-by: Grant Henke
Tested-by: Andrew Wong
> testSlowWriterDoesntBlockQueues is flaky in the ARM builds
> --
>
> Key: KUDU-3170
> URL: https://issues.apache.org/jira/browse/KUDU-3170
> Project: Kudu
> Issue Type: Bug
>Reporter: Grant Henke
>Assignee: Andrew Wong
>Priority: Major
>
> It looks like testSlowWriterDoesntBlockQueues is flaky in the ARM builds. It
> has failed with the below in a few recent runs:
> {code}
> org.apache.kudu.subprocess.echo.TestEchoSubprocess >
> testSlowWriterDoesntBlockQueues FAILED java.lang.AssertionError: expected:<1>
> but was:<0> at org.junit.Assert.fail(Assert.java:89) at
> org.junit.Assert.failNotEquals(Assert.java:835) at
> org.junit.Assert.assertEquals(Assert.java:647) at
> org.junit.Assert.assertEquals(Assert.java:633) at
> org.apache.kudu.subprocess.echo.TestEchoSubprocess.testSlowWriterDoesntBlockQueues(TestEchoSubprocess.java:291)
> {code}
> *
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/20ae949/
> *
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/87eac39/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
