docs(auditlog): mark follow-ups complete in roadmap; refresh stale comments
This commit is contained in:
@@ -32,6 +32,16 @@ public class SiteCallAuditOptions
|
||||
/// reports a <c>SiteUnreachable</c> outcome. Default 10 seconds: long enough
|
||||
/// to absorb a healthy cross-cluster round-trip, short enough that an
|
||||
/// operator clicking Retry on an offline site gets a fast, honest answer.
|
||||
/// <para>
|
||||
/// <b>Ordering invariant:</b> <c>RelayTimeout</c> must stay below
|
||||
/// <c>CommunicationOptions.QueryTimeout</c> (default 30s), the timeout the
|
||||
/// outer <c>CommunicationService.RetrySiteCallAsync</c>/<c>DiscardSiteCallAsync</c>
|
||||
/// Ask of the <c>SiteCallAuditActor</c> uses. The outer Ask must outlive this
|
||||
/// inner site relay Ask so the inner relay times out first and yields the
|
||||
/// distinct <c>SiteUnreachable</c> outcome; if the outer Ask expired first,
|
||||
/// that outcome would be lost to a generic Ask-timeout exception. The
|
||||
/// defaults (10s < 30s) satisfy this — keep the gap when tuning either.
|
||||
/// </para>
|
||||
/// </summary>
|
||||
public TimeSpan RelayTimeout { get; set; } = TimeSpan.FromSeconds(10);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user