2
92%
main: 92%

Ran 16 May 2019 01:11AM UTC

Files 25

Run time 2s

Badge

Embed ▾

Committed 16 May 2019 01:01AM UTC coverage: 92.029% (-0.05%) from 92.075%

Job # 1919.2

Build Type

Pull #839

travis-ci

Committed by

web-flow

Commit Message

[FIXED] Clustering: channel first/last sequence may fall to zero

This could happen if the leader took a snapshot while messages were
not yet expired, then a node is started without state and tries
to restore from this snapshot. If the messages have expired by then,
no message would be stored. If that node later did a snapshot itself,
it would persist in it the first/last being zero. If no message are
published and this node becomes leader, it would start storing
messages at the wrong sequence and would also send the bad snapshot
to other nodes.

Resolves #833

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

Pull Request Pull Request #839: [FIXED] Clustering: channel first/last sequence may fall to zero

Run Details

11476 of 12470 relevant lines covered (92.03%)

49869.77 hits per line

nats-io / nats-streaming-server / 1919 / 2
92%
main: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1919.2

nats-io / nats-streaming-server / 1919 / 2 92% main: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1919.2

nats-io / nats-streaming-server / 1919 / 2
92%
main: 92%

README BADGES
x