kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "冯宝利" <fengba...@uce.cn>
Subject 回复: Re: kuduissue!
Date Tue, 12 Mar 2019 00:09:37 GMT
My kudu version is 1.8.0.I think the problem that is impala issued .When I created the kudu
table with impala, I found that the tablet of the newly created kudu table was in the initialization
state.------------------------------------------------------------------
发件人:William Berkeley<wdberkeley@cloudera.com>
日 期:2019年03月12日 05:46:07
收件人:<user@kudu.apache.org>
抄 送:Attila Bukor<abukor@apache.org>
主 题:Re: Re: kuduissue!

What Kudu version are you running? The master logs would be useful here, otherwise we can't
understand why the table took so long to create.

I'm not sure what timeout to set as that is an Impala configuration, not a Kudu one. You want
the configuration that changes the default Kudu operation timeout for DDL operations issued
by Impala.

-Will
On Thu, Mar 7, 2019 at 5:37 PM fengbaoli@uce.cn <fengbaoli@uce.cn> wrote:

This table partitions  is 32  ,the master logs has been deleted.
 I want to know which timeout parameter is. I want to modify this timeout parameter to see
if it can solve this problem.Because my kudu cluster is small, but the tablet format is already
very large


  thanks!


优速物流科技有限公司
大数据中心     冯宝利
Mobil:15050552430
Email:fengbaoli@uce.cn 
发件人: Attila Bukor
发送时间: 2019-03-07 18:24
收件人: fengbaoli@uce.cn
抄送: user
主题: Re: kuduissue!
Hi,
From Impala 2.12 it's not allowed to set the kudu.table_name explicity
on CREATE TABLE[1], so that part is expected.
It's interesting that the table creation times out though. How many
partitions does the table have? Can you share the master logs with us
from the relevant time period?
Thanks,
Attila
[1] https://issues.apache.org/jira/browse/IMPALA-5654
On Thu, Mar 07, 2019 at 06:19:05PM +0800, fengbaoli@uce.cn wrote:
> Hi:
>    When I upgraded from cm 5.14.0 to cm 6.1.0, there was a problem that I failed to create
kudu tables using imapla. The specific impala client's error was as follows:
> ERROR: ImpalaRuntimeException: Error creating Kudu table 'impala::tmp_kudu.t_prs_acc_bill_prep'
> CAUSED BY: NonRecoverableException: can not complete before timeout: KuduRpc(method=IsCreateTableDone,
tablet=null, attempt=95, DeadlineTracker(timeout=180000, elapsed=178986), Traces: [0ms] sending
RPC to server master-hadoop2.uce.cn:7051, [0ms] received from server master-hadoop2.uce.cn:7051
response OK, [20ms] sending RPC to server master-hadoop2.uce.cn:7051, [20ms] received from
server master-hadoop2.uce.cn:7051 response OK, [40ms] sending RPC to server master-hadoop2.uce.cn:7051,
[41ms] received from server master-hadoop2.uce.cn:7051 response OK, [59ms] sending RPC to
server master-hadoop2.uce.cn:7051, [60ms] received from server master-hadoop2.uce.cn:7051
response OK, [80ms] sending RPC to server master-hadoop2.uce.cn:7051, [80ms] received from
server master-hadoop2.uce.cn:7051 response OK, [120ms] sending RPC to server master-hadoop2.uce.cn:7051,
[121ms] received from server master-hadoop2.uce.cn:7051 response OK, [180ms] sending RPC to
server master-hadoop2.uce.cn:7051, [180ms] received from server master-hadoop2.uce.cn:7051
response OK, [260ms] sending RPC to server master-hadoop2.uce.cn:7051, [261ms] received from
server master-hadoop2.uce.cn:7051 response OK, [440ms] sending RPC to server master-hadoop2.uce.cn:7051,
[489ms] received from server master-hadoop2.uce.cn:7051 response OK, [580ms] sending RPC to
server master-hadoop2.uce.cn:7051, [580ms] received from server master-hadoop2.uce.cn:7051
response OK, [980ms] sending RPC to server master-hadoop2.uce.cn:7051, [981ms] received from
server master-hadoop2.uce.cn:7051 response OK, [1300ms] sending RPC to server master-hadoop2.uce.cn:7051,
[1301ms] received from server master-hadoop2.uce.cn:7051 response OK, [2260ms] sending RPC
to server master-hadoop2.uce.cn:7051, [2261ms] received from server master-hadoop2.uce.cn:7051
response OK, [6240ms] sending RPC to server master-hadoop2.uce.cn:7051, [6240ms] received
from server master-hadoop2.uce.cn:7051 response OK, [6700ms] sending RPC to server master-hadoop2.uce.cn:7051,
[6700ms] received from server master-hadoop2.uce.cn:7051 response OK, [9539ms] sending RPC
to server master-hadoop2.uce.cn:7051, [9540ms] received from server master-hadoop2.uce.cn:7051
response OK, [10040ms] sending RPC to server master-hadoop2.uce.cn:7051, [10041ms] received
from server master-hadoop2.uce.cn:7051 response OK, [13940ms] sending RPC to server master-hadoop2.uce.cn:7051,
[13940ms] received from server master-hadoop2.uce.cn:7051 response OK, [17380ms] sending RPC
to server master-hadoop2.uce.cn:7051, [17380ms] received from server master-hadoop2.uce.cn:7051
response OK, [20540ms] sending RPC to server master-hadoop2.uce.cn:7051, [20540ms] received
from server master-hadoop2.uce.cn:7051 response OK, [22880ms] sending RPC to server master-hadoop2.uce.cn:7051,
[22880ms] received from server master-hadoop2.uce.cn:7051 response OK, [26400ms] sending RPC
to server master-hadoop2.uce.cn:7051, [26400ms] received from server master-hadoop2.uce.cn:7051
response OK, [26799ms] sending RPC to server master-hadoop2.uce.cn:7051, [26800ms] received
from server master-hadoop2.uce.cn:7051 response OK, [29040ms] sending RPC to server master-hadoop2.uce.cn:7051,
[29041ms] received from server master-hadoop2.uce.cn:7051 response OK, [32040ms] sending RPC
to server master-hadoop2.uce.cn:7051, [32041ms] received from server master-hadoop2.uce.cn:7051
response OK, [33280ms] sending RPC to server master-hadoop2.uce.cn:7051, [33280ms] received
from server master-hadoop2.uce.cn:7051 response OK, [35380ms] sending RPC to server master-hadoop2.uce.cn:7051,
[35380ms] received from server master-hadoop2.uce.cn:7051 response OK, [36040ms] sending RPC
to server master-hadoop2.uce.cn:7051, [36041ms] received from server master-hadoop2.uce.cn:7051
response OK, [38400ms] sending RPC to server master-hadoop2.uce.cn:7051, [38401ms] received
from server master-hadoop2.uce.cn:7051 response OK, [42240ms] sending RPC to server master-hadoop2.uce.cn:7051,
[42240ms] received from server master-hadoop2.uce.cn:7051 response OK, [42900ms] sending RPC
to server master-hadoop2.uce.cn:7051, [42900ms] received from server master-hadoop2.uce.cn:7051
response OK, [46680ms] sending RPC to server master-hadoop2.uce.cn:7051, [46681ms] received
from server master-hadoop2.uce.cn:7051 response OK, [47199ms] sending RPC to server master-hadoop2.uce.cn:7051,
[47200ms] received from server master-hadoop2.uce.cn:7051 response OK, [50900ms] sending RPC
to server master-hadoop2.uce.cn:7051, [50900ms] received from server master-hadoop2.uce.cn:7051
response OK, [53340ms] sending RPC to server master-hadoop2.uce.cn:7051, [53341ms] received
from server master-hadoop2.uce.cn:7051 response OK, [55920ms] sending RPC to server master-hadoop2.uce.cn:7051,
[55921ms] received from server master-hadoop2.uce.cn:7051 response OK, [58300ms] sending RPC
to server master-hadoop2.uce.cn:7051, [58300ms] received from server master-hadoop2.uce.cn:7051
response OK, [61780ms] sending RPC to server master-hadoop2.uce.cn:7051, [61781ms] received
from server master-hadoop2.uce.cn:7051 response OK, [62220ms] sending RPC to server master-hadoop2.uce.cn:7051,
[62221ms] received from server master-hadoop2.uce.cn:7051 response OK, [63440ms] sending RPC
to server master-hadoop2.uce.cn:7051, [63441ms] received from server master-hadoop2.uce.cn:7051
response OK, [65440ms] sending RPC to server master-hadoop2.uce.cn:7051, [65441ms] received
from server master-hadoop2.uce.cn:7051 response OK, [67719ms] sending RPC to server master-hadoop2.uce.cn:7051,
[67720ms] received from server master-hadoop2.uce.cn:7051 response OK, [70480ms] sending RPC
to server master-hadoop2.uce.cn:7051, [70480ms] received from server master-hadoop2.uce.cn:7051
response OK, [74280ms] sending RPC to server master-hadoop2.uce.cn:7051, [74280ms] received
from server master-hadoop2.uce.cn:7051 response OK, [76580ms] sending RPC to server master-hadoop2.uce.cn:7051,
[76580ms] received from server master-hadoop2.uce.cn:7051 response OK, [79520ms] sending RPC
to server master-hadoop2.uce.cn:7051, [79520ms] received from server master-hadoop2.uce.cn:7051
response OK, [80620ms] sending RPC to server master-hadoop2.uce.cn:7051, [80621ms] received
from server master-hadoop2.uce.cn:7051 response OK, [84320ms] sending RPC to server master-hadoop2.uce.cn:7051,
[84321ms] received from server master-hadoop2.uce.cn:7051 response OK, [88080ms] sending RPC
to server master-hadoop2.uce.cn:7051, [88080ms] received from server master-hadoop2.uce.cn:7051
response OK, [91380ms] sending RPC to server master-hadoop2.uce.cn:7051, [91381ms] received
from server master-hadoop2.uce.cn:7051 response OK, [94400ms] trace too long, truncated)
> At the same time, the kudu table created by impala can not be modified:
> ERROR: AnalysisException: Not allowed to set 'kudu.table_name' manually for managed Kudu
tables .
> Please help me,thanks!
> 
> 
> 优速物流科技有限公司
> 大数据中心     冯宝利
> Mobil:15050552430
> Email:fengbaoli@uce.cn

Mime
View raw message