[PR] Clarify lease database locker timings and database timeouts [activemq-website]

["colinwerner (via GitHub)" <gi...@apache.org>]

colinwerner opened a new pull request, #191:
URL: https://github.com/apache/activemq-website/pull/191

   Relates to apache/activemq#2667
   
   Changes to the Lease Database Locker section of the pluggable storage lockers page:
   
   - **Fix the lease timings.** The page said the lease is held for `lockKeepAlivePeriod` and extended by `lockAcquireSleepInterval`. It is the other way round: a lease lasts `lockAcquireSleepInterval` and the master renews it every `lockKeepAlivePeriod` (see `LeaseDatabaseLocker.keepAlive()`, which sets the expiry to `now + lockAcquireSleepInterval`).
   - **Add "Lease timing and database timeouts":**
     - size the lease to outlive the slowest renewal (`lockKeepAlivePeriod` + connect timeout + statement timeout);
     - bound lease statements with driver-level timeouts;
     - explain why `queryTimeout` is not safe for the lease on PostgreSQL with synchronous replication, where a cancelled commit is reported as successful.
   
   I couldn't build the site locally (no Ruby toolchain here); the change is plain Markdown in the existing heading style.
   
   Generated with Claude Code.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org
For additional commands, e-mail: gitbox-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact