Comments (6)
What exactly do you mean by max lifetime parameter? Could you give an example of where it would feature in the api?
from node-pool.
var pool = poolModule.Pool({
name: 'pool',
create: function (cb) {
//set this client's timer to 0
},
destroy: function (client) {
},
max: 30,
lifetime: 2 * 3600 //2 hours max clients' lifetime, after we recreate it.
})
Every 2 hours your module will call ".destroy" method and after will call ".create" method to recreate all old clients.
I can't do it by "idleTimeoutMillis" parameter because my clients have no idle time. They are working always and I have to restart they because of memory leak in clients (Firefox under Selenium server).
from node-pool.
Ok, Let me have a think about this, off the top of my head there should be a way to achieve this with the current version of node-pool
from node-pool.
We are facing the same problem, I think we can solve this by using the "validate" callback.
In create function, attach a timestamp to the resource. In validate make sure resource in not older than
xyz.
@sandfox that should do it. =)
from node-pool.
@jtsoi that sounds like a good solution. Let me know if it's not workable with the current code.
from node-pool.
@sandfox The POC is working well.
Both with TTL and "max_number_of_requests".
A note: If using this, make sure the TTL/max_number_of_requests is randomized, or all resources will expire at once.
I suggest we close this issue.
SOLUTION:
Use "validate" callback: https://github.com/coopernurse/node-pool#documentation
from node-pool.
Related Issues (20)
- Im not getting any performance using a pool connection vs reusing one connection
- waitingClientsCount function has disappeared HOT 1
- resource release not getting called HOT 2
- NPM installation faliure HOT 2
- Add param to factory
- Feature: add pool.use method. HOT 1
- Borrowed resources never go higher than 1 HOT 2
- Share pool between servers in a cluster HOT 3
- How to work maxWaitingClients? HOT 1
- Add destroy timeout to prevent pool.clear from hanging when destroy promise never resolves HOT 4
- testOnReturn = no-op?
- What does happen if I don't release the resource and close the node? HOT 2
- Resource not currently part of this pool HOT 1
- `ready` method from Pool is missing from the TS definitions (v3.8.2)
- .use does not handle synchronous work functions
- Consistently occuring `ResourceRequest timed out` Error HOT 1
- TimeoutError: ResourceRequest timed out HOT 2
- Suggested Feature: borrowTimeoutMillis HOT 2
- Pool does not maintain the minimum HOT 1
- Suggestion on softEvictConnections
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-pool.