storm.twisted.StorePool should expose API to put hard limit on connections (store_max)
Bug #373816 reported by
Drew Smathers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Storm |
Fix Committed
|
Medium
|
Thomas Herve | ||
Bug Description
(Note: This applies to twisted-integration branch)
StorePool currently allows connections to grow beyond store_max under load and tones them down later in adjust_pool_size(). I work environment where Oracle DBAs set dranconian limits on the number of client connections so having an option to not allow connection overflow is crucial. Please review the following changeset which adds allow_overflow as an option to StorePool (the default is True to preserve the current behavior):
http://
Related branches
Revision history for this message
| Thomas Herve (therve) wrote | #1 |
| Changed in storm: | |
| assignee: | nobody → Thomas Herve (therve) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
To post a comment you must log in.
Thanks, committed in r221 of the twisted-integration branch. It doesn't add an option though, and forces the value by default.