Issue Summary

The db.schema.lock.maxWait configuration property is currently documented as having the value in seconds when it is in fact in minutes. Additionally, the default value 30 minutes is also too long and will need to be reduced to a more reasonable value.

Steps to Reproduce

See the Database Schema section of the documentation for Bitbucket DC configuration properties.

Expected Results

The documentation should say "This value is in minutes."

Actual Results

The documentation currently says "This value is in seconds."

Workaround

Values specified for db.schema.lock.maxWait should be treated as minutes. If the default value of 30 minutes is taking to long and is causing issues, consider setting it to 5 minutes in the bitbucket.properties file.