[
https://issues.apache.org/jira/browse/HAWQ-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107963#comment-15107963
]
ASF GitHub Bot commented on HAWQ-344:
-------------------------------------
GitHub user jiny2 opened a pull request:
https://github.com/apache/incubator-hawq/pull/281
HAWQ-344. When resource queue capacity is shrunk, deadlock detection …
When resource queue capacity is shrunk, deadlock detection maybe not
triggered.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiny2/incubator-hawq HAWQ-344-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/281.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #281
----
commit 67e945c473032023fc41cfeb058b3293eac3836e
Author: YI JIN <[email protected]>
Date: 2016-01-20T04:15:31Z
HAWQ-344. When resource queue capacity is shrunk, deadlock detection maybe
not triggered
----
> When resource queue capacity is shrunk, deadlock detection maybe not triggered
> ------------------------------------------------------------------------------
>
> Key: HAWQ-344
> URL: https://issues.apache.org/jira/browse/HAWQ-344
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Resource Manager
> Reporter: Amy
> Assignee: Yi Jin
>
> It maybe an unsigned integer problem. When resource queue capacity is shrunk,
> the waiting requests' vseg capacity is bigger than the real capacity, so that
> the D-value will be a negative number, then type of variable uint32 will
> turn the negative number to a big positive number.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
