In the new buckets collection acquisition code added in SERVER-101680, if we attempt to acquire a legacy timeseries collections (i.e. one where a view plus system.buckets-prefix collection would be normally expected), but which is missing the view (e.g. because a stepdown), we accidentally acquire both the view and buckets namespace locks, in this order.

On the other hand, when dropping a well-formed time-series collection, the locks are acquired in buckets then view order.

This has potential for creating in a deadlock due to conflicting lock acquisition orderings.