rbeckman-nextgen
commented
4 years ago What would happen with the following theoretical?
- Clustered two-node Active-Active Production environment and AMI backups
- All licenses used (2 of 2 for this scenario)
- Primary node failure (let's say primary partition fsck failure, which happens from time to time with EC2's)
- Replacement node stood up using AMI and existing key
Would this be disabled because of this license checking feature until I contact support / create a ticket / etc.?
Imported Comment. Original Details: Author: jimchandler Created: 2019-03-01T06:20:25.000-0800
Scenario and current state: Starting 3.7.0, if an end-user is paying for a Core Extension Bundle or higher licence, they have to add the licence key provided by NextGen, in mirth.properties. This registers the Mirth Connect EC2 instance with NextGen.
The problem with this, though, is that the end-user has no way to know which instances are using the licence key without manually documenting it someplace. If the end-user uses the licence key on more than the number of instances that they've paid for, by mistake, the instance fails to start. This is pretty bad for a production instance that has live customers and can only be solved by NextGen Support, who is impossible to reach out to if you're a Core Extension Bundle user. This also defeats the purpose of downgrading from Gold to Core Extension Bundle.
Ideal state:
Imported Issue. Original Details: Jira Issue Key: MIRTH-4384 Reporter: ashishshetty1992 Created: 2019-02-20T06:04:50.000-0800