Add TA-131639 #18981
Add TA-131639 #18981
Conversation
Fixes DOC-11251
Files changed: |
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
❌ Deploy Preview for cockroachdb-docs failed. Why did it fail? →
|
|
TFTR @arulajmani ! (FYI for anyone reading, the reason this build is failing is b/c the link to v23.1.27 release notes does not exist yet, once #18978 merges that link will exist and I'll trigger re-build of this) |
|
@rmloveland please hold off on merging this for now. We need to find a better way to eliminate false positives without manual inspection of the logs before publishing. If we don’t do a good enough job, we’ll create a lot of undue concern. |
👍 |
| applied lease after .* replication lag, client traffic may have been delayed.*epo=.*prev.*exp=.*Request.* | ||
| ~~~ | ||
|
|
||
| If all three of these log lines are present and the timestamp of the third log is less than the specified "replication lag" after the timestamp of the second log, then it is possible that a lost write occurred on the range identified in the third log line. |
There was a problem hiding this comment.
@nvanbenschoten - wdyt about putting a few of those examples that you had from the original issue investigation to really drive home what we're looking for. Maybe we can "bold" the bits of interesting (does markdown support bold within a code block??).
There was a problem hiding this comment.
Maybe we can "bold" the bits of interesting (does markdown support bold within a code block??).
AFAICT the answer is no but we can do ASCII gymnastics like
INFO: the value of foo=bar at time t=123
^^^^^^^
LOOK FOR THIS
thanks @florence-crl! applied all of your suggestions |
Fixes DOC-11251