[jira] [Updated] (KUDU-2878) kudu CLI in kerberized environment: connection negotiation fails due to inability to validate tserver's TLS certificate
[
https://issues.apache.org/jira/browse/KUDU-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-2878:
Attachment: tls-negotiation-trace.txt.xz
> kudu CLI in kerberized environment: connection negotiation fails due to
> inability to validate tserver's TLS certificate
> ---
>
> Key: KUDU-2878
> URL: https://issues.apache.org/jira/browse/KUDU-2878
> Project: Kudu
> Issue Type: Bug
> Components: client, tserver
>Affects Versions: 1.9.0, 1.10.0
>Reporter: Alexey Serbin
>Priority: Major
> Attachments: tls-negotiation-trace.txt.xz
>
>
> Rarely, when running {{kudu perf loadgen}} multiple times in a succession in
> kerberized/secure environment, the tool fails due to connection negotiation
> failure. The negotiation fails because of the client being unable to verify
> tserver's certificate. The client-side connection negotiation trace with the
> rest of the {{kudu}} CLI binary's output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KUDU-2878) kudu CLI in kerberized environment: connection negotiation fails due to inability to validate tserver's TLS certificate
Alexey Serbin created KUDU-2878:
---
Summary: kudu CLI in kerberized environment: connection
negotiation fails due to inability to validate tserver's TLS certificate
Key: KUDU-2878
URL: https://issues.apache.org/jira/browse/KUDU-2878
Project: Kudu
Issue Type: Bug
Components: client, tserver
Affects Versions: 1.9.0, 1.10.0
Reporter: Alexey Serbin
Rarely, when running {{kudu perf loadgen}} multiple times in a succession in
kerberized/secure environment, the tool fails due to connection negotiation
failure. The negotiation fails because of the client being unable to verify
tserver's certificate. The client-side connection negotiation trace with the
rest of the {{kudu}} CLI binary's output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KUDU-2877) Support logging to files and stderr at the same time
Grant Henke created KUDU-2877: - Summary: Support logging to files and stderr at the same time Key: KUDU-2877 URL: https://issues.apache.org/jira/browse/KUDU-2877 Project: Kudu Issue Type: Improvement Components: docker Reporter: Grant Henke Support logging to both the _--log_dir_ directory and to stderr via _--logtostderr_ at the same time. This could be done with a new flag. __ This would be useful in docker environments where is standard to log to stderr, but we still want the logs to be viewable in the web ui. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KUDU-2876) Audit the semantics and the usage of Tabet::GetComponents() in tablet.cc
Alexey Serbin created KUDU-2876:
---
Summary: Audit the semantics and the usage of
Tabet::GetComponents() in tablet.cc
Key: KUDU-2876
URL: https://issues.apache.org/jira/browse/KUDU-2876
Project: Kudu
Issue Type: Task
Components: tserver
Affects Versions: 1.10.0
Reporter: Alexey Serbin
As of now, {{Tablet::GetComponents()}} is used in multiple places in the
implementation of the {{kudu::tablet::Tablet}} class. In some cases the code
verifies that the output parameter is null, in others not. And it seems in
some cases returning null would be an error, in some cases not. It would be
nice to do a bit of audit in that area to make sure there will be no unexpected
SIGSEGV crashes in some corner cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KUDU-1644) Simplify IN-list predicate values based on tablet partition key or rowset PK bounds
[ https://issues.apache.org/jira/browse/KUDU-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873493#comment-16873493 ] Todd Lipcon commented on KUDU-1644: --- Worth noting there's also the case where the merging of the DRS bounds with the IN-list can fully eliminate the DRS (ie the predicate converts to 'None') in which case the rowset can be skipped. I don't know if we implement that optimization today but seems again like an easy win. > Simplify IN-list predicate values based on tablet partition key or rowset PK > bounds > --- > > Key: KUDU-1644 > URL: https://issues.apache.org/jira/browse/KUDU-1644 > Project: Kudu > Issue Type: Sub-task > Components: tablet >Reporter: Dan Burkert >Priority: Major > > When new scans are optimized by the tablet, the tablet's partition key bounds > aren't taken into account in order to remove predicates from the scan. One > of the most important such optimizations is that IN-list predicates could > remove values based on the tablet's constraints. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KUDU-1644) Simplify IN-list predicate values based on tablet partition key bounds
[
https://issues.apache.org/jira/browse/KUDU-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873487#comment-16873487
]
Todd Lipcon commented on KUDU-1644:
---
This optimization can even happen at the DRS level, which is useful for IN-list
on PK prefixes. For example, we may have {{PK IN ('foo', 'bar')}} but within a
given DRS we know from the DRS row bounds that we have an implied predicate
{{PK BETWEEN 'apple' and 'cat'}}. If we merge that implied predicate with the
IN list, it simplifies to {{PK = 'bar'}} which can be evaluated as a range scan.
This isn't as general as the proposal in KUDU-2875, but in the common case of a
well-compacted table, it could possibly have almost the same level benefit vs
the naive full scan of the PK column.
> Simplify IN-list predicate values based on tablet partition key bounds
> --
>
> Key: KUDU-1644
> URL: https://issues.apache.org/jira/browse/KUDU-1644
> Project: Kudu
> Issue Type: Sub-task
> Components: tablet
>Reporter: Dan Burkert
>Priority: Major
>
> When new scans are optimized by the tablet, the tablet's partition key bounds
> aren't taken into account in order to remove predicates from the scan. One
> of the most important such optimizations is that IN-list predicates could
> remove values based on the tablet's constraints.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KUDU-1644) Simplify IN-list predicate values based on tablet partition key or rowset PK bounds
[ https://issues.apache.org/jira/browse/KUDU-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1644: -- Summary: Simplify IN-list predicate values based on tablet partition key or rowset PK bounds (was: Simplify IN-list predicate values based on tablet partition key bounds) > Simplify IN-list predicate values based on tablet partition key or rowset PK > bounds > --- > > Key: KUDU-1644 > URL: https://issues.apache.org/jira/browse/KUDU-1644 > Project: Kudu > Issue Type: Sub-task > Components: tablet >Reporter: Dan Burkert >Priority: Major > > When new scans are optimized by the tablet, the tablet's partition key bounds > aren't taken into account in order to remove predicates from the scan. One > of the most important such optimizations is that IN-list predicates could > remove values based on the tablet's constraints. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KUDU-2875) Convert scans with IN-list predicates on primary key prefix to multiple scans with equality predicates
Todd Lipcon created KUDU-2875: - Summary: Convert scans with IN-list predicates on primary key prefix to multiple scans with equality predicates Key: KUDU-2875 URL: https://issues.apache.org/jira/browse/KUDU-2875 Project: Kudu Issue Type: Sub-task Components: perf, tserver Reporter: Todd Lipcon In the case that an IN predicate is applied to a prefix of the primary key (or to column N of a composite key with equality predicates present on all columns 10'. In this case, we can internally convert to two scans 'entity = 1 and timestamp > 10' and 'entity = 3 and timestamp > 10'. These can then be evaluated efficiently using the index. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
