- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
You can't execute queries until the end of the 'atomic' block
- Labels:
-
Apache Hive
-
Apache Impala
Created on ‎08-06-2019 03:11 PM - edited ‎08-06-2019 03:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am getting above error from Hive while trying to query a table.
This is coincidentally during an insert operation on the table...
does it mean I cant access the table while a hive insert operation is ongoing...?
table contains lots of rows partitioned by two columns
Created ‎08-09-2019 01:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't see any errors posted in the post, can you please share again?
In general, Hive have locking mechanism enabled, so when INSERT is happening on a table, an exclusive lock will be place on the table and any query tries to run against the same table will have to wait, and there is a timeout to control how long the wait will be, and the query will fail with error if timeout exceeded, otherwise it will just keep waiting until lock is released.
So to understand more on the issue, I need to see what error was reported.
Cheers
Eric
Created ‎08-29-2021 11:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Issue resolved by increasing number of conection and session timeout as a workaround.
Actually need to use dedicated disk for DB's.
Thanks,
Syed
Created ‎08-09-2019 01:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't see any errors posted in the post, can you please share again?
In general, Hive have locking mechanism enabled, so when INSERT is happening on a table, an exclusive lock will be place on the table and any query tries to run against the same table will have to wait, and there is a timeout to control how long the wait will be, and the query will fail with error if timeout exceeded, otherwise it will just keep waiting until lock is released.
So to understand more on the issue, I need to see what error was reported.
Cheers
Eric
Created ‎03-01-2020 01:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi ,
im facing same issue ,
attached is the error screenshot
Created ‎12-25-2020 12:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am facing the same error when executing sql query through hue server。Now I have no idea to solve the error。
Please。
Created ‎07-19-2021 04:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Im also facing same issue ,
increased connections numbers to HUE DB, still issue exits.
Thanks,
SS
Created ‎07-20-2021 01:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you check "show locks" if the table is acquired EXCLUSIVE lock ?
Created ‎07-26-2021 11:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
No its not acquiring lock , result was empty set in hue DB.
Thanks,
syed
Created ‎08-03-2021 03:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DOes the same issue happen when you run via beeline ? I researched ,I found this occurs only in hue.
Created ‎08-04-2021 11:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
yes its happening at hue browser only
Created ‎08-07-2021 07:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hue is unable to handle the slow responses from Hive servers and hence the error. This happens when Hive is unable to return the query handle to Hue in a timely manner. So, the ideal solution here would be to investigate Hive slowness and not Hue.
Hue relies on server_conn_timeout parameter in its configuration (default 120s), after which the active sessions with hiveserver2 is teared down.
If Hue is using MySQL as the underlying DB, then we can tweak the innodb-lock-wait-timeout to be greater than the server_conn_timeout in Hue's configuration, that way we get fail-fast system and the locked tables are released. Please note that this is only a workaround until the cause of Hive performance issue is found and remediated.
