Todd Lipcon created KUDU-2844:
-
Summary: Avoid copying strings from dictionary or plain-encoded
blocks
Key: KUDU-2844
URL: https://issues.apache.org/jira/browse/KUDU-2844
Project: Kudu
Issue
[
https://issues.apache.org/jira/browse/KUDU-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860242#comment-16860242
]
Todd Lipcon commented on KUDU-2836:
---
Looking at the code of GcTcmalloc:
{code}
// Number of bytes in
[
https://issues.apache.org/jira/browse/KUDU-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858411#comment-16858411
]
Todd Lipcon commented on KUDU-2713:
---
I think we could bump to 1.11. A relatively simple fix though would
Todd Lipcon created KUDU-2841:
-
Summary: Expose HMS DB UUID to clients in MetastoreConfig
Key: KUDU-2841
URL: https://issues.apache.org/jira/browse/KUDU-2841
Project: Kudu
Issue Type:
[
https://issues.apache.org/jira/browse/KUDU-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854764#comment-16854764
]
Todd Lipcon commented on KUDU-749:
--
Hi [~ZhangYao]. That makes sense to me -- maybe the POC will expose
[
https://issues.apache.org/jira/browse/KUDU-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851097#comment-16851097
]
Todd Lipcon commented on KUDU-2826:
---
Yea, it seems fine to make this optimization and follow up with
[
https://issues.apache.org/jira/browse/KUDU-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850482#comment-16850482
]
Todd Lipcon commented on KUDU-2826:
---
[~ZhangYao] please check out KUDU-749 as well. I think your
[
https://issues.apache.org/jira/browse/KUDU-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844126#comment-16844126
]
Todd Lipcon commented on KUDU-2395:
---
[~aserbin] do we expect this will be fully fixed by KUDU-2791?
>
[
https://issues.apache.org/jira/browse/KUDU-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned KUDU-2366:
-
Assignee: (was: Todd Lipcon)
> LockManager consumes significant memory
>
[
https://issues.apache.org/jira/browse/KUDU-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831928#comment-16831928
]
Todd Lipcon commented on KUDU-2395:
---
Worth noting that this can also occur with stacks in
[
https://issues.apache.org/jira/browse/KUDU-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823544#comment-16823544
]
Todd Lipcon commented on KUDU-2466:
---
Is there a subset of this patch series that could be backported to
[
https://issues.apache.org/jira/browse/KUDU-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814808#comment-16814808
]
Todd Lipcon commented on KUDU-2771:
---
Can't just use an atomic pointer to a Promise?
> Re-factor the
[
https://issues.apache.org/jira/browse/KUDU-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned KUDU-2711:
-
Assignee: Will Berkeley (was: Todd Lipcon)
> Improve performance of GetTableLocations for large
[
https://issues.apache.org/jira/browse/KUDU-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned KUDU-2356:
-
Assignee: (was: Todd Lipcon)
> Idle WALs can consume significant memory
>
[
https://issues.apache.org/jira/browse/KUDU-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813647#comment-16813647
]
Todd Lipcon commented on KUDU-2768:
---
This is looking for a stronger durability guarantee, not a stronger
[
https://issues.apache.org/jira/browse/KUDU-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2763:
--
Labels: newbie (was: )
> Confusing "log matching property violated" message on new tablets
>
Todd Lipcon created KUDU-2763:
-
Summary: Confusing "log matching property violated" message on new
tablets
Key: KUDU-2763
URL: https://issues.apache.org/jira/browse/KUDU-2763
Project: Kudu
[
https://issues.apache.org/jira/browse/KUDU-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808235#comment-16808235
]
Todd Lipcon commented on KUDU-2758:
---
[~kwho] you might be interested in this for Impala's usage of KRPC
Todd Lipcon created KUDU-2758:
-
Summary: TLS socket writes in 16kb chunks with intervening
epoll/setsockopt syscalls
Key: KUDU-2758
URL: https://issues.apache.org/jira/browse/KUDU-2758
Project: Kudu
[
https://issues.apache.org/jira/browse/KUDU-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned KUDU-2750:
-
Assignee: HeLifu
> Add create timestamp to every table
> ---
>
>
[
https://issues.apache.org/jira/browse/KUDU-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2750.
---
Resolution: Fixed
Fix Version/s: 1.10.0
> Add create timestamp to every table
>
Todd Lipcon created KUDU-2717:
-
Summary: Add an environment variable for username override in
non-secure clusters
Key: KUDU-2717
URL: https://issues.apache.org/jira/browse/KUDU-2717
Project: Kudu
[
https://issues.apache.org/jira/browse/KUDU-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2713:
--
Affects Version/s: (was: 1.4.0)
> FS misinterprets file block size as file system block size
>
Todd Lipcon created KUDU-2713:
-
Summary: FS misinterprets file block size as file system block size
Key: KUDU-2713
URL: https://issues.apache.org/jira/browse/KUDU-2713
Project: Kudu
Issue Type:
Todd Lipcon created KUDU-2711:
-
Summary: Improve performance of GetTableLocations for large tables
Key: KUDU-2711
URL: https://issues.apache.org/jira/browse/KUDU-2711
Project: Kudu
Issue Type:
[
https://issues.apache.org/jira/browse/KUDU-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774539#comment-16774539
]
Todd Lipcon commented on KUDU-2708:
---
KUDU-2204 has some earlier explorations of this issue
> Possible
[
https://issues.apache.org/jira/browse/KUDU-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773530#comment-16773530
]
Todd Lipcon commented on KUDU-2706:
---
Seems we should probably re-report this upstream in addition to
Todd Lipcon created KUDU-2695:
-
Summary: Python client cannot connect on Ubuntu 18
Key: KUDU-2695
URL: https://issues.apache.org/jira/browse/KUDU-2695
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756389#comment-16756389
]
Todd Lipcon commented on KUDU-2685:
---
Dont we have some tools like this with 'kudu local_replica dump
[
https://issues.apache.org/jira/browse/KUDU-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701199#comment-16701199
]
Todd Lipcon commented on KUDU-2466:
---
[~wdberkeley] recently troubleshooted a similar issue where
[
https://issues.apache.org/jira/browse/KUDU-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2466:
--
Component/s: tserver
> Fault tolerant scanners can over-allocate memory and crash a cluster
>
[
https://issues.apache.org/jira/browse/KUDU-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699410#comment-16699410
]
Todd Lipcon commented on KUDU-2626:
---
[~wdberkeley] any idea on this? is this an edge case where the
[
https://issues.apache.org/jira/browse/KUDU-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584642#comment-16584642
]
Todd Lipcon commented on KUDU-2545:
---
Does Impala have any other local directory available that could be
Todd Lipcon created KUDU-2540:
-
Summary: Authorization failures on exactly-once RPCs cause FATAL
Key: KUDU-2540
URL: https://issues.apache.org/jira/browse/KUDU-2540
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562093#comment-16562093
]
Todd Lipcon commented on KUDU-2514:
---
hm, I'm afraid that making it only changeable at create time would
[
https://issues.apache.org/jira/browse/KUDU-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559117#comment-16559117
]
Todd Lipcon commented on KUDU-2514:
---
Sounds like a good idea. Were you thinking of including this in the
[
https://issues.apache.org/jira/browse/KUDU-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558861#comment-16558861
]
Todd Lipcon commented on KUDU-2502:
---
I'd be in favor of doing it as a maintenance op instead of a
[
https://issues.apache.org/jira/browse/KUDU-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553740#comment-16553740
]
Todd Lipcon commented on KUDU-2273:
---
Sure, seems reasonable. Are you in the dev list? There is recently
[
https://issues.apache.org/jira/browse/KUDU-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545397#comment-16545397
]
Todd Lipcon commented on KUDU-2502:
---
This is an interesting idea. Recently I had discussed a similar
[
https://issues.apache.org/jira/browse/KUDU-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540563#comment-16540563
]
Todd Lipcon commented on KUDU-2494:
---
bq. If I want to use a key-value store I use HBase not Kudu.
Sure,
[
https://issues.apache.org/jira/browse/KUDU-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1925:
--
Component/s: supportability
> Server should propagate the reason for token verification failure back to
[
https://issues.apache.org/jira/browse/KUDU-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540533#comment-16540533
]
Todd Lipcon commented on KUDU-2497:
---
In addition, are the existing logs relatively clear about the type
[
https://issues.apache.org/jira/browse/KUDU-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540433#comment-16540433
]
Todd Lipcon commented on KUDU-2495:
---
Alternatively we could have pstack_watcher use prctl(PR_SET_TRACER)
[
https://issues.apache.org/jira/browse/KUDU-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2494:
--
Target Version/s: (was: 1.7.1)
Fix Version/s: (was: 1.8.0)
(removed Fix Version -- we use
[
https://issues.apache.org/jira/browse/KUDU-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539038#comment-16539038
]
Todd Lipcon commented on KUDU-2494:
---
{quote}
Kudu API should provide "almost" the same query processing
[
https://issues.apache.org/jira/browse/KUDU-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reopened KUDU-2463:
---
> Different results returned by group by on count() metric
>
[
https://issues.apache.org/jira/browse/KUDU-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531953#comment-16531953
]
Todd Lipcon commented on KUDU-2483:
---
It sounds interesting to me. Impala could also make use of this
[
https://issues.apache.org/jira/browse/KUDU-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522882#comment-16522882
]
Todd Lipcon commented on KUDU-2483:
---
It would be great if you can share some of the performance results
[
https://issues.apache.org/jira/browse/KUDU-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520839#comment-16520839
]
Todd Lipcon commented on KUDU-2398:
---
I'd probably start with building from source. I know there are
[
https://issues.apache.org/jira/browse/KUDU-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520562#comment-16520562
]
Todd Lipcon commented on KUDU-531:
--
https://github.com/dgraph-io/tove has some interesting application of
[
https://issues.apache.org/jira/browse/KUDU-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520560#comment-16520560
]
Todd Lipcon commented on KUDU-2481:
---
Perhaps it would be easier to reuse ALICE for this? See KUDU-531.
[
https://issues.apache.org/jira/browse/KUDU-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520555#comment-16520555
]
Todd Lipcon commented on KUDU-2398:
---
[~sanysand...@gmail.com] sorry, not sure I understand the question.
[
https://issues.apache.org/jira/browse/KUDU-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508436#comment-16508436
]
Todd Lipcon commented on KUDU-2463:
---
If you can run a 'kudu cluster ksck --checksum_scan' on the whole
[
https://issues.apache.org/jira/browse/KUDU-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2463.
---
Resolution: Cannot Reproduce
Fix Version/s: n/a
> Different results returned by group by on
[
https://issues.apache.org/jira/browse/KUDU-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508383#comment-16508383
]
Todd Lipcon commented on KUDU-2463:
---
bq. but after the restart did not want to start some of the Kudu
[
https://issues.apache.org/jira/browse/KUDU-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505578#comment-16505578
]
Todd Lipcon commented on KUDU-2463:
---
Hi Tomas. [~danburkert] and I looked at this a bit today and we're
[
https://issues.apache.org/jira/browse/KUDU-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505532#comment-16505532
]
Todd Lipcon commented on KUDU-2465:
---
The issue seems to be that you're using a Debian 8 deb on Debian 9.
[
https://issues.apache.org/jira/browse/KUDU-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502170#comment-16502170
]
Todd Lipcon commented on KUDU-2461:
---
Can think of two options:
(1) just report it as a number
[
https://issues.apache.org/jira/browse/KUDU-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned KUDU-1465:
-
Assignee: (was: Todd Lipcon)
This is probably not so critical now that we are using a
[
https://issues.apache.org/jira/browse/KUDU-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1502.
---
Resolution: Fixed
Assignee: Todd Lipcon
Fix Version/s: 1.8.0
Fixed this in
[
https://issues.apache.org/jira/browse/KUDU-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493624#comment-16493624
]
Todd Lipcon commented on KUDU-1779:
---
Raising the memory limit may help avoid the issue. That said, the
[
https://issues.apache.org/jira/browse/KUDU-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484697#comment-16484697
]
Todd Lipcon commented on KUDU-2452:
---
I think we already do stop the failure detector during
[
https://issues.apache.org/jira/browse/KUDU-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484455#comment-16484455
]
Todd Lipcon commented on KUDU-2450:
---
oops, yea, I meant EBUSY as well :)
> pthread_mutex_destroy returns
[
https://issues.apache.org/jira/browse/KUDU-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483397#comment-16483397
]
Todd Lipcon commented on KUDU-2450:
---
Eagain on destroy indicates an attempt to destroy a locked mutex, so
[
https://issues.apache.org/jira/browse/KUDU-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2408.
---
Resolution: Fixed
Assignee: David Alves
Fix Version/s: 1.8.0
> Restarting masters and
[
https://issues.apache.org/jira/browse/KUDU-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1038:
--
Priority: Major (was: Minor)
> Deleting a tablet should also delete its log recovery directory, if any
[
https://issues.apache.org/jira/browse/KUDU-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1038:
--
Labels: supportability (was: )
> Deleting a tablet should also delete its log recovery directory, if
[
https://issues.apache.org/jira/browse/KUDU-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472163#comment-16472163
]
Todd Lipcon commented on KUDU-2433:
---
Quite possibly it's just due to the normal background stack tracing
[
https://issues.apache.org/jira/browse/KUDU-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467562#comment-16467562
]
Todd Lipcon commented on KUDU-2433:
---
I commented on the review, but also noting here: I dont think this
[
https://issues.apache.org/jira/browse/KUDU-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466197#comment-16466197
]
Todd Lipcon commented on KUDU-2428:
---
Note the docs for the lower and upper bound parameters for
[
https://issues.apache.org/jira/browse/KUDU-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2428.
---
Resolution: Invalid
> Segmentation fault when calling add_range_partition multiple times
>
[
https://issues.apache.org/jira/browse/KUDU-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2428:
--
Description:
Hi,
I'm trying to modify and run the following sample.cc program to create a table
with
[
https://issues.apache.org/jira/browse/KUDU-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2422.
---
Resolution: Fixed
Fix Version/s: 1.8.0
> Subprocess hang at startup in TSAN builds
>
[
https://issues.apache.org/jira/browse/KUDU-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460050#comment-16460050
]
Todd Lipcon commented on KUDU-2425:
---
Wonder if this is the same underlying issue as KUDU-2212 or
[
https://issues.apache.org/jira/browse/KUDU-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460013#comment-16460013
]
Todd Lipcon commented on KUDU-2371:
---
[~fwang29] since this was just committed, shouldn't the "fix
[
https://issues.apache.org/jira/browse/KUDU-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459939#comment-16459939
]
Todd Lipcon commented on KUDU-2035:
---
We should be careful that this doesn't increase CPU substantially
[
https://issues.apache.org/jira/browse/KUDU-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2423:
--
Issue Type: Bug (was: Improvement)
> rpc-test flaky in TestRpc.TestServerShutsDown (ENOTCONN errno)
>
Todd Lipcon created KUDU-2423:
-
Summary: rpc-test flaky in TestRpc.TestServerShutsDown (ENOTCONN
errno)
Key: KUDU-2423
URL: https://issues.apache.org/jira/browse/KUDU-2423
Project: Kudu
Issue
[
https://issues.apache.org/jira/browse/KUDU-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16457224#comment-16457224
]
Todd Lipcon commented on KUDU-2422:
---
Filed a bug with tsan here:
Todd Lipcon created KUDU-2422:
-
Summary: Subprocess hang at startup in TSAN builds
Key: KUDU-2422
URL: https://issues.apache.org/jira/browse/KUDU-2422
Project: Kudu
Issue Type: Improvement
Todd Lipcon created KUDU-2417:
-
Summary: Add further documentation on the diagnostics log
Key: KUDU-2417
URL: https://issues.apache.org/jira/browse/KUDU-2417
Project: Kudu
Issue Type:
[
https://issues.apache.org/jira/browse/KUDU-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451437#comment-16451437
]
Todd Lipcon commented on KUDU-2416:
---
[~granthenke] mind taking a look at this? I can add the missing
Todd Lipcon created KUDU-2416:
-
Summary: Incorrect fallthrough in Java PartialRow.setMin for
DECIMAL times
Key: KUDU-2416
URL: https://issues.apache.org/jira/browse/KUDU-2416
Project: Kudu
[
https://issues.apache.org/jira/browse/KUDU-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451395#comment-16451395
]
Todd Lipcon commented on KUDU-2415:
---
One other detail that looks important: this only happens if the
[
https://issues.apache.org/jira/browse/KUDU-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451395#comment-16451395
]
Todd Lipcon edited comment on KUDU-2415 at 4/24/18 11:26 PM:
-
One other detail
Todd Lipcon created KUDU-2415:
-
Summary: READ_YOUR_WRITES scan with no prior operation fails
Key: KUDU-2415
URL: https://issues.apache.org/jira/browse/KUDU-2415
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1366.
---
Resolution: Won't Fix
Fix Version/s: n/a
With recent improvements in tcmalloc I don't think
[
https://issues.apache.org/jira/browse/KUDU-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1977.
---
Resolution: Fixed
Fix Version/s: 1.8.0
Fixed in b2b8fb74dc564b5e55af6406982e80f2efa19f3c
>
[
https://issues.apache.org/jira/browse/KUDU-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2378.
---
Resolution: Fixed
Fix Version/s: 1.7.1
> Crash due to unaligned loads when building with clang
[
https://issues.apache.org/jira/browse/KUDU-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2414.
---
Resolution: Fixed
Fix Version/s: 1.8.0
> C++ client retries in a tight loop for SCANNER_EXPIRED
Todd Lipcon created KUDU-2414:
-
Summary: C++ client retries in a tight loop for SCANNER_EXPIRED
Key: KUDU-2414
URL: https://issues.apache.org/jira/browse/KUDU-2414
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2378:
--
Fix Version/s: 1.8.0
> Crash due to unaligned loads when building with clang 6.0
>
[
https://issues.apache.org/jira/browse/KUDU-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442792#comment-16442792
]
Todd Lipcon commented on KUDU-1621:
---
If actually flushing is tricky due to the fact that it may block
[
https://issues.apache.org/jira/browse/KUDU-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441705#comment-16441705
]
Todd Lipcon commented on KUDU-2411:
---
I think exposing BaseKuduTest as a public artifact would be pretty
[
https://issues.apache.org/jira/browse/KUDU-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2388:
--
Resolution: Fixed
Fix Version/s: 1.8.0
Status: Resolved (was: In Review)
> TSAN race
[
https://issues.apache.org/jira/browse/KUDU-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2394.
---
Resolution: Fixed
Fix Version/s: 1.8.0
> RpcStubTest.TestDontHandleTimedOutCalls flaky in ASAN
[
https://issues.apache.org/jira/browse/KUDU-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438122#comment-16438122
]
Todd Lipcon commented on KUDU-2395:
---
Looks like YugaByte did some work in a similar area:
[
https://issues.apache.org/jira/browse/KUDU-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2406:
--
Resolution: Fixed
Status: Resolved (was: In Review)
> Don't persist directory filesystem block
[
https://issues.apache.org/jira/browse/KUDU-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437720#comment-16437720
]
Todd Lipcon commented on KUDU-2287:
---
This would also be useful on masters. We've seen some cases where
[
https://issues.apache.org/jira/browse/KUDU-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-2151:
--
Labels: newbie (was: )
> ConsensusMetadata IO does not retry on EINTR
>
101 - 200 of 1359 matches
Mail list logo
