Heartbeats being sent, despite no publishing.

[yeetfield]

I have a publishing application on one host and an instance of Aeron Archive running on another host. On the publishing host, I'm observing within AeronStat that Bytes sent and Heartbeats sent continue to increase, even after I've terminated the publishing program (pub-pos does not increase). This causes the recording within Archive to be considered active, which precludes it from deletion. I'm currently mitigating this by restarting aeronmd.

Is there something I need to configure to have the publication deleted in the driver after some timeout where pub-pos isn't incremented? Thanks!

I've also got ssc=True and fc=min set on this channel.

[yeetfield]

Anecdotally, I'm also observing that this isn't happening when I reduce the publish rate of my application. It's almost as if my program isn't cleaning up the relevant resources properly when it's under higher load, but even so, I'd expect there to be some way to detect this from within the driver.

[mikeb01]

Do you still have an active subscription somewhere that hasn't reached the most recent published position. This will result in a publication remaining active in the driver.

[yeetfield]

There wasn't an active subscription here, outside of the one that I imagine exists in the Archive.

[mikeb01]

How long did you see heartbeats being sent for? There is also a linger timeout associated with publications before they get removed from the driver. If it was indefinite, could you post a code example that demonstrates the problem? Also did you check see if the publication is still visible in AeronStat?

[yeetfield]

We'll reopen if this become a priority again; it initially manifested when we were under an unrealistically high load.