Here is a schema disagreement we encountered.
Schema versions:
        b6467059-5897-3cc1-9ee2-73f31841b0b0: [,]
        c8971b2d-0949-3584-aa87-0050a4149bbd: [,,]
        c733920b-2a31-30f0-bca1-45a8c9130a2c: []

We deployed an application which would send a schema update (DDL=auto). We found this prod cluster had 3 schema difference. Other existing applications were fine, so some people were curious what if we left this problem alone until off hours.

Is there any concerns with not resolve schema disagreement right away? FWIW we went ahead and restarted 221 first, and continue with the rest of the minors.