[
https://issues.apache.org/jira/browse/IMPALA-11014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449242#comment-17449242
]
Tsvetomir Palashki commented on IMPALA-11014:
---------------------------------------------
[~csringhofer] Thanks for the reply. Here are the answers to your questions as
well as some additional information.
CDH 6 version: 6.3.2-1.cdh6.3.2.p0.1605554
HMS version: 2.1.1-cdh6.3.2
Logs
Impala Catalog Server:
{code:java}
E1125 02:25:51.949892 21791 catalog-server.cc:135] TableLoadingException: Error
loading metadata for table: some_table
CAUSED BY: MetaException: Object with id "" is managed by a different
persistence manager{code}
Impala Daemon:
{code:java}
E1123 15:06:55.069455 19096 client-request-state.cc:1121] ERROR Finalizing DML:
TableLoadingException: Error loading metadata for table: some_table
CAUSED BY: MetaException: Object with id "" is managed by a different
persistence manager {code}
One more question: is there a way to monitor for queries that fail with this
Exception, but have inserted the data regardless. Maybe using the profile of
the query?
I've attached the profile of one of the queries that fail with this exception:
[^profile.txt]
> Data is being inserted even though an INSERT INTO query fails
> -------------------------------------------------------------
>
> Key: IMPALA-11014
> URL: https://issues.apache.org/jira/browse/IMPALA-11014
> Project: IMPALA
> Issue Type: Bug
> Reporter: Tsvetomir Palashki
> Priority: Major
> Attachments: profile.txt
>
>
> We are executing an INSERT INTO query against Impala. In rare cases this
> query fails with the following error:
> {code:java}
> MetaException: Object with id "" is managed by a different persistence
> manager {code}
> Even though there is an error, the data is inserted into the table. This is
> particularly problematic due to our error handling logic, which refreshes the
> table metadata and retries the query, which causes data duplication.
> I am aware that this bug might be fixed in one of the newer Impala versions,
> but at this point, we are unable to upgrade.
> Can you suggest a workaround for this? Is it safe to assume that the data is
> always inserted when this particular error happens? Can we rely on the
> rows_inserted and rows_produced fields of the query in order to make
> assumptions about what data is inserted?
> The exact version of our Impala is:
> {code:java}
> impalad version 3.2.0-cdh6.3.2 RELEASE (build
> 1bb9836227301b839a32c6bc230e35439d5984ac) Built on Fri Nov 8 07:22:06 PST
> 2019 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
