Fix: make sure no index is in flight before using inactivity beacons
authorJulien Desfossez <jdesfossez@efficios.com>
Wed, 27 Aug 2014 17:59:21 +0000 (13:59 -0400)
committerDavid Goulet <dgoulet@efficios.com>
Wed, 3 Sep 2014 19:16:09 +0000 (15:16 -0400)
commit6f6e4c37288138998bb97ee0b3588ff5817ec90d
tree672ed983c9a5a63adf7988bad1eb85ea86bbe075
parent262c79ae38080b98923e64f40c2c0788a452e410
Fix: make sure no index is in flight before using inactivity beacons

Since the index is sent in two parts on two separate connections from
the consumer, there can be cases where we receive an inactivity beacon
between the index creation and the data reception.

This fix prevents from using the inactivity beacon if we know a data
index is coming.

Signed-off-by: Julien Desfossez <jdesfossez@efficios.com>
Signed-off-by: David Goulet <dgoulet@efficios.com>
src/bin/lttng-relayd/main.c
src/bin/lttng-relayd/stream.h
This page took 0.025495 seconds and 4 git commands to generate.