[jira] [Updated] (KUDU-3097) whether master load deleted entries into memory could be configuable

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Description: The tablet of master is not under control of MVCC. The deleted entries like table

[jira] [Updated] (KUDU-3097) whether master load deleted entries into memory could be configuable

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Description: The (was: Recently I addressed a memory problem occurred by kudu master. Related info:

[jira] [Updated] (KUDU-3097) whether master load deleted entries into memory could be configuable

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Summary: whether master load deleted entries into memory could be configuable (was: master should

[jira] [Commented] (KUDU-2612) Implement multi-row transactions

[ https://issues.apache.org/jira/browse/KUDU-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119169#comment-17119169 ] Andrew Wong commented on KUDU-2612: --- I posted this design doc to the dev mailing list and intend on

[jira] [Resolved] (KUDU-2632) Add DATE data type

[ https://issues.apache.org/jira/browse/KUDU-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-2632. --- Fix Version/s: 1.12.0 Resolution: Fixed > Add DATE data type > -- > >

[jira] [Assigned] (KUDU-368) Run local benchmarks under perf-stat

[ https://issues.apache.org/jira/browse/KUDU-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin reassigned KUDU-368: -- Assignee: Alexey Serbin > Run local benchmarks under perf-stat >

[jira] [Updated] (KUDU-477) Implement block storage microbenchmark

[ https://issues.apache.org/jira/browse/KUDU-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-477: - Labels: benchmarks (was: ) > Implement block storage microbenchmark >

[jira] [Updated] (KUDU-523) Add comprehensive cfile read/write benchmarks to dashboard

[ https://issues.apache.org/jira/browse/KUDU-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-523: - Labels: benchmarks (was: ) > Add comprehensive cfile read/write benchmarks to dashboard >

[jira] [Updated] (KUDU-368) Run local benchmarks under perf-stat

[ https://issues.apache.org/jira/browse/KUDU-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-368: - Labels: benchmarks perf (was: perf) > Run local benchmarks under perf-stat >

[jira] [Resolved] (KUDU-545) TSAN failure in master_replication-itest

[ https://issues.apache.org/jira/browse/KUDU-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-545. -- Fix Version/s: NA Resolution: Fixed > TSAN failure in master_replication-itest >

[jira] [Resolved] (KUDU-515) Log-dump, and anything else that acts on logs must handle schema changes mid segment.

[ https://issues.apache.org/jira/browse/KUDU-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-515. -- Fix Version/s: 0.7.0 Resolution: Fixed > Log-dump, and anything else that acts on logs must

[jira] [Commented] (KUDU-515) Log-dump, and anything else that acts on logs must handle schema changes mid segment.

[ https://issues.apache.org/jira/browse/KUDU-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118853#comment-17118853 ] Grant Henke commented on KUDU-515: -- It looks like this was resolved with the following commits: *

[jira] [Updated] (KUDU-521) Consider splitting the WAL in two, one for replicated operations and one for local operations

[ https://issues.apache.org/jira/browse/KUDU-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-521: - Labels: roadmap-candidate scalability (was: ) > Consider splitting the WAL in two, one for replicated

[jira] [Updated] (KUDU-500) Changes to SysTables should be queryable on follower leaders upon replication

[ https://issues.apache.org/jira/browse/KUDU-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-500: - Labels: roadmap-candidate (was: ) > Changes to SysTables should be queryable on follower leaders upon

[jira] [Updated] (KUDU-437) Support tablet splits

[ https://issues.apache.org/jira/browse/KUDU-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-437: - Target Version/s: (was: 1.8.0) > Support tablet splits > - > > Key:

[jira] [Updated] (KUDU-423) Implement scalable and performant on-disk storage

[ https://issues.apache.org/jira/browse/KUDU-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-423: - Target Version/s: (was: 1.8.0) > Implement scalable and performant on-disk storage >

[jira] [Updated] (KUDU-388) Simplify C++ KuduScanner iteration API

[ https://issues.apache.org/jira/browse/KUDU-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-388: - Summary: Simplify C++ KuduScanner iteration API (was: Simplify KuduScanner iteration API) > Simplify C++

[jira] [Updated] (KUDU-351) Tag sessions with a descriptor

[ https://issues.apache.org/jira/browse/KUDU-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-351: - Labels: supportability (was: ) > Tag sessions with a descriptor > -- > >

[jira] [Updated] (KUDU-1768) Tablet server cannot recover after run out of disk space

[ https://issues.apache.org/jira/browse/KUDU-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-1768: -- Labels: roadmap-candidate (was: ) > Tablet server cannot recover after run out of disk space >

[jira] [Updated] (KUDU-320) Running out of space should be handled more gracefully

[ https://issues.apache.org/jira/browse/KUDU-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-320: - Labels: roadmap-candidate (was: ) > Running out of space should be handled more gracefully >

[jira] [Resolved] (KUDU-272) [java client] Investigate using FastTuple

[ https://issues.apache.org/jira/browse/KUDU-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-272. -- Fix Version/s: n/a Resolution: Won't Fix > [java client] Investigate using FastTuple >

[jira] [Resolved] (KUDU-245) Add ability to limit size of threadpool queue

[ https://issues.apache.org/jira/browse/KUDU-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-245. -- Fix Version/s: (was: Backlog) NA Resolution: Fixed > Add ability to limit

[jira] [Commented] (KUDU-80) Facility to dump master metadata

[ https://issues.apache.org/jira/browse/KUDU-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118817#comment-17118817 ] Grant Henke commented on KUDU-80: - This can be done via some of the more manual tools like `kudu

[jira] [Commented] (KUDU-39) RPC system metrics

[ https://issues.apache.org/jira/browse/KUDU-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118782#comment-17118782 ] Grant Henke commented on KUDU-39: - Resolving as we have a few RPC metrics: * rpcs_queue_overflow *

[jira] [Resolved] (KUDU-39) RPC system metrics

[ https://issues.apache.org/jira/browse/KUDU-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-39. - Fix Version/s: n/a Target Version/s: (was: Backlog) Resolution: Fixed > RPC system

[jira] [Commented] (KUDU-2604) Add label for tserver

[ https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118788#comment-17118788 ] Alexey Serbin commented on KUDU-2604: - [~granthenke], yes, I think the remaining functionality can be

[jira] [Updated] (KUDU-65) TS should refuse to re-register to different cluster

[ https://issues.apache.org/jira/browse/KUDU-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-65: Summary: TS should refuse to re-register to different cluster (was: TS should remember master UUID and

[jira] [Updated] (KUDU-18) Handle "slow readers" not holding too much memory

[ https://issues.apache.org/jira/browse/KUDU-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-18: Target Version/s: (was: 1.8.0) > Handle "slow readers" not holding too much memory >

[jira] [Commented] (KUDU-5) Shared memory transport for local scanners

[ https://issues.apache.org/jira/browse/KUDU-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118774#comment-17118774 ] Grant Henke commented on KUDU-5: Some related work is in progress here:

[jira] [Commented] (KUDU-2604) Add label for tserver

[ https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118772#comment-17118772 ] Grant Henke commented on KUDU-2604: --- [~aserbin] Do you think the remaining functionality not addressed

[jira] [Reopened] (KUDU-2604) Add label for tserver

[ https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin reopened KUDU-2604: - It seems this JIRA item contains some useful ideas and details which are orthogonal to current

[jira] [Comment Edited] (KUDU-2604) Add label for tserver

[ https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118729#comment-17118729 ] Grant Henke edited comment on KUDU-2604 at 5/28/20, 2:36 PM: - I think a

[jira] [Resolved] (KUDU-1013) MR input format read from any replica

[ https://issues.apache.org/jira/browse/KUDU-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-1013. --- Fix Version/s: NA Resolution: Won't Fix Resolving as wont fix given we don't really focus on

[jira] [Updated] (KUDU-2577) Support rebalancing data allocation across directories when adding a new data dir

[ https://issues.apache.org/jira/browse/KUDU-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-2577: -- Labels: roadmap-candidate (was: ) > Support rebalancing data allocation across directories when adding

[jira] [Resolved] (KUDU-577) Specification for expected semantics and client modes

[ https://issues.apache.org/jira/browse/KUDU-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-577. -- Fix Version/s: NA Resolution: Fixed > Specification for expected semantics and client modes >

[jira] [Resolved] (KUDU-3006) RebalanceIgnoredTserversTest.Basic is flaky

[ https://issues.apache.org/jira/browse/KUDU-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-3006. --- Fix Version/s: 1.12.0 Resolution: Fixed > RebalanceIgnoredTserversTest.Basic is flaky >

[jira] [Updated] (KUDU-3127) Have replica placement and rebalancing consider non-uniform hardware

[ https://issues.apache.org/jira/browse/KUDU-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-3127: -- Labels: roadmap-candidate (was: ) > Have replica placement and rebalancing consider non-uniform

[jira] [Resolved] (KUDU-2604) Add label for tserver

[ https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-2604. --- Fix Version/s: n/a Resolution: Duplicate > Add label for tserver > - > >

[jira] [Commented] (KUDU-2604) Add label for tserver

[ https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118729#comment-17118729 ] Grant Henke commented on KUDU-2604: --- I think a similar goal was achieved via the rack awareness feature

[jira] [Updated] (KUDU-2726) Very large tablets defeat budgeted compaction

[ https://issues.apache.org/jira/browse/KUDU-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-2726: -- Labels: density roadmap-candidate (was: ) > Very large tablets defeat budgeted compaction >

[jira] [Resolved] (KUDU-886) Cluster load balancing

[ https://issues.apache.org/jira/browse/KUDU-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KUDU-886. -- Fix Version/s: 1.9.0 Resolution: Fixed Kudu has the ability to rebalance load using the

[jira] [Updated] (KUDU-3061) Balance tablet leaders across TServers

[ https://issues.apache.org/jira/browse/KUDU-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-3061: -- Labels: performance roadmap-candidate scalability (was: balance features performance) > Balance

[jira] [Comment Edited] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118571#comment-17118571 ] wangningito edited comment on KUDU-3097 at 5/28/20, 11:42 AM: -- Loading all

[jira] [Commented] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118571#comment-17118571 ] wangningito commented on KUDU-3097: --- Loading all data into memory. !image-2020-05-28-19-41-05-485.png!  

[jira] [Updated] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Attachment: image-2020-05-28-19-41-05-485.png > master should delete table info if table deleted,

[jira] [Updated] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Attachment: (was: screenshot-2.png) > master should delete table info if table deleted, instead of

[jira] [Updated] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Attachment: screenshot-2.png > master should delete table info if table deleted, instead of keeping

[jira] [Updated] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

[ https://issues.apache.org/jira/browse/KUDU-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangningito updated KUDU-3097: -- Attachment: screenshot-1.png > master should delete table info if table deleted, instead of keeping