[
https://issues.apache.org/jira/browse/PHOENIX-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby updated PHOENIX-3663:
-------------------------------------
Attachment: PHOENIX-3663.patch
Patch to create an optional per-ConnectionQueryServices max number of
PhoenixConnections. I also noticed that the addendum to PHOENIX-3611 to remove
the maxSize on the ConnectionInfo/CQSI cache had been reverted or not applied
to trunk, so I re-did that as well.
> Implement resource controls in Phoenix JDBC driver
> --------------------------------------------------
>
> Key: PHOENIX-3663
> URL: https://issues.apache.org/jira/browse/PHOENIX-3663
> Project: Phoenix
> Issue Type: New Feature
> Affects Versions: 4.9.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Attachments: PHOENIX-3663.patch
>
>
> It would be very useful for service protection to be able to limit how many
> Phoenix connections a particular client machine can request at one time.
> This feature should be optional, and default to off for backwards
> compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
