[jira] [Created] (KUDU-2143) i want't upgrade impala ,how can i select lzo table,my impala version is 2.3
qinzl_1 created KUDU-2143: - Summary: i want't upgrade impala ,how can i select lzo table,my impala version is 2.3 Key: KUDU-2143 URL: https://issues.apache.org/jira/browse/KUDU-2143 Project: Kudu Issue Type: New Feature Reporter: qinzl_1 Error loading impala-lzo library. Check that the impala-lzo library is at version 2.3.0-IMPALA_KUDU-cdh5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KUDU-2451) kudu scaner performance is lowly
[ https://issues.apache.org/jira/browse/KUDU-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486636#comment-16486636 ] qinzl_1 commented on KUDU-2451: --- impala use Peak Mem is allway very low，and the proformence is very bad > kudu scaner performance is lowly > > > Key: KUDU-2451 > URL: https://issues.apache.org/jira/browse/KUDU-2451 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > > i use impala search kudu table it scaner performance is lowly 。Per-Host > Resources: mem-estimate=10 MB -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KUDU-2451) kudu scaner performance is lowly
qinzl_1 created KUDU-2451: - Summary: kudu scaner performance is lowly Key: KUDU-2451 URL: https://issues.apache.org/jira/browse/KUDU-2451 Project: Kudu Issue Type: Bug Reporter: qinzl_1 i use impala search kudu table it scaner performance is lowly 。Per-Host Resources: mem-estimate=10 MB -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727266#comment-16727266 ] qinzl_1 commented on KUDU-2646: --- @jiaqiyang close tserver log if have effect on kudu，and do you just close tserver log ，what about master log > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2646: -- Attachment: kudu-tserver (1).INFO.gz > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do > not have any especial config. when i restart the server, it can not offer > service.i found all tablet server is INITIALIZED , and it spend a long time > to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2646: -- Description: [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is INITIALIZED , and it spend a long time to change to RUNNING (was: i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is INITIALIZED , and it spend a long time to change to RUNNING) > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2646: -- Description: i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is INITIALIZED , and it spend a long time to change to (was: i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is ) > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > > i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do > not have any especial config. when i restart the server, it can not offer > service.i found all tablet server is INITIALIZED , and it spend a long time > to change to -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2646: -- Description: i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is INITIALIZED , and it spend a long time to change to RUNNING (was: i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is INITIALIZED , and it spend a long time to change to ) > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > > i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do > not have any especial config. when i restart the server, it can not offer > service.i found all tablet server is INITIALIZED , and it spend a long time > to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2646: -- Description: i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do not have any especial config. when i restart the server, it can not offer service.i found all tablet server is > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > > i install kudu from cloudera manager ,i have 3 master and 4 tablet server .do > not have any especial config. when i restart the server, it can not offer > service.i found all tablet server is -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 reopened KUDU-2646: --- [^kudu-tserver (1).INFO.gz] > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KUDU-2649) can not create table in impala
[ https://issues.apache.org/jira/browse/KUDU-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729559#comment-16729559 ] qinzl_1 commented on KUDU-2649: --- when i delete the table in command line , in the ui the table still there !1.jpg! > can not create table in impala > -- > > Key: KUDU-2649 > URL: https://issues.apache.org/jira/browse/KUDU-2649 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Attachments: 1.jpg > > > ERROR: ImpalaRuntimeException: Error creating Kudu table > 'impala::kudu_yxy_ods.renew_realtime_log' > CAUSED BY: NonRecoverableException: too many attempts: > KuduRpc(method=IsCreateTableDone, tablet=null, attempt=105, > DeadlineTracker(timeout=18, elapsed=179305), Traces: [0ms] sending RPC to > server master-serverA1:7051, [7ms] received from server master-serverA1:7051 > response OK, [20ms] sending RPC to server master-serverA1:7051, [20ms] > received from server master-serverA1:7051 response OK, [40ms] sending RPC to > server master-serverA1:7051, [40ms] received from server master-serverA1:7051 > response OK, [59ms] sending RPC to server master-serverA1:7051, [60ms] > received from server master-serverA1:7051 response OK, [80ms] sending RPC to > server master-serverA1:7051, [80ms] received from server master-serverA1:7051 > response OK, [100ms] sending RPC to server master-serverA1:7051, [100ms] > received from server master-serverA1:7051 response OK, [139ms] sending RPC to > server master-serverA1:7051, [140ms] received from server > master-serverA1:7051 response OK, [260ms] sending RPC to server > master-serverA1:7051, [260ms] received from server master-serverA1:7051 > response OK, [439ms] sending RPC to server master-serverA1:7051, [440ms] > received from server master-serverA1:7051 response OK, [960ms] sending RPC to > server master-serverA1:7051, [960ms] received from server > master-serverA1:7051 response OK, [1800ms] sending RPC to server > master-serverA1:7051, [1801ms] received from server master-serverA1:7051 > response OK, [3140ms] sending RPC to server master-serverA1:7051, [3140ms] > received from server master-serverA1:7051 response OK, [4159ms] sending RPC > to server master-serverA1:7051, [4160ms] received from server > master-serverA1:7051 response OK, [7400ms] sending RPC to server > master-serverA1:7051, [7400ms] received from server master-serverA1:7051 > response OK, [7820ms] sending RPC to server master-serverA1:7051, [7821ms] > received from server master-serverA1:7051 response OK, [9820ms] sending RPC > to server master-serverA1:7051, [9820ms] received from server > master-serverA1:7051 response OK, [10640ms] sending RPC to server > master-serverA1:7051, [10641ms] received from server master-serverA1:7051 > response OK, [10839ms] sending RPC to server master-serverA1:7051, [10840ms] > received from server master-serverA1:7051 response OK, [12439ms] sending RPC > to server master-serverA1:7051, [12440ms] received from server > master-serverA1:7051 response OK, [12980ms] sending RPC to server > master-serverA1:7051, [12981ms] received from server master-serverA1:7051 > response OK, [15979ms] sending RPC to server master-serverA1:7051, [15980ms] > received from server master-serverA1:7051 response OK, [19160ms] sending RPC > to server master-serverA1:7051, [19161ms] received from server > master-serverA1:7051 response OK, [22540ms] sending RPC to server > master-serverA1:7051, [22540ms] received from server master-serverA1:7051 > response OK, [24680ms] sending RPC to server master-serverA1:7051, [24680ms] > received from server master-serverA1:7051 response OK, [26759ms] sending RPC > to server master-serverA1:7051, [26760ms] received from server > master-serverA1:7051 response OK, [30779ms] sending RPC to server > master-serverA1:7051, [30780ms] received from server master-serverA1:7051 > response OK, [31879ms] sending RPC to server master-serverA1:7051, [31880ms] > received from server master-serverA1:7051 response OK, [33039ms] sending RPC > to server master-serverA1:7051, [33040ms] received from server > master-serverA1:7051 response OK, [34739ms] sending RPC to server > master-serverA1:7051, [34740ms] received from server master-serverA1:7051 > response OK, [35160ms] sending RPC to server master-serverA1:7051, [35160ms] > received from server master-serverA1:7051 response OK, [35740ms] sending RPC > to server master-serverA1:7051, [35740ms] received from server > master-serverA1:7051 response OK, [37680ms] sending RPC to server > master-serverA1:7051, [37680ms] received from server master-serverA1:7051 > response OK, [41499ms] sending RPC to server master-serverA1:7051, [41500ms] > received from server master-serverA1:7051 response OK, [44720ms] sending RPC > to server master-serverA1:7051,
[jira] [Commented] (KUDU-2649) can not create table in impala
[ https://issues.apache.org/jira/browse/KUDU-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729560#comment-16729560 ] qinzl_1 commented on KUDU-2649: --- !2.jpg! > can not create table in impala > -- > > Key: KUDU-2649 > URL: https://issues.apache.org/jira/browse/KUDU-2649 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Attachments: 1.jpg, 2.jpg > > > ERROR: ImpalaRuntimeException: Error creating Kudu table > 'impala::kudu_yxy_ods.renew_realtime_log' > CAUSED BY: NonRecoverableException: too many attempts: > KuduRpc(method=IsCreateTableDone, tablet=null, attempt=105, > DeadlineTracker(timeout=18, elapsed=179305), Traces: [0ms] sending RPC to > server master-serverA1:7051, [7ms] received from server master-serverA1:7051 > response OK, [20ms] sending RPC to server master-serverA1:7051, [20ms] > received from server master-serverA1:7051 response OK, [40ms] sending RPC to > server master-serverA1:7051, [40ms] received from server master-serverA1:7051 > response OK, [59ms] sending RPC to server master-serverA1:7051, [60ms] > received from server master-serverA1:7051 response OK, [80ms] sending RPC to > server master-serverA1:7051, [80ms] received from server master-serverA1:7051 > response OK, [100ms] sending RPC to server master-serverA1:7051, [100ms] > received from server master-serverA1:7051 response OK, [139ms] sending RPC to > server master-serverA1:7051, [140ms] received from server > master-serverA1:7051 response OK, [260ms] sending RPC to server > master-serverA1:7051, [260ms] received from server master-serverA1:7051 > response OK, [439ms] sending RPC to server master-serverA1:7051, [440ms] > received from server master-serverA1:7051 response OK, [960ms] sending RPC to > server master-serverA1:7051, [960ms] received from server > master-serverA1:7051 response OK, [1800ms] sending RPC to server > master-serverA1:7051, [1801ms] received from server master-serverA1:7051 > response OK, [3140ms] sending RPC to server master-serverA1:7051, [3140ms] > received from server master-serverA1:7051 response OK, [4159ms] sending RPC > to server master-serverA1:7051, [4160ms] received from server > master-serverA1:7051 response OK, [7400ms] sending RPC to server > master-serverA1:7051, [7400ms] received from server master-serverA1:7051 > response OK, [7820ms] sending RPC to server master-serverA1:7051, [7821ms] > received from server master-serverA1:7051 response OK, [9820ms] sending RPC > to server master-serverA1:7051, [9820ms] received from server > master-serverA1:7051 response OK, [10640ms] sending RPC to server > master-serverA1:7051, [10641ms] received from server master-serverA1:7051 > response OK, [10839ms] sending RPC to server master-serverA1:7051, [10840ms] > received from server master-serverA1:7051 response OK, [12439ms] sending RPC > to server master-serverA1:7051, [12440ms] received from server > master-serverA1:7051 response OK, [12980ms] sending RPC to server > master-serverA1:7051, [12981ms] received from server master-serverA1:7051 > response OK, [15979ms] sending RPC to server master-serverA1:7051, [15980ms] > received from server master-serverA1:7051 response OK, [19160ms] sending RPC > to server master-serverA1:7051, [19161ms] received from server > master-serverA1:7051 response OK, [22540ms] sending RPC to server > master-serverA1:7051, [22540ms] received from server master-serverA1:7051 > response OK, [24680ms] sending RPC to server master-serverA1:7051, [24680ms] > received from server master-serverA1:7051 response OK, [26759ms] sending RPC > to server master-serverA1:7051, [26760ms] received from server > master-serverA1:7051 response OK, [30779ms] sending RPC to server > master-serverA1:7051, [30780ms] received from server master-serverA1:7051 > response OK, [31879ms] sending RPC to server master-serverA1:7051, [31880ms] > received from server master-serverA1:7051 response OK, [33039ms] sending RPC > to server master-serverA1:7051, [33040ms] received from server > master-serverA1:7051 response OK, [34739ms] sending RPC to server > master-serverA1:7051, [34740ms] received from server master-serverA1:7051 > response OK, [35160ms] sending RPC to server master-serverA1:7051, [35160ms] > received from server master-serverA1:7051 response OK, [35740ms] sending RPC > to server master-serverA1:7051, [35740ms] received from server > master-serverA1:7051 response OK, [37680ms] sending RPC to server > master-serverA1:7051, [37680ms] received from server master-serverA1:7051 > response OK, [41499ms] sending RPC to server master-serverA1:7051, [41500ms] > received from server master-serverA1:7051 response OK, [44720ms] sending RPC > to server master-serverA1:7051, [44720ms] received from server > master-serverA1:7051 response OK,
[jira] [Commented] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729519#comment-16729519 ] qinzl_1 commented on KUDU-2646: --- [~helifu] the 6 disk configure RAID 0 ,so i can only one dir > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729522#comment-16729522 ] qinzl_1 commented on KUDU-2646: --- [~jiaqiyang] kudu tserver set_flag x.x.x.x:7050 --num_tablets_to_open_simultaneously 4 -force Invalid argument: must provide positional argument flag how to configure whit command > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729522#comment-16729522 ] qinzl_1 edited comment on KUDU-2646 at 12/27/18 10:45 AM: -- [~jiaqiyang] kudu tserver set_flag x.x.x.x:7050 --num_tablets_to_open_simultaneously 4 -force Invalid argument: must provide positional argument flag how to excu whit command was (Author: qinzl_1): [~jiaqiyang] kudu tserver set_flag x.x.x.x:7050 --num_tablets_to_open_simultaneously 4 -force Invalid argument: must provide positional argument flag how to configure whit command > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729519#comment-16729519 ] qinzl_1 edited comment on KUDU-2646 at 12/27/18 11:11 AM: -- [~helifu] the 6 disk configure RAID 0 ,so it show only one dir was (Author: qinzl_1): [~helifu] the 6 disk configure RAID 0 ,so i can only one dir > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2649) can not create table in impala
[ https://issues.apache.org/jira/browse/KUDU-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2649: -- Attachment: 1.jpg > can not create table in impala > -- > > Key: KUDU-2649 > URL: https://issues.apache.org/jira/browse/KUDU-2649 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Attachments: 1.jpg > > > ERROR: ImpalaRuntimeException: Error creating Kudu table > 'impala::kudu_yxy_ods.renew_realtime_log' > CAUSED BY: NonRecoverableException: too many attempts: > KuduRpc(method=IsCreateTableDone, tablet=null, attempt=105, > DeadlineTracker(timeout=18, elapsed=179305), Traces: [0ms] sending RPC to > server master-serverA1:7051, [7ms] received from server master-serverA1:7051 > response OK, [20ms] sending RPC to server master-serverA1:7051, [20ms] > received from server master-serverA1:7051 response OK, [40ms] sending RPC to > server master-serverA1:7051, [40ms] received from server master-serverA1:7051 > response OK, [59ms] sending RPC to server master-serverA1:7051, [60ms] > received from server master-serverA1:7051 response OK, [80ms] sending RPC to > server master-serverA1:7051, [80ms] received from server master-serverA1:7051 > response OK, [100ms] sending RPC to server master-serverA1:7051, [100ms] > received from server master-serverA1:7051 response OK, [139ms] sending RPC to > server master-serverA1:7051, [140ms] received from server > master-serverA1:7051 response OK, [260ms] sending RPC to server > master-serverA1:7051, [260ms] received from server master-serverA1:7051 > response OK, [439ms] sending RPC to server master-serverA1:7051, [440ms] > received from server master-serverA1:7051 response OK, [960ms] sending RPC to > server master-serverA1:7051, [960ms] received from server > master-serverA1:7051 response OK, [1800ms] sending RPC to server > master-serverA1:7051, [1801ms] received from server master-serverA1:7051 > response OK, [3140ms] sending RPC to server master-serverA1:7051, [3140ms] > received from server master-serverA1:7051 response OK, [4159ms] sending RPC > to server master-serverA1:7051, [4160ms] received from server > master-serverA1:7051 response OK, [7400ms] sending RPC to server > master-serverA1:7051, [7400ms] received from server master-serverA1:7051 > response OK, [7820ms] sending RPC to server master-serverA1:7051, [7821ms] > received from server master-serverA1:7051 response OK, [9820ms] sending RPC > to server master-serverA1:7051, [9820ms] received from server > master-serverA1:7051 response OK, [10640ms] sending RPC to server > master-serverA1:7051, [10641ms] received from server master-serverA1:7051 > response OK, [10839ms] sending RPC to server master-serverA1:7051, [10840ms] > received from server master-serverA1:7051 response OK, [12439ms] sending RPC > to server master-serverA1:7051, [12440ms] received from server > master-serverA1:7051 response OK, [12980ms] sending RPC to server > master-serverA1:7051, [12981ms] received from server master-serverA1:7051 > response OK, [15979ms] sending RPC to server master-serverA1:7051, [15980ms] > received from server master-serverA1:7051 response OK, [19160ms] sending RPC > to server master-serverA1:7051, [19161ms] received from server > master-serverA1:7051 response OK, [22540ms] sending RPC to server > master-serverA1:7051, [22540ms] received from server master-serverA1:7051 > response OK, [24680ms] sending RPC to server master-serverA1:7051, [24680ms] > received from server master-serverA1:7051 response OK, [26759ms] sending RPC > to server master-serverA1:7051, [26760ms] received from server > master-serverA1:7051 response OK, [30779ms] sending RPC to server > master-serverA1:7051, [30780ms] received from server master-serverA1:7051 > response OK, [31879ms] sending RPC to server master-serverA1:7051, [31880ms] > received from server master-serverA1:7051 response OK, [33039ms] sending RPC > to server master-serverA1:7051, [33040ms] received from server > master-serverA1:7051 response OK, [34739ms] sending RPC to server > master-serverA1:7051, [34740ms] received from server master-serverA1:7051 > response OK, [35160ms] sending RPC to server master-serverA1:7051, [35160ms] > received from server master-serverA1:7051 response OK, [35740ms] sending RPC > to server master-serverA1:7051, [35740ms] received from server > master-serverA1:7051 response OK, [37680ms] sending RPC to server > master-serverA1:7051, [37680ms] received from server master-serverA1:7051 > response OK, [41499ms] sending RPC to server master-serverA1:7051, [41500ms] > received from server master-serverA1:7051 response OK, [44720ms] sending RPC > to server master-serverA1:7051, [44720ms] received from server > master-serverA1:7051 response OK, [46519ms] sending RPC to server >
[jira] [Updated] (KUDU-2649) can not create table in impala
[ https://issues.apache.org/jira/browse/KUDU-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qinzl_1 updated KUDU-2649: -- Attachment: 2.jpg > can not create table in impala > -- > > Key: KUDU-2649 > URL: https://issues.apache.org/jira/browse/KUDU-2649 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Attachments: 1.jpg, 2.jpg > > > ERROR: ImpalaRuntimeException: Error creating Kudu table > 'impala::kudu_yxy_ods.renew_realtime_log' > CAUSED BY: NonRecoverableException: too many attempts: > KuduRpc(method=IsCreateTableDone, tablet=null, attempt=105, > DeadlineTracker(timeout=18, elapsed=179305), Traces: [0ms] sending RPC to > server master-serverA1:7051, [7ms] received from server master-serverA1:7051 > response OK, [20ms] sending RPC to server master-serverA1:7051, [20ms] > received from server master-serverA1:7051 response OK, [40ms] sending RPC to > server master-serverA1:7051, [40ms] received from server master-serverA1:7051 > response OK, [59ms] sending RPC to server master-serverA1:7051, [60ms] > received from server master-serverA1:7051 response OK, [80ms] sending RPC to > server master-serverA1:7051, [80ms] received from server master-serverA1:7051 > response OK, [100ms] sending RPC to server master-serverA1:7051, [100ms] > received from server master-serverA1:7051 response OK, [139ms] sending RPC to > server master-serverA1:7051, [140ms] received from server > master-serverA1:7051 response OK, [260ms] sending RPC to server > master-serverA1:7051, [260ms] received from server master-serverA1:7051 > response OK, [439ms] sending RPC to server master-serverA1:7051, [440ms] > received from server master-serverA1:7051 response OK, [960ms] sending RPC to > server master-serverA1:7051, [960ms] received from server > master-serverA1:7051 response OK, [1800ms] sending RPC to server > master-serverA1:7051, [1801ms] received from server master-serverA1:7051 > response OK, [3140ms] sending RPC to server master-serverA1:7051, [3140ms] > received from server master-serverA1:7051 response OK, [4159ms] sending RPC > to server master-serverA1:7051, [4160ms] received from server > master-serverA1:7051 response OK, [7400ms] sending RPC to server > master-serverA1:7051, [7400ms] received from server master-serverA1:7051 > response OK, [7820ms] sending RPC to server master-serverA1:7051, [7821ms] > received from server master-serverA1:7051 response OK, [9820ms] sending RPC > to server master-serverA1:7051, [9820ms] received from server > master-serverA1:7051 response OK, [10640ms] sending RPC to server > master-serverA1:7051, [10641ms] received from server master-serverA1:7051 > response OK, [10839ms] sending RPC to server master-serverA1:7051, [10840ms] > received from server master-serverA1:7051 response OK, [12439ms] sending RPC > to server master-serverA1:7051, [12440ms] received from server > master-serverA1:7051 response OK, [12980ms] sending RPC to server > master-serverA1:7051, [12981ms] received from server master-serverA1:7051 > response OK, [15979ms] sending RPC to server master-serverA1:7051, [15980ms] > received from server master-serverA1:7051 response OK, [19160ms] sending RPC > to server master-serverA1:7051, [19161ms] received from server > master-serverA1:7051 response OK, [22540ms] sending RPC to server > master-serverA1:7051, [22540ms] received from server master-serverA1:7051 > response OK, [24680ms] sending RPC to server master-serverA1:7051, [24680ms] > received from server master-serverA1:7051 response OK, [26759ms] sending RPC > to server master-serverA1:7051, [26760ms] received from server > master-serverA1:7051 response OK, [30779ms] sending RPC to server > master-serverA1:7051, [30780ms] received from server master-serverA1:7051 > response OK, [31879ms] sending RPC to server master-serverA1:7051, [31880ms] > received from server master-serverA1:7051 response OK, [33039ms] sending RPC > to server master-serverA1:7051, [33040ms] received from server > master-serverA1:7051 response OK, [34739ms] sending RPC to server > master-serverA1:7051, [34740ms] received from server master-serverA1:7051 > response OK, [35160ms] sending RPC to server master-serverA1:7051, [35160ms] > received from server master-serverA1:7051 response OK, [35740ms] sending RPC > to server master-serverA1:7051, [35740ms] received from server > master-serverA1:7051 response OK, [37680ms] sending RPC to server > master-serverA1:7051, [37680ms] received from server master-serverA1:7051 > response OK, [41499ms] sending RPC to server master-serverA1:7051, [41500ms] > received from server master-serverA1:7051 response OK, [44720ms] sending RPC > to server master-serverA1:7051, [44720ms] received from server > master-serverA1:7051 response OK, [46519ms] sending RPC to server
[jira] [Commented] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
[ https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729445#comment-16729445 ] qinzl_1 commented on KUDU-2646: --- [~jiaqiyang] in my system i have 6 data disk for RAID 0,how configure num_tablets_to_open_simultaneously for my system > kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few > days > - > > Key: KUDU-2646 > URL: https://issues.apache.org/jira/browse/KUDU-2646 > Project: Kudu > Issue Type: Bug >Reporter: qinzl_1 >Priority: Major > Fix For: n/a > > Attachments: kudu-tserver (1).INFO.gz > > > [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3 > master and 4 tablet server .do not have any especial config. when i restart > the server, it can not offer service.i found all tablet server is INITIALIZED > , and it spend a long time to change to RUNNING -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KUDU-2649) can not create table in impala
qinzl_1 created KUDU-2649: - Summary: can not create table in impala Key: KUDU-2649 URL: https://issues.apache.org/jira/browse/KUDU-2649 Project: Kudu Issue Type: Bug Reporter: qinzl_1 ERROR: ImpalaRuntimeException: Error creating Kudu table 'impala::kudu_yxy_ods.renew_realtime_log' CAUSED BY: NonRecoverableException: too many attempts: KuduRpc(method=IsCreateTableDone, tablet=null, attempt=105, DeadlineTracker(timeout=18, elapsed=179305), Traces: [0ms] sending RPC to server master-serverA1:7051, [7ms] received from server master-serverA1:7051 response OK, [20ms] sending RPC to server master-serverA1:7051, [20ms] received from server master-serverA1:7051 response OK, [40ms] sending RPC to server master-serverA1:7051, [40ms] received from server master-serverA1:7051 response OK, [59ms] sending RPC to server master-serverA1:7051, [60ms] received from server master-serverA1:7051 response OK, [80ms] sending RPC to server master-serverA1:7051, [80ms] received from server master-serverA1:7051 response OK, [100ms] sending RPC to server master-serverA1:7051, [100ms] received from server master-serverA1:7051 response OK, [139ms] sending RPC to server master-serverA1:7051, [140ms] received from server master-serverA1:7051 response OK, [260ms] sending RPC to server master-serverA1:7051, [260ms] received from server master-serverA1:7051 response OK, [439ms] sending RPC to server master-serverA1:7051, [440ms] received from server master-serverA1:7051 response OK, [960ms] sending RPC to server master-serverA1:7051, [960ms] received from server master-serverA1:7051 response OK, [1800ms] sending RPC to server master-serverA1:7051, [1801ms] received from server master-serverA1:7051 response OK, [3140ms] sending RPC to server master-serverA1:7051, [3140ms] received from server master-serverA1:7051 response OK, [4159ms] sending RPC to server master-serverA1:7051, [4160ms] received from server master-serverA1:7051 response OK, [7400ms] sending RPC to server master-serverA1:7051, [7400ms] received from server master-serverA1:7051 response OK, [7820ms] sending RPC to server master-serverA1:7051, [7821ms] received from server master-serverA1:7051 response OK, [9820ms] sending RPC to server master-serverA1:7051, [9820ms] received from server master-serverA1:7051 response OK, [10640ms] sending RPC to server master-serverA1:7051, [10641ms] received from server master-serverA1:7051 response OK, [10839ms] sending RPC to server master-serverA1:7051, [10840ms] received from server master-serverA1:7051 response OK, [12439ms] sending RPC to server master-serverA1:7051, [12440ms] received from server master-serverA1:7051 response OK, [12980ms] sending RPC to server master-serverA1:7051, [12981ms] received from server master-serverA1:7051 response OK, [15979ms] sending RPC to server master-serverA1:7051, [15980ms] received from server master-serverA1:7051 response OK, [19160ms] sending RPC to server master-serverA1:7051, [19161ms] received from server master-serverA1:7051 response OK, [22540ms] sending RPC to server master-serverA1:7051, [22540ms] received from server master-serverA1:7051 response OK, [24680ms] sending RPC to server master-serverA1:7051, [24680ms] received from server master-serverA1:7051 response OK, [26759ms] sending RPC to server master-serverA1:7051, [26760ms] received from server master-serverA1:7051 response OK, [30779ms] sending RPC to server master-serverA1:7051, [30780ms] received from server master-serverA1:7051 response OK, [31879ms] sending RPC to server master-serverA1:7051, [31880ms] received from server master-serverA1:7051 response OK, [33039ms] sending RPC to server master-serverA1:7051, [33040ms] received from server master-serverA1:7051 response OK, [34739ms] sending RPC to server master-serverA1:7051, [34740ms] received from server master-serverA1:7051 response OK, [35160ms] sending RPC to server master-serverA1:7051, [35160ms] received from server master-serverA1:7051 response OK, [35740ms] sending RPC to server master-serverA1:7051, [35740ms] received from server master-serverA1:7051 response OK, [37680ms] sending RPC to server master-serverA1:7051, [37680ms] received from server master-serverA1:7051 response OK, [41499ms] sending RPC to server master-serverA1:7051, [41500ms] received from server master-serverA1:7051 response OK, [44720ms] sending RPC to server master-serverA1:7051, [44720ms] received from server master-serverA1:7051 response OK, [46519ms] sending RPC to server master-serverA1:7051, [46520ms] received from server master-serverA1:7051 response OK, [46879ms] sending RPC to server master-serverA1:7051, [46880ms] received from server master-serverA1:7051 response OK, [47580ms] sending RPC to server master-serverA1:7051, [47580ms] received from server master-serverA1:7051 response OK, [49560ms] sending RPC to
[jira] [Created] (KUDU-2647) client connection to *:7051 recv error: Network error: failed to read from TLS socket: Connection reset by peer (error 104)
qinzl_1 created KUDU-2647: - Summary: client connection to *:7051 recv error: Network error: failed to read from TLS socket: Connection reset by peer (error 104) Key: KUDU-2647 URL: https://issues.apache.org/jira/browse/KUDU-2647 Project: Kudu Issue Type: Bug Reporter: qinzl_1 i did not open any TLS/SSL config.why have this error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KUDU-2650) cloudera manager can not add kudu master role
qinzl_1 created KUDU-2650: - Summary: cloudera manager can not add kudu master role Key: KUDU-2650 URL: https://issues.apache.org/jira/browse/KUDU-2650 Project: Kudu Issue Type: Bug Reporter: qinzl_1 when i add kucu master role in cloudera manager ,can not start kudu master role Unable to init master catalog manager: Invalid argument: Unable to initialize catalog manager: Failed to initialize sys tables async: on-disk master list (serverA1:7051, serverA2:7051, serverA3:7051, shyt-dz-12-bigdata-200-23:7051) and provided master list (serverA1:7051, serverA2:7051, serverA3:7051) differ. Their symmetric difference is: shyt-dz-12-bigdata-200-23:7051 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KUDU-2646) kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days
qinzl_1 created KUDU-2646: - Summary: kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few days Key: KUDU-2646 URL: https://issues.apache.org/jira/browse/KUDU-2646 Project: Kudu Issue Type: Bug Reporter: qinzl_1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
