If a secondary node tries to acquire a DDL lock, the thread will get hung waiting here for the node to become primary again.

Until now, we have relied on the callers to ensure the node is the primary and the operation context is marked as interruptible when the DDL lock is acquired. However, we don't have any guarantees that this is going to be true.

The purpose of this ticket is to throw an error when the node is not the primary, instead of waiting for being the primary.