[
https://issues.apache.org/jira/browse/IMPALA-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077920#comment-17077920
]
Balazs Jeszenszky commented on IMPALA-9622:
-------------------------------------------
FWIW I know it's possible this is the only way out of this - ie. it's a legit
deadlock -, but not sure that's the case here.
> Exceeding user disk quota leads to crash
> ----------------------------------------
>
> Key: IMPALA-9622
> URL: https://issues.apache.org/jira/browse/IMPALA-9622
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.12.0
> Reporter: Balazs Jeszenszky
> Priority: Major
> Attachments: pause_monitor_kill.log
>
>
> Apparently, a user running out of disk quota gets detected by JvmPauseMonitor
> as a deadlock and the impalad is killed. This is potentially bad since it
> could lead to a node crashing continuously if the user keeps firing queries
> without clearing up disk space, although this is the first time I'm seeing
> this.
> Ideally, the query should fail and cite the quota as a reason.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
