[jira] [Commented] (KUDU-1905) TS can not start

[ https://issues.apache.org/jira/browse/KUDU-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891597#comment-15891597 ] Todd Lipcon commented on KUDU-1905: --- Interesting, this looks a lot like KUDU-1623, but that bug was fixed

[jira] [Commented] (KUDU-1905) TS can not start

[ https://issues.apache.org/jira/browse/KUDU-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891577#comment-15891577 ] Todd Lipcon commented on KUDU-1905: --- Thanks for reporting this. Do you think you could email me the

[jira] [Updated] (KUDU-1905) TS can not start

[ https://issues.apache.org/jira/browse/KUDU-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YulongZ updated KUDU-1905: -- Description: TabletServer can not start, here is the log: Mar 1, 8:40:03.872 PM ERROR compaction.cc:966

[jira] [Resolved] (KUDU-427) Support for strong authentication (kerberos)

[ https://issues.apache.org/jira/browse/KUDU-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-427. -- Resolution: Fixed Fix Version/s: 1.3.0 > Support for strong authentication (kerberos) >

[jira] [Commented] (KUDU-1837) kudu-jepsen reports non-linearizable history for the tserver-majorities-ring scenario

[ https://issues.apache.org/jira/browse/KUDU-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891347#comment-15891347 ] David Alves commented on KUDU-1837: --- Well I found something very wrong with our client that could

[jira] [Commented] (KUDU-1411) Implement HT timestamp propagation in the Java client

[ https://issues.apache.org/jira/browse/KUDU-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891345#comment-15891345 ] David Alves commented on KUDU-1411: --- Most of this is solved. The java client always did timestamp

[jira] [Commented] (KUDU-1411) Implement HT timestamp propagation in the Java client

[ https://issues.apache.org/jira/browse/KUDU-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891335#comment-15891335 ] Todd Lipcon commented on KUDU-1411: --- [~dralves] is this still the case? > Implement HT timestamp

[jira] [Resolved] (KUDU-944) All builder objects should return pointers or references consistently

[ https://issues.apache.org/jira/browse/KUDU-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-944. -- Resolution: Won't Fix Fix Version/s: n/a Now that we've released an API I don't think we can

[jira] [Resolved] (KUDU-14) Fault injection testing for common operations

[ https://issues.apache.org/jira/browse/KUDU-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-14. - Resolution: Duplicate Fix Version/s: n/a we've done a bunch of this since 2013 > Fault injection

[jira] [Commented] (KUDU-1560) Implement delta flush history GC

[ https://issues.apache.org/jira/browse/KUDU-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891178#comment-15891178 ] Mike Percy commented on KUDU-1560: -- Resolved as dup > Implement delta flush history GC >

[jira] [Updated] (KUDU-1782) Fault injection tests should exit with a special exit code

[ https://issues.apache.org/jira/browse/KUDU-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1782: -- Resolution: Fixed Fix Version/s: 1.2.0 Status: Resolved (was: In Review) > Fault

[jira] [Commented] (KUDU-1837) kudu-jepsen reports non-linearizable history for the tserver-majorities-ring scenario

[ https://issues.apache.org/jira/browse/KUDU-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891127#comment-15891127 ] Todd Lipcon commented on KUDU-1837: --- [~dralves] did you find this to be a test issue? > kudu-jepsen

[jira] [Resolved] (KUDU-84) rename simple_spinlock to gspinlock

[ https://issues.apache.org/jira/browse/KUDU-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-84. - Resolution: Won't Fix Fix Version/s: n/a > rename simple_spinlock to gspinlock >

[jira] [Commented] (KUDU-1813) Scan at a specific timestamp doesn't include that timestamp as committed

[ https://issues.apache.org/jira/browse/KUDU-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890992#comment-15890992 ] Todd Lipcon commented on KUDU-1813: --- [~dralves] do you have an opinion on this one? > Scan at a specific

[jira] [Updated] (KUDU-564) Consensus logging improvements for better operability

[ https://issues.apache.org/jira/browse/KUDU-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-564: - Target Version/s: Backlog (was: 1.3.0) > Consensus logging improvements for better operability >

[jira] [Updated] (KUDU-1465) Large allocations for scanner result buffers harm allocator thread caching

[ https://issues.apache.org/jira/browse/KUDU-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1465: -- Target Version/s: 1.4.0 (was: 1.3.0) > Large allocations for scanner result buffers harm allocator

[jira] [Updated] (KUDU-668) Log block container metadata files should be more forgiving to truncation

[ https://issues.apache.org/jira/browse/KUDU-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-668: - Target Version/s: Backlog (was: 1.3.0) > Log block container metadata files should be more forgiving to

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

[ https://issues.apache.org/jira/browse/KUDU-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-65: Target Version/s: Backlog (was: 1.3.0) > TS should remember master UUID and refuse to re-register to

[jira] [Updated] (KUDU-38) bootstrap should not replay logs that are known to be fully flushed

[ https://issues.apache.org/jira/browse/KUDU-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-38: Labels: data-scalability startup-time (was: ) > bootstrap should not replay logs that are known to be fully

[jira] [Updated] (KUDU-38) bootstrap should not replay logs that are known to be fully flushed

[ https://issues.apache.org/jira/browse/KUDU-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-38: Target Version/s: Backlog (was: 1.3.0) > bootstrap should not replay logs that are known to be fully flushed

[jira] [Updated] (KUDU-1779) Consensus "stuck" with all transaction trackers are at limit

[ https://issues.apache.org/jira/browse/KUDU-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1779: -- Target Version/s: 1.4.0 (was: 1.3.0) > Consensus "stuck" with all transaction trackers are at limit >

[jira] [Updated] (KUDU-1848) Simplified dictionary-compression for in-memory data

[ https://issues.apache.org/jira/browse/KUDU-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1848: -- Target Version/s: Backlog (was: 1.3.0) > Simplified dictionary-compression for in-memory data >

[jira] [Updated] (KUDU-1848) Simplified dictionary-compression for in-memory data

[ https://issues.apache.org/jira/browse/KUDU-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1848: -- Issue Type: Improvement (was: Bug) > Simplified dictionary-compression for in-memory data >

[jira] [Resolved] (KUDU-1835) Support compression of the WAL

[ https://issues.apache.org/jira/browse/KUDU-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-1835. --- Resolution: Fixed Fix Version/s: 1.3.0 > Support compression of the WAL >

[jira] [Resolved] (KUDU-884) CM rolling upgrade support

[ https://issues.apache.org/jira/browse/KUDU-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-884. -- Resolution: Invalid Fix Version/s: n/a This is a feature for CM/Cloudera to deal with, not

[jira] [Updated] (KUDU-1904) Nullable RLE columns with only null values crash on scan

[ https://issues.apache.org/jira/browse/KUDU-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans updated KUDU-1904: - Code Review: https://gerrit.cloudera.org/#/c/6184/ > Nullable RLE columns with only null

[jira] [Resolved] (KUDU-1904) Nullable RLE columns with only null values crash on scan

[ https://issues.apache.org/jira/browse/KUDU-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans resolved KUDU-1904. -- Resolution: Fixed Assignee: Andrew Wong Fix Version/s: 1.3.0 Fixed in

[jira] [Updated] (KUDU-1817) Failed to execute spark-shell with kudu-spark2 package

[ https://issues.apache.org/jira/browse/KUDU-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1817: -- Fix Version/s: (was: 1.3.0) 1.2.0 > Failed to execute spark-shell with

[jira] [Updated] (KUDU-1895) Document the effects of non-renewable authn tokens

[ https://issues.apache.org/jira/browse/KUDU-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin updated KUDU-1895: Summary: Document the effects of non-renewable authn tokens (was: Document effects of non-renewable

[jira] [Commented] (KUDU-1863) Deadlock while shutting down master

[ https://issues.apache.org/jira/browse/KUDU-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890615#comment-15890615 ] Alexey Serbin commented on KUDU-1863: - I think the issue is fixed by changelist

[jira] [Created] (KUDU-1905) TS can not start

YulongZ created KUDU-1905: - Summary: TS can not start Key: KUDU-1905 URL: https://issues.apache.org/jira/browse/KUDU-1905 Project: Kudu Issue Type: Bug Components: tserver Affects