You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/08/16 09:09:18 UTC
[jira] [Comment Edited] (PHOENIX-1172) Prevent lock contention in
ConnectionQueryServicesImpl. Fix exception handling.
[ https://issues.apache.org/jira/browse/PHOENIX-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099521#comment-14099521 ]
James Taylor edited comment on PHOENIX-1172 at 8/16/14 7:07 AM:
----------------------------------------------------------------
Looks good, [~samarthjain]. Much simpler. One question: what do you think about using an AtomicInteger for connectionCount instead of a lock?
was (Author: jamestaylor):
Looks good, [~samarthjain]. Much simpler. One question: what do you think about using an AtomicInteger for connectionCount instead of a lock? Or does it need to be locked at all?
> Prevent lock contention in ConnectionQueryServicesImpl. Fix exception handling.
> --------------------------------------------------------------------------------
>
> Key: PHOENIX-1172
> URL: https://issues.apache.org/jira/browse/PHOENIX-1172
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 3.1, 4.1
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Fix For: 5.0.0, 3.1, 4.1
>
> Attachments: PHOENIX-1172-3.0-v2.patch, PHOENIX-1172.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)