After adding a clustering license, you should not have to restart Bitbucket to allow new nodes to join

Problem Definition

In Bitbucket Data Center versions up to and including 4.8, after adding a clustering license you must restart Bitbucket before new nodes are allowed to join. This adds friction and makes it harder to automate the deployment of Data Center instances where a clustering license hasn't been pre-installed.

Solution

Hazelcast should be constructed with all configured join methods enabled, but reject cluster join requests until a valid clustering license is supplied.