[
https://issues.apache.org/jira/browse/KUDU-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348020#comment-17348020
]
Alexey Serbin commented on KUDU-2649:
-------------------------------------
The fact that waiting for a table's creation timed out doesn't mean the table
isn't going to be created eventually. The way how a table is created in Kudu
is:
# client sends a request to create the table
# client waits for the completion of the table creation process, polling for
the status of the process with some pre-defined timeout (by default it's 30
seconds)
There are multitude of reasons behind the timeout of waiting for the table
creation in 30 seconds. One possible reason is an overloaded cluster. Another
is [KUDU-3124|https://issues.apache.org/jira/browse/KUDU-3124]. There might be
many more. To understand what's really going on on the server side, it's
better to check the server-side logs.
As a workaround, it's possible to set {{\-\-kudu_client_rpc_timeout_ms}} flag
for {{impalad}} to something higher than 30000 (starting with impala version
3.0.1).
As for this particular JIRA issue, the way how this issue is reported doesn't
constitute a valid defect report that allows for troubleshooting and correcting
it, so it's been resolved as INVALID.
> 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
> Fix For: n/a
>
> 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=180000, 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 server
> master-serverA1:7051, [49561ms] received from server master-serverA1:7051
> response OK, [50080ms] sending RPC to server master-serverA1:7051, [50080ms]
> received from server master-serverA1:7051 response OK, [52260ms] sending RPC
> to server master-serverA1:7051, [52261ms] received from server
> master-serverA1:7051 response OK, [52279ms] sending RPC to server
> master-serverA1:7051, [52280ms] received from server master-serverA1:7051
> response OK, [54579ms] sending RPC to server master-serverA1:7051, [54580ms]
> received from server master-serverA1:7051 response OK, [56620ms] sending RPC
> to server master-serverA1:7051, [56621ms] received from server
> master-serverA1:7051 response OK, [57180ms] sending RPC to server
> master-serverA1:7051, [57180ms] received from server master-serverA1:7051
> response OK, [57819ms] sending RPC to server master-serverA1:7051, [57820ms]
> received from server master-serverA1:7051 response OK, [60260ms] sending RPC
> to server master-serverA1:7051, [60261ms] received from server
> master-serverA1:7051 response OK, [61440ms] sending RPC to server
> master-serverA1:7051, [61440ms] received from server master-serverA1:7051
> response OK, [61920ms] sending RPC to server master-serverA1:7051, [61920ms]
> received from server master-serverA1:7051 response OK, [64100ms] sending RPC
> to server master-serverA1:7051, [64101ms] received from server
> master-serverA1:7051 response OK, [65080ms] sending RPC to server
> master-serverA1:7051, [65080ms] received from server master-serverA1:7051
> response OK, [68080ms] trace too long, truncated)
>
> but after this error i can find the table in kudu web ui , and i can not show
> the table in impala
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
