Connect

Discussions

Members

Resources

Events

 View Only

  • 1.  Connect CDC license expiry doesn’t stop replication - it locks your control instead

    Employee
    Posted 08-07-2026 19:53
    What I ran into
    I expected something dramatic when a Connect CDC license expired. I assumed replication would stop, kernels would shut down, and everything would break.
    That’s not what happens.
    What actually happens

    When the license expires:

    ✅ Kernel keeps running
    ✅ Replication continues in the background
    ❌ MonCon access is blocked
    ❌ Director access is blocked

    So the system keeps moving data, but you lose the ability to control or modify it.
    Why this feels confusing at first
    From the outside:
    • Data is still flowing
    • Jobs are still running
    • No obvious failure in pipelines
    But:
    • You cannot stop requests
    • You cannot make changes
    • You cannot manage models
    It feels like the system is “working” but you are locked out.
    The key insight
    License expiry in Connect CDC is not a runtime failure.
    It is a control-plane lockout.
    • Data plane (replication) → keeps running
    • Control plane (MonCon / Director) → gets restricted
    Once I understood this split, the behavior made a lot more sense.
    What about applying a new license?
    This was the part I found most useful.
    You can apply a new license key while the kernel is still running.
    No need to stop replication.
    That means:
    • No downtime required
    • No disruption to ongoing data flow
    • Just restore access and continue
    Why this matters in production
    In real environments, this changes how you respond to license issues:
    • There is no immediate panic to “fix before outage”
    • Replication continues safely in the background
    • You have time to apply the license and regain control
    The real risk is not data loss. It is losing the ability to manage the system.
    What changed for me
    I used to think licenses were tied directly to system uptime.
    This made it clear:
    Connect CDC separates data movement from system control.
    And license expiration only affects one of them.
    Takeaway
    If a Connect CDC license expires:
    • Your data keeps moving
    • Your control disappears
    Fixing it is not about restoring replication.
    It is about restoring visibility and control.

    Have you seen cases where replication was still running, but you couldn’t access MonCon or Director


    ------------------------------
    Adhitya Maya
    *Precisely Software Inc.
    ------------------------------


  • 2.  RE: Connect CDC license expiry doesn't stop replication - it locks your control instead

    Employee
    Posted 27 days ago

    Good point. Even if existing replication continues, the bigger operational risk is what happens if a request needs intervention while MonCon or Director access is unavailable. Keeping the license renewed before expiry is still important, especially in production.



    ------------------------------
    Sathya LJK
    *Precisely Software Inc.
    ------------------------------



  • 3.  RE: Connect CDC license expiry doesn't stop replication - it locks your control instead

    Employee
    Posted yesterday
    Good point. The real concern is not whether replication stops, but whether the environment remains manageable. If a request fails, falls behind, or requires administrative action while management access is restricted, recovery and troubleshooting become much more difficult.


    ------------------------------
    Neha Goel
    *Precisely Software Inc.
    ------------------------------