[jira] [Updated] (KUDU-721) Support for DECIMAL type

[ https://issues.apache.org/jira/browse/KUDU-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-721: - Target Version/s: 1.7.0 (was: 1.6.0) > Support for DECIMAL type > > >

[jira] [Updated] (KUDU-2240) Expose partitioning information in a straightforward way in the Java API

[ https://issues.apache.org/jira/browse/KUDU-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Bukor updated KUDU-2240: --- Target Version/s: 1.7.0 (was: 1.6.0) > Expose partitioning information in a straightforward way in

[jira] [Assigned] (KUDU-2126) DeleteTablet RPC on an already deleted tablet should be a no-op

[ https://issues.apache.org/jira/browse/KUDU-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey F. Lukman reassigned KUDU-2126: --- Assignee: Jeffrey F. Lukman > DeleteTablet RPC on an already deleted tablet should be

[jira] [Created] (KUDU-2265) A non-leader master uses self-signed server TLS cert if it hasn't ever run as a leader

Alexey Serbin created KUDU-2265: --- Summary: A non-leader master uses self-signed server TLS cert if it hasn't ever run as a leader Key: KUDU-2265 URL: https://issues.apache.org/jira/browse/KUDU-2265

[jira] [Commented] (KUDU-2265) A non-leader master uses self-signed server TLS cert if it hasn't ever run as a leader

[ https://issues.apache.org/jira/browse/KUDU-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331127#comment-16331127 ] Todd Lipcon commented on KUDU-2265: --- Would be great if we could augment this message

[jira] [Commented] (KUDU-2265) A non-leader master uses self-signed server TLS cert if it hasn't ever run as a leader

[ https://issues.apache.org/jira/browse/KUDU-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331197#comment-16331197 ] Alexey Serbin commented on KUDU-2265: - [~tlipcon], yes, I think that would be easier to troubleshoot.

[jira] [Updated] (KUDU-1489) Use WAL directory for tablet metadata files

[ https://issues.apache.org/jira/browse/KUDU-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wong updated KUDU-1489: -- Resolution: Fixed Fix Version/s: 1.7.0 Status: Resolved (was: In Review) Resolved as 

[jira] [Updated] (KUDU-2267) Client may see negotiation failure when talks to master followers with only self signed cert

[ https://issues.apache.org/jira/browse/KUDU-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated KUDU-2267: -- Summary: Client may see negotiation failure when talks to master followers with only self signed cert (was:

[jira] [Created] (KUDU-2267) Client may see negotiation failure exception when talks to master followers with only self signed cert

Hao Hao created KUDU-2267: - Summary: Client may see negotiation failure exception when talks to master followers with only self signed cert Key: KUDU-2267 URL: https://issues.apache.org/jira/browse/KUDU-2267

[jira] [Updated] (KUDU-2267) Client may see negotiation failure when talks to master followers with only self signed cert

[ https://issues.apache.org/jira/browse/KUDU-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated KUDU-2267: -- Description: Currently, if a master has never been a leader from the very start of the cluster, it has just

[jira] [Commented] (KUDU-869) Support PRE_VOTER config membership type

[ https://issues.apache.org/jira/browse/KUDU-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331420#comment-16331420 ] Todd Lipcon commented on KUDU-869: -- [~mpercy] [~aserbin] this can be resolved, right? > Support PRE_VOTER

[jira] [Commented] (KUDU-2265) A non-leader master uses self-signed server TLS cert if it hasn't ever run as a leader

[ https://issues.apache.org/jira/browse/KUDU-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331421#comment-16331421 ] Todd Lipcon commented on KUDU-2265: --- [~aserbin] k I'm actually working the error message improvements

[jira] [Commented] (KUDU-869) Support PRE_VOTER config membership type

[ https://issues.apache.org/jira/browse/KUDU-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331428#comment-16331428 ] Alexey Serbin commented on KUDU-869: [~tlipcon], yes, I think we can mark this as resolved: the

[jira] [Resolved] (KUDU-869) Support PRE_VOTER config membership type

[ https://issues.apache.org/jira/browse/KUDU-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin resolved KUDU-869. Resolution: Fixed Fix Version/s: 1.7.0 This particular feature with corresponding operations

[jira] [Updated] (KUDU-2126) DeleteTablet RPC on an already deleted tablet should be a no-op

[ https://issues.apache.org/jira/browse/KUDU-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey F. Lukman updated KUDU-2126: Code Review: http://gerrit.cloudera.org:8080/9069 > DeleteTablet RPC on an already deleted

[jira] [Created] (KUDU-2266) Add OpId to pre-election / election log messages

Mike Percy created KUDU-2266: Summary: Add OpId to pre-election / election log messages Key: KUDU-2266 URL: https://issues.apache.org/jira/browse/KUDU-2266 Project: Kudu Issue Type: Improvement

[jira] [Closed] (KUDU-2241) NoSuchMethodError happened when run flume agent using kudu flume sink

[ https://issues.apache.org/jira/browse/KUDU-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changyao Ye closed KUDU-2241. - Resolution: Fixed > NoSuchMethodError happened when run flume agent using kudu flume sink >

[jira] [Commented] (KUDU-2241) NoSuchMethodError happened when run flume agent using kudu flume sink

[ https://issues.apache.org/jira/browse/KUDU-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331768#comment-16331768 ] Aki Ariga commented on KUDU-2241: - It seems [this

[jira] [Updated] (KUDU-2267) Client may see negotiation failure when talks to master followers with only self signed cert

[ https://issues.apache.org/jira/browse/KUDU-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated KUDU-2267: -- Issue Type: Improvement (was: Bug) > Client may see negotiation failure when talks to master followers with

[jira] [Resolved] (KUDU-2193) Severe lock contention on TSTabletManager lock

[ https://issues.apache.org/jira/browse/KUDU-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2193. --- Resolution: Fixed Fix Version/s: 1.6.0 I fixed this in 1.6 > Severe lock contention on

[jira] [Resolved] (KUDU-1721) Expose ability to force an unsafe Raft configuration change

[ https://issues.apache.org/jira/browse/KUDU-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-1721. --- Resolution: Fixed Assignee: Dinesh Bhat (was: zhangsong) Fix Version/s: 1.4.0 >

[jira] [Resolved] (KUDU-1330) Add tool to unsafely recover from loss of majority (or all) tablet replicas

[ https://issues.apache.org/jira/browse/KUDU-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-1330. --- Resolution: Fixed Fix Version/s: 1.4.0 Target Version/s: (was: 1.5.0) > Add tool to

[jira] [Commented] (KUDU-1720) Expose ability to appoint a replica as leader via RPC

[ https://issues.apache.org/jira/browse/KUDU-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331611#comment-16331611 ] Todd Lipcon commented on KUDU-1720: --- [~mpercy] [~wdberkeley] do you guys think this is still necessary?I

[jira] [Commented] (KUDU-1391) 2 of 3 replica alive but failed to elect leader

[ https://issues.apache.org/jira/browse/KUDU-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331612#comment-16331612 ] Todd Lipcon commented on KUDU-1391: --- [~mpercy] I believe this should be considered fixed back when we did

[jira] [Updated] (KUDU-441) Support tablet merges

[ https://issues.apache.org/jira/browse/KUDU-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-441: - Issue Type: New Feature (was: Bug) > Support tablet merges > - > >

[jira] [Updated] (KUDU-2244) spinlock contention in raft_consensus

[ https://issues.apache.org/jira/browse/KUDU-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-2244: -- Issue Type: Improvement (was: Bug) > spinlock contention in raft_consensus >

[jira] [Updated] (KUDU-2214) voting while tablet copying says "voting while tombstoned"

[ https://issues.apache.org/jira/browse/KUDU-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-2214: -- Labels: newbie (was: ) > voting while tablet copying says "voting while tombstoned" >

[jira] [Updated] (KUDU-760) Rare ThreadRestrictions shutdown CHECK failure

[ https://issues.apache.org/jira/browse/KUDU-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-760: - Priority: Trivial (was: Major) > Rare ThreadRestrictions shutdown CHECK failure >

[jira] [Resolved] (KUDU-2261) flush responses' order should match the order we call apply

[ https://issues.apache.org/jira/browse/KUDU-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2261. --- Resolution: Fixed Fix Version/s: 1.7.0 > flush responses' order should match the order we call

[jira] [Commented] (KUDU-2086) Uneven assignment of connections to Reactor threads creates skew and limits transfer throughput

[ https://issues.apache.org/jira/browse/KUDU-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331492#comment-16331492 ] Joe McDonnell commented on KUDU-2086: - [~tlipcon] Good point, this is not a blocker. I will lower the

[jira] [Resolved] (KUDU-2228) Make Messenger options configurable

[ https://issues.apache.org/jira/browse/KUDU-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2228. --- Resolution: Fixed Fix Version/s: 1.7.0 Sailesh fixed in

[jira] [Updated] (KUDU-1578) kudu-tserver should refuse service or "freeze" instead of crash when NTP loses sync

[ https://issues.apache.org/jira/browse/KUDU-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1578: -- Priority: Minor (was: Major) > kudu-tserver should refuse service or "freeze" instead of crash when NTP

[jira] [Commented] (KUDU-2011) Request-side sidecars cannot be safely destroyed on timeout

[ https://issues.apache.org/jira/browse/KUDU-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331520#comment-16331520 ] Todd Lipcon commented on KUDU-2011: --- This was reopened because of a test failure on a stress cluster. See

[jira] [Updated] (KUDU-2048) consensus: Only evict a replica is a majority is up to date

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

[jira] [Commented] (KUDU-2267) Client may see negotiation failure when talks to master followers with only self signed cert

[ https://issues.apache.org/jira/browse/KUDU-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331458#comment-16331458 ] Todd Lipcon commented on KUDU-2267: --- I believe this problem is actualy worse than just some log spew, in

[jira] [Assigned] (KUDU-2265) A non-leader master uses self-signed server TLS cert if it hasn't ever run as a leader

[ https://issues.apache.org/jira/browse/KUDU-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin reassigned KUDU-2265: --- Assignee: Alexey Serbin > A non-leader master uses self-signed server TLS cert if it hasn't

[jira] [Created] (KUDU-2268) Sync client exceptions don't show appropriate call stack

Todd Lipcon created KUDU-2268: - Summary: Sync client exceptions don't show appropriate call stack Key: KUDU-2268 URL: https://issues.apache.org/jira/browse/KUDU-2268 Project: Kudu Issue Type:

[jira] [Commented] (KUDU-2086) Uneven assignment of connections to Reactor threads creates skew and limits transfer throughput

[ https://issues.apache.org/jira/browse/KUDU-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331487#comment-16331487 ] Todd Lipcon commented on KUDU-2086: --- [~joemcdonnell] is this still a blocker? From talking with

[jira] [Commented] (KUDU-2262) Java client does not retry if no master is a leader

[ https://issues.apache.org/jira/browse/KUDU-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331493#comment-16331493 ] Todd Lipcon commented on KUDU-2262: --- Similar issue to KUDU-2267 but this one happens even without

[jira] [Updated] (KUDU-2086) Uneven assignment of connections to Reactor threads creates skew and limits transfer throughput

[ https://issues.apache.org/jira/browse/KUDU-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe McDonnell updated KUDU-2086: Priority: Critical (was: Blocker) > Uneven assignment of connections to Reactor threads creates

[jira] [Resolved] (KUDU-2249) fix client shut down prematurely in KuduTableInputFormat

[ https://issues.apache.org/jira/browse/KUDU-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2249. --- Resolution: Fixed Assignee: Clemens Valiente Fix Version/s: 1.7.0 Thanks Clemens! >

[jira] [Resolved] (KUDU-2238) Big DMS not flush under memory pressure

[ https://issues.apache.org/jira/browse/KUDU-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2238. --- Resolution: Fixed Assignee: ZhangZhen Fix Version/s: 1.7.0 Zhen put in a fix for this

[jira] [Commented] (KUDU-2226) Tablets with too many DRSs will cause a huge DMS memory overhead

[ https://issues.apache.org/jira/browse/KUDU-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331513#comment-16331513 ] Todd Lipcon commented on KUDU-2226: --- [~zhqu...@gmail.com] can you try upgrading to 1.4 or later? There

[jira] [Updated] (KUDU-2234) kudu-tool-test fails when environment has GLOG_colorlogtostderr=1

[ https://issues.apache.org/jira/browse/KUDU-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-2234: -- Labels: newbie (was: ) > kudu-tool-test fails when environment has GLOG_colorlogtostderr=1 >

[jira] [Resolved] (KUDU-2225) Cannot submit Spark 2.2 job on yarn client mode to a secure Kudu cluster

[ https://issues.apache.org/jira/browse/KUDU-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2225. --- Resolution: Not A Problem Fix Version/s: n/a > Cannot submit Spark 2.2 job on yarn client mode

[jira] [Commented] (KUDU-1762) suspected tablet memory leak

[ https://issues.apache.org/jira/browse/KUDU-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331517#comment-16331517 ] Todd Lipcon commented on KUDU-1762: --- [~cfreely][~dawn110110][~zhqu...@gmail.com] - anything to report

[jira] [Updated] (KUDU-1397) Allow building safely with custom toolchains

[ https://issues.apache.org/jira/browse/KUDU-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1397: -- Priority: Minor (was: Major) > Allow building safely with custom toolchains >

[jira] [Resolved] (KUDU-2187) Don't hold threadpool lock when creating additional workers

[ https://issues.apache.org/jira/browse/KUDU-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2187. --- Resolution: Fixed Fix Version/s: 1.6.0 Fixed thisin f5e1203a344c031e357075c900740da33f4d736e >