[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] [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] [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)
