3236
59%
master: 57%

Ran 11 Apr 2016 07:34PM UTC

Jobs 1

Files 52

Run time 1min

Badge

Embed ▾

pending completion

Build # 3236

Build Type

Pull #1151

travis-ci

Committed by

thibaultCha

Commit Message

fix(cassandra) add a 'port' option for clusters

Clusters with nodes not running on the default `9042` port couldn't be
properly reached by Kong. This bumps the driver (including the fix), and
adds a `port` options to the configuration. Thanks @allisthere2love for
the investigation.

This issue was never encountered before and my guess is because such
clusters added their contact_points including the port (`x.x.x.x:9043`),
and the driver could connect to it, but not to the other nodes, since it
was trying `9042` on those. So it simply considered the other nodes as
DOWN, and thus still works (if one doesn't check the logs and those lags
are not displaying warnings, it seems like nothing is going wrong).
However @allisthere2love had nodes from another C* cluster listening on
`9042`, leading to inconsistencies and thus, actual errors that allowed
us to track it down.

As per other datastax drivers, all nodes of a cluster must listen on the
same port.

Fix Mashape/kong#1139
See thibaultCha/lua-cassandra#47

Pull Request Pull Request #1151: fix(cassandra) add a 'port' option for clusters

Run Details

1545 of 2606 relevant lines covered (59.29%)

27.12 hits per line

Uncovered Existing Lines

Lines	Coverage	∆	File
111	100.0		./kong/dao/cassandra_db.lua

Jobs

ID	Job ID	Ran	Files	Coverage
1	3236.1 (TEST_SUITE=unit)	11 Apr 2016 07:34PM UTC	0	59.29	Travis Job 3236.1

Source Files on build 3236

Detailed source file information is not available for this build.

Mashape / kong / 3236
59%
master: 57%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 3236

Mashape / kong / 3236 59% master: 57%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 3236

Mashape / kong / 3236
59%
master: 57%

README BADGES
x