Giter VIP home page Giter VIP logo

electrode-keepalive's Introduction

electrode-keepalive

electrode-keepalive provides an keep-alive HttpAgent capable of maintaining and tracking available sockets using IP address and hostname as key. This allows for graceful handling of DNS changes or failover when routing configuration is updated. It resolves part of the problems in this issue

It also uses the patched agentkeepalive to support destroying kept alive sockets within a timeout.

The big changes from agentkeepalive are:

  1. Do DNS lookup and use host and IP address as key to track sockets.
  2. Use LIFO instead of FIFO when reusing free sockets. This solves issue of free sockets stay around too long, because after a burst of traffic, node creates a long list of free sockets, and continuous traffic would cycle through and prevent them from expiring.

Usage

const ElectrodeKeepAlive = require("electrode-keepalive");
const keepAlive = new ElectrodeKeepAlive();
request({ url: "http://www.google.com", agent: keepAlive.agent });

HTTPS:

const ElectrodeKeepAlive = require("electrode-keepalive");
const keepAlive = new ElectrodeKeepAlive({ https: true });
request({ url: "https://www.google.com", agent: keepAlive.agent });

See contructor for details on options you can passed.

Install

npm install electrode-keepalive --save

APIs

Properties

instance.agent - Returns the http/https agent. (readonly)

instance.https - If true, then the agent is an https agent. (readonly)

ElectrodeKeepAlive.DNS_CACHE - Internal DNS cache mapping object.

ElectrodeKeepAlive.checkExpiredDnsInterval - Interval in milliseconds to check and delete expired DNS cache entries. Default: 5000ms

This is not a regular timer interval. The check only occurs when preLookup is called.

Static Methods

ElectrodeKeepAlive.clearDnsCache() - Wipes out current DNS mapping.

ElectrodeKeepAlive.deleteExpiredDnsCache() - delete any DNS cache entry that's expired.

Methods

constructor(options)

Creates an instance of ElectrodeKeepAlive.

  • options should be the default http agent settings that are passed through to the underlying implementation. Additionally the following options are supported:

    • https - If true, then creates an https Agent.
    • expiry - The duration (in milliseconds) that ip entries in the DNS mapping will be refreshed. Default: 5000ms
  • Since this uses agentkeepalive, you can also pass in any options it supports.

    • The defaults for the following two options are set if you didn't specify them:
      • freeSocketKeepAliveTimeout - 30000ms
      • timeout - 60000ms
  • keepAlive - This is always default to true by ElectrodeKeepAlive.

instance.preLookup(host, options, callback)

This method is used to do DNS lookup to translate host name into IP for tracking free sockets. It will also populate ElectrodeKeepAlive DNS cache.

The arguments matches Node dns module lookup.

instance.getName(options)

The internal method to override http agent's default getName. Not intended for public use.

instance.getNameAsync(options, callback)

Async version of getName.

electrode-keepalive's People

Contributors

jasonwilson avatar jchip avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

electrode-keepalive's Issues

Should Expiry be more or less than keepAliveMsecs?

Just curious if there are any known quirks. I know we're dealing with two things here, expiry of DNS cache and pinging the server to keep it's sockets open every n msec but have there been any noticeable behaviors where one should keep expiry or keepalivemsec at a particular threshold over the other for

Memory Leak

Team,

I wanted to inform you that since we introduced electrode into our code we noticed pretty drastic memory leaks which caused us to revert our changes. While preliminary review of the code doesn't show anything obvious, the evidence is clear.

screen shot 2017-06-15 at 11 49 34 am

This graph shows our memory metrics of our UI application, which a partnered API also saw the same memory decline. No other code changes were introduced. You'll notice the flat line is a set of servers that don't have the module while the rapid decline includes electrode.

Same is true for our regularly deployed development environment (flat lines are other non-prod environments)

screen shot 2017-06-15 at 11 59 27 am

We followed your implementation instructions completely. Since removing electrode, our memory is flat.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.