[
https://issues.apache.org/jira/browse/IMPALA-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Jacobs resolved IMPALA-5829.
------------------------------------
Resolution: Duplicate
Fix Version/s: Impala 2.10.0
You already filed a JIRA for this:
https://issues.apache.org/jira/browse/IMPALA-5751
As was stated there, this is fixed in Impala 2.10.
> Insert KUDU Table ERROR: FATAL_INVALID_AUTHENTICATION_TOKEN: Not authorized:
> authentication token expired
> ----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-5829
> URL: https://issues.apache.org/jira/browse/IMPALA-5829
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.9.0
> Environment: impala-2.9
> kudu-client 1.4.0 kudu-server 1.4.0
> Reporter: yyzzjj
> Fix For: Impala 2.10.0
>
> Attachments: TimLine图片20170823151329.png
>
>
> after runing about 7 days use impalad insert data to kudu get ERROR
> (retry no use )
> Status: Kudu error(s) reported, first error: Runtime error: Failed to write
> batch of 57681 ops to tablet 7d8b4c1d8b3c4f549c782db0866a8774 after 1
> attempt(s): Failed to write to server: b7f05bfccc774b6f83b8a128469f2cb3
> (172.22.194.70:7050): Client connection negotiation failed: client connection
> to 172.22.194.70:7050: FATAL_INVALID_AUTHENTICATION_TOKEN: Not authorized:
> authentication token expired
> {color:red}restart impala Cluster insert opt working{color}
> like [https://issues.apache.org/jira/browse/IMPALA-5751]
> KUDU-1.4.0 already contained
> [https://github.com/cloudera/kudu/commit/3db551f7b31def26c0fa04184843d3dfa6161d9a]
>
> [^TimLine图片20170823151329.png]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
