{
  "name": "restbase-cassandra",
  "description": "RESTBase table storage on Cassandra",
  "version": "0.3.6",
  "dependencies": {
    "async": "0.x.x",
    "bluebird": "~2.3.10",
    "cassandra-codec": "~0.0.3",
    "cassandra-driver": "~1.0.2",
    "connect-busboy": "git+https://github.com/gwicke/connect-busboy.git#master",
    "extend": "~2.0.0",
    "node-uuid": "git+https://github.com/gwicke/node-uuid.git#master",
    "request": "2.x.x",
    "restify": "2.x.x",
    "routeswitch": "~0.6.3"
  },
  "scripts": {
    "test": "mocha"
  },
  "devDependencies": {
    "mocha": "x.x.x",
    "mocha-jshint": "0.0.9"
  }
}

{
  "name": "restbase-cassandra",
  "description": "RESTBase table storage on Cassandra",
  "version": "0.3.6",
  "dependencies": {
    "async": "0.x.x",
    "bluebird": "~2.3.10",
    "cassandra-codec": "~0.0.3",
    "cassandra-driver": "git+https://github.com/gwicke/nodejs-driver.git#keepalive",
    "connect-busboy": "git+https://github.com/gwicke/connect-busboy.git#master",
    "extend": "~2.0.0",
    "node-uuid": "git+https://github.com/gwicke/node-uuid.git#master",
    "request": "2.x.x",
    "restify": "2.x.x",
    "routeswitch": "~0.6.3"
  },
  "scripts": {
    "test": "mocha"
  },
  "devDependencies": {
    "mocha": "x.x.x",
    "mocha-jshint": "0.0.9"
  }
}

Enable TCP keepalive in the cassandra driver
Enable TCP keepalive in the cassandra driver

Temporarily use a patched version of the cassandra driver with TCP keepalive
enabled. We are seeing cassandra connection hangs in production, in particular
after an unclean cassandra shutdown (OOM). This then causes client connections
to pile up in the worker, which in turn uses a lot of memory until the client
runs out of memory as well & is restarted by the coordinator.

Lets see if this helps.
