Arthur Petukhovsky ce1bbc9fa7 Always send the latest commit_lsn in send_wal (#4150) ...

When a new connection is established to the safekeeper, the 'end_pos'
field is initially set to Lsn::INVALID (i.e 0/0). If there is no WAL to
send to the client, we send KeepAlive messages with Lsn::INVALID. That
confuses the pageserver: it thinks that safekeeper is lagging very much
behind the tip of the branch, and will reconnect to a different
safekeeper. Then the same thing happens with the new safekeeper, until
some WAL is streamed which sets 'end_pos' to a valid value.

This fix always sets `end_pos` to the most recent `commit_lsn` value.
This is useful to send the latest `commit_lsn` to the receiver, so it
will know how advanced this safekeeper compared to the others.

Fixes https://github.com/neondatabase/neon/issues/3972
Supersedes https://github.com/neondatabase/neon/pull/4144

2023-05-04 00:07:45 +03:00

..

spec

Fix typos

2022-05-28 14:02:05 +03:00

src

Always send the latest commit_lsn in send_wal (#4150)

2023-05-04 00:07:45 +03:00

Cargo.toml

Add more safekeeper and walreceiver metrics (#4142)

2023-05-03 17:07:41 +03:00