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:13 +0000 (15:16 -0400)
commite36fbffbebacb3d15f2b5b190f086bdde65766b1
tree807d496301f41f1dc1605d39b79c16bfefeafde5
parent89ce04fc76fab6434cc0b9dba725cf6946431abb
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.028433 seconds and 4 git commands to generate.