[
https://issues.apache.org/jira/browse/HIVE-16847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-16847:
------------------------------------
Attachment: HIVE-16847.06.patch
Updated the patch. The sync block is how the queue access is synchronized. The
queue itself is synchronized too, though, so it shouldn't be necessary.
Overall, some synchronization is needed if we want to get the queue in order.
To protect against malicious users, rate limiting should happen on UI level.
> LLAP queue order issue
> ----------------------
>
> Key: HIVE-16847
> URL: https://issues.apache.org/jira/browse/HIVE-16847
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-16847.01.patch, HIVE-16847.01.patch,
> HIVE-16847.02.patch, HIVE-16847.03.patch, HIVE-16847.04.patch,
> HIVE-16847.05.patch, HIVE-16847.06.patch, HIVE-16847.patch
>
>
> There's an ordering issue with the LLAP queue that we've seen on some run.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
