rocksdb_replicator: sample logs for missing WAL updates (#616)
rocksdb_replicator: sample logs for missing WAL updates (#616)

This log was previously added in #599. While it has been
very useful to detect the WAL TTL issue, it can be noisy due to an issue we are investigating (https://jira.pinadmin.com/browse/KV-5446) where the log may be printing for a long time before recovery, for every replication request.

Now that we know the root cause of the above issue (see details in the ticket, but basically the follower may be always lagging behind after the WAL expired from leader, until the follower's sequence number has caught up with lowest sequence number the leader has and the leader's rocksdb iterator cache has expired the entry for the request), and we have a metric to detect the issue as well, it's not very useful to print on every occurrence. we can reduce the log frequency.

Adding a GFLAG for that with a default value of 1 in every 1000 messages.
pinterest/rocksplicator,pinterest/rocksplicator,pinterest/rocksplicator,pinterest/rocksplicator,pinterest/rocksplicator