You are here: Redundant License Managers > Redundant License Managers and Usage Logs

Redundant License Managers and Usage Logs

Each License Manager in the pool has its usage log. If the leader License Manager is always up, all the transactions are logged in its usage log file.

Given below is a example that describes transaction ID update in the usage logs when the leader License Manager goes down:

Operation Transaction ID Logged in S1 Usage Log Transaction ID Logged in S2 Usage Log
Client A has requested a feature from the leader License Manager 0 --
Leader License Manager shuts down 10 --
Due to failover mechanism, Client A shifts to next License Manager (new leader) in the pool -- 14
Leader License Manager comes back and Client A sends an update 14 16
Client A releases this feature 2 --