Clustron Zaris 2.0.1: Durable by Default, Licensed in One Line

Zaris 2.0.1 is out. It's a drop-in upgrade from 2.0.0 — same wire protocol, same client API, same on-disk and in-memory formats — and it does two things worth upgrading for: it makes the cluster's ownership and recovery path meaningfully more durable under failure, and it gives Zaris a clean, built-in trial-and-license model so you can evaluate it and run it in production without friction.

Durability: the quiet part made solid

The hardest problems in a distributed store aren't on the happy path — they're in the seams. A node restarts mid-migration. A replica falls behind, then the active it was chasing fails back. Ownership of a partition moves while writes are still landing. Each of these is a window where an acknowledged write can quietly go missing if the handoff isn't exactly right.

2.0.1 closes a series of those windows. The work centered on the ownership and recovery backbone — the state machine that decides who owns a partition, how a lagging replica catches up, and how a migration cuts over — and on the data path underneath it during churn. Concretely:

• Replica catch-up is stronger. A replica that drifts far behind the active, or gets stranded by a promotion/demotion flip, is now detected and re-synced instead of sitting frozen.
• Migration cut-over is safer. The source of a partition no longer destroys its only copy on a stale cut-over proof; a segment the new owner hasn't fully adopted is retained until it's safe to drop. Acknowledged data isn't thrown away.
• Recovery reconciles both directions. Whether a replica is behind or ahead of the active after a churn storm, the leader reconciles it back to convergence.

None of this changes an API. It changes what happens when things go wrong.

How we know it holds

The claim behind this release is simple: under sustained chaos, acknowledged writes are not lost. We validate that with a continuous certification run — nodes stopped, started, and restarted at random; failovers; migrations; scale-out — against a workload that checks both data-plane convergence and API stability throughout.

2.0.1 passed a clean 12-hour run with zero genuine data loss and full convergence on both suites. That's the bar for shipping it.

Licensing: a trial that just works, and one line to license

Zaris now has a built-in licensing model, and it's designed to stay out of your way.

• A 30-day trial starts automatically on install. No key, no sign-up, no network access. It's bound to the machine, and the full product runs during the trial — nothing is held back.
• Need more time? A Trial-tier extension key lengthens the evaluation, typically to around 90 days total from install.
• Production is an Enterprise license, per machine: one machine is one seat, and any number of nodes on that machine share it.

The lifecycle is deliberately gentle. When the trial ends, the Web Console locks first — but the cluster keeps serving reads, writes, and coordination through a grace period, so you're never surprised by an outage. Only after the grace period does the product stop answering data operations, and even then nothing is deleted: nodes stay up, your data stays in memory, and activating a license resumes serving immediately — no restart, no data loss.

Activation is one line, and it applies across the whole workspace:

Set-ZrLicense -Key 'LIC-…'

That fans the key out to every manager in your workspace and prints a row per machine. You can also paste the key into the Web Console's license screen, or set ZARIS_SUPPORT_KEY on each host for scripted and air-gapped installs. Check where any machine stands with Get-ZrLicenseStatus.

See the Licensing and activation guide for the full lifecycle, the configuration knobs, and troubleshooting.

Upgrading from 2.0.0

In place. 2.0.1 is wire-compatible with 2.0.0 — the protocol, the client API, and the data formats are unchanged — so you can roll it out node by node. On first start after upgrade, each machine begins its 30-day trial automatically; activate your license when you're ready to run in production.

Get it

• Windows: clustron-zaris-2.0.1-win-x64.zip from the GitHub release — Management Service, Web Console, node runtime, and the PowerShell modules.
• Containers: clustron/zaris-node:2.0.1 and clustron/zaris-manager:2.0.1 (multi-arch, linux/amd64 + linux/arm64).
• NuGet: Clustron.Zaris.Client, Clustron.Zaris.SDK, Clustron.Zaris.Abstractions, Clustron.Zaris.InProc, Clustron.Zaris.DistributedCache, Clustron.Zaris.HybridCache — all at 2.0.1.

New to Zaris? Start with the quickstart. Questions or want to talk through a deployment? Reach out.