A Locker allows setting a max lock timeout which will cause lock acquisitions on that Locker to use the specified timeout or shorter. Until SERVER-74959, this max timeout applied to all resources including tickets; after SERVER-74959, it applies to all locks but it does not apply to tickets. This max lock timeout functionality is specifically useful for preventing deadlocks on resources that are acquired in an indeterminate order. However, certain resources are always acquired in a determinate order and thus should not need to abide by such a timeout. For instance, all locks under RESOURCE_GLOBAL and RESOURCE_MUTEX fall under this category. Thus we should consider defining a holistic policy for abiding by or ignoring the Locker's max lock timeout.