[jira] [Commented] (KUDU-1879) Support table without a primary key
[ https://issues.apache.org/jira/browse/KUDU-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955207#comment-15955207 ] Gordon Gardiner commented on KUDU-1879: --- Related > Support table without a primary key > --- > > Key: KUDU-1879 > URL: https://issues.apache.org/jira/browse/KUDU-1879 > Project: Kudu > Issue Type: New Feature > Components: master >Affects Versions: 1.2.0 >Reporter: Amos Bird > > PK-less tables are more suitable for "bulk loading and processing" workflow. > It would be easier to implement new features for this kind of table, such as > rebalancing. We may even be able to add raw cfiles directly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KUDU-428) Support for service/table/column authorization
[ https://issues.apache.org/jira/browse/KUDU-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605121#comment-15605121 ] Gordon Gardiner commented on KUDU-428: -- Please consider integration with Sentry for authorisation. > Support for service/table/column authorization > -- > > Key: KUDU-428 > URL: https://issues.apache.org/jira/browse/KUDU-428 > Project: Kudu > Issue Type: New Feature > Components: master, security, tserver >Affects Versions: 1.2.0 >Reporter: Todd Lipcon >Priority: Critical > Labels: kudu-roadmap > > We need to support basic SQL-like access control: > - grant/revoke on tables, columns > - service-level grant/revoke > - probably need some group/role mapping infrastructure as well -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KUDU-424) Kudu CLI/shell for DDL and basic DML
[ https://issues.apache.org/jira/browse/KUDU-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605118#comment-15605118 ] Gordon Gardiner commented on KUDU-424: -- Please include support for specifying the encoding and compression options for columns when creating or altering a table. > Kudu CLI/shell for DDL and basic DML > > > Key: KUDU-424 > URL: https://issues.apache.org/jira/browse/KUDU-424 > Project: Kudu > Issue Type: New Feature > Components: client, ops-tooling >Affects Versions: M5 >Reporter: Todd Lipcon >Priority: Critical > Labels: kudu-roadmap > > Currently there is basically no way to access Kudu aside from programmatic > APIs. We need to have some simple ability to do basic tasks from the command > line: > - create/drop/alter table > - scan a table/key range > - stretch goal: insert/delete/update -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KUDU-1508) Log block manager triggers ext4 hole punching bug in el6
[ https://issues.apache.org/jira/browse/KUDU-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605072#comment-15605072 ] Gordon Gardiner commented on KUDU-1508: --- It could be several more months before RHEL 6.9 appears. I note that RHEL 6 is pretty long in the tooth. It was released in November 2010 and is in the Production 2 stage of its life cycle. https://access.redhat.com/support/policy/updates/errata Support for XFS on RHEL 6 requires an additional subscription, albeit very low cost. In RHEL 7 XFS support is included and it is the default file system. I'd be encouraging people in that direction, noting that an in place upgrade to RHEL 7 is possible but in many cases may not be an option. > Log block manager triggers ext4 hole punching bug in el6 > > > Key: KUDU-1508 > URL: https://issues.apache.org/jira/browse/KUDU-1508 > Project: Kudu > Issue Type: Bug > Components: fs >Affects Versions: 0.9.0 >Reporter: Todd Lipcon >Priority: Blocker > Attachments: e9f83e4acef3405f99d01914317351ce.metadata > > > I've experienced many times that when I reboot an el6 node that was running > Kudu tservers, fsck reports issues like: > data6 contains a file system with errors, check forced. > data6: Interior extent node level 0 of inode 5259348: > Logical start 154699 does not match logical start 2623046 at next level. > After some investigation, I've determined that this is due to an ext4 kernel > bug: https://patchwork.ozlabs.org/patch/206123/ > Details in a comment to follow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KUDU-1483) in some cases, followers cannot promote to leader.
[ https://issues.apache.org/jira/browse/KUDU-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604673#comment-15604673 ] Gordon Gardiner edited comment on KUDU-1483 at 10/25/16 8:42 AM: - We saw something like this recently on kudu 1.0.0 where for a particular tablet there were two followers and the election of a leader keeps failing. Every other tablet for that table and others has a single leader and two followers. This just keeps spamming the logs with the same kind of messages posted above. It means the table is effectively read only. Fortunately this is only a QA cluster and was just a test table with a modest amount of data. I believe the table was created under kudu 0.8 or 0.7. was (Author: gordon.gardiner1): We saw something like this recently where for a particular tablet there were two followers and the election of a leader keeps failing. Every other tablet for that table and others has a single leader and two followers. This just keeps spamming the logs with the same kind of messages posted above. It means the table is effectively read only. Fortunately this is only a QA cluster and was just a test table with a modest amount of data. I believe the table was created under kudu 0.8 or 0.7. > in some cases, followers cannot promote to leader. > -- > > Key: KUDU-1483 > URL: https://issues.apache.org/jira/browse/KUDU-1483 > Project: Kudu > Issue Type: Bug >Reporter: zhangsong > > in my env, a tablet only has two follower on master's webui, that situation > last forever. > Some logs about the tablet on two followers log: > follower1: > I0613 11:16:33.244365 26846 leader_election.cc:223] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e > [CANDIDATE]: Term 31717 election: Requesting vote from > peer 8cf59ddd6d154ae99d3b23da840169e0W0613 11:16:33.247150 26016 > leader_election.cc:281] T 87588b06c65d4898a5b8c29d08b3528d P > eded59517b14432ab9022cd50d160b8e [CANDIDATE]: Term 31717 election: Tablet > error from VoteRequest() call to peer 8cf59ddd6d154ae99d3b23da840169e0: > Illegal state: Tablet not RUN > NING: FAILED: Not found: Can't find block: 1363326557009763249I0613 > 11:16:33.247463 26016 leader_election.cc:248] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e > [CANDIDATE]: Term 31717 election: Election decided. Re > sult: candidate lost.I0613 11:16:33.248205 17534 raft_consensus.cc:1942] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Snoozing failure detection for election timeout plus an > additional 15.536s > I0613 11:16:33.248245 17534 raft_consensus.cc:1795] T > 87588b06c65d4898a5b8c29d08b3528d P > eded59517b14432ab9022cd50d160b8e [term 31717 FOLLOWER]: Leader election lost > for term 3 > 1717. Reason: None given > sult: candidate lost.I0613 11:16:33.248205 17534 raft_consensus.cc:1942] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Snoozing failure detection for election timeout plus an > additional 15.536sI0613 11:16:33.248245 17534 raft_consensus.cc:1795] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election lost for term 31717. Reason: None given > I0613 11:16:34.288436 26137 raft_consensus.cc:1298] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Handling vote request from an unknown peer > 95bc8f3637ed4a52b53a984052ba6114 > I0613 11:16:34.288633 26137 raft_consensus.cc:1558] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election vote request: Denying vote to candidate > 95bc8f3637ed4a52b53a984052ba6114 for earlier term 31666. Current term is > 31717. > I0613 11:16:41.506261 26127 raft_consensus.cc:1298] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Handling vote request from an unknown peer > 95bc8f3637ed4a52b53a984052ba6114 > I0613 11:16:41.506325 26127 raft_consensus.cc:1558] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election vote request: Denying vote to candidate > 95bc8f3637ed4a52b53a984052ba6114 for earlier term 31667. Current term is > 31717. > I0613 11:16:45.440551 26135 raft_consensus.cc:1298] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Handling vote request from an unknown peer > 95bc8f3637ed4a52b53a984052ba6114 > I0613 11:16:45.440625 26135 raft_consensus.cc:1558] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election vote request: Denying vote to candidate >
[jira] [Commented] (KUDU-1483) in some cases, followers cannot promote to leader.
[ https://issues.apache.org/jira/browse/KUDU-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604673#comment-15604673 ] Gordon Gardiner commented on KUDU-1483: --- We saw something like this recently where for a particular tablet there were two followers and the election of a leader keeps failing. Every other tablet for that table and others has a single leader and two followers. This just keeps spamming the logs with the same kind of messages posted above. It means the table is effectively read only. Fortunately this is only a QA cluster and was just a test table with a modest amount of data. I believe the table was created under kudu 0.8 or 0.7. > in some cases, followers cannot promote to leader. > -- > > Key: KUDU-1483 > URL: https://issues.apache.org/jira/browse/KUDU-1483 > Project: Kudu > Issue Type: Bug >Reporter: zhangsong > > in my env, a tablet only has two follower on master's webui, that situation > last forever. > Some logs about the tablet on two followers log: > follower1: > I0613 11:16:33.244365 26846 leader_election.cc:223] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e > [CANDIDATE]: Term 31717 election: Requesting vote from > peer 8cf59ddd6d154ae99d3b23da840169e0W0613 11:16:33.247150 26016 > leader_election.cc:281] T 87588b06c65d4898a5b8c29d08b3528d P > eded59517b14432ab9022cd50d160b8e [CANDIDATE]: Term 31717 election: Tablet > error from VoteRequest() call to peer 8cf59ddd6d154ae99d3b23da840169e0: > Illegal state: Tablet not RUN > NING: FAILED: Not found: Can't find block: 1363326557009763249I0613 > 11:16:33.247463 26016 leader_election.cc:248] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e > [CANDIDATE]: Term 31717 election: Election decided. Re > sult: candidate lost.I0613 11:16:33.248205 17534 raft_consensus.cc:1942] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Snoozing failure detection for election timeout plus an > additional 15.536s > I0613 11:16:33.248245 17534 raft_consensus.cc:1795] T > 87588b06c65d4898a5b8c29d08b3528d P > eded59517b14432ab9022cd50d160b8e [term 31717 FOLLOWER]: Leader election lost > for term 3 > 1717. Reason: None given > sult: candidate lost.I0613 11:16:33.248205 17534 raft_consensus.cc:1942] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Snoozing failure detection for election timeout plus an > additional 15.536sI0613 11:16:33.248245 17534 raft_consensus.cc:1795] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election lost for term 31717. Reason: None given > I0613 11:16:34.288436 26137 raft_consensus.cc:1298] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Handling vote request from an unknown peer > 95bc8f3637ed4a52b53a984052ba6114 > I0613 11:16:34.288633 26137 raft_consensus.cc:1558] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election vote request: Denying vote to candidate > 95bc8f3637ed4a52b53a984052ba6114 for earlier term 31666. Current term is > 31717. > I0613 11:16:41.506261 26127 raft_consensus.cc:1298] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Handling vote request from an unknown peer > 95bc8f3637ed4a52b53a984052ba6114 > I0613 11:16:41.506325 26127 raft_consensus.cc:1558] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election vote request: Denying vote to candidate > 95bc8f3637ed4a52b53a984052ba6114 for earlier term 31667. Current term is > 31717. > I0613 11:16:45.440551 26135 raft_consensus.cc:1298] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Handling vote request from an unknown peer > 95bc8f3637ed4a52b53a984052ba6114 > I0613 11:16:45.440625 26135 raft_consensus.cc:1558] T > 87588b06c65d4898a5b8c29d08b3528d P eded59517b14432ab9022cd50d160b8e [term > 31717 FOLLOWER]: Leader election vote request: Denying vote to candidate > 95bc8f3637ed4a52b53a984052ba6114 for earlier term 31668. Current term is > 31717. > it seems that there are three follower/voters and one of it has tablet in > "not running" state. > on the other follower: > W0613 11:16:45.437863 18782 leader_election.cc:281] T > 87588b06c65d4898a5b8c29d08b3528d P 95bc8f3637ed4a52b53a984052ba6114 > [CANDIDATE]: Term 31668 election: Tablet error from VoteRequest() call to > peer 8cf59ddd6d154ae99d3b23da840169e0: Illegal state: Tablet not RUNNING: > FAILED: Not found: Can't find block: 1363326557009763249 > W0613 11:16:45.438611 18782 leader_election.cc:333] T >
