-
### Observed behavior
kv is created with OLD discard policy using jetstream pkg while with nats pkg it gets NEW
### Expected behavior
both pkgs shall have the same resolution
### Server and client…
-
### Observed behavior
When running NATS configuration that has a `hub` connecting two remote `leaf` nodes, we observe an warning when publishing a file to object store on a leaf node when it has a co…
-
### What version were you using?
nats-server: v2.0.0
Jetstream Version: 2.10.4
### What environment was the server running in?
Local - On Eclipse IDE running in my system
### Is this def…
-
### Proposed change
Jetstream `Context` is just a thin clone-able layer on top of core Client, however, you can't access Client after you create a `Context`.
Even though Client is `Clone`, it wo…
-
### Use case
updating consumers at runtime, useful for running consumer migrations
one thing i'm unsure of (i haven't been able to find any docs on updating consumers) is the broader effects of a …
-
At our company, we're big fans of event sourcing and message streaming between our services. We use Kafka a lot, but also sometimes Google's Pub/Sub when it makes sense.
I've been reading (and list…
-
### Observed behavior
Given a main and a leaf cluster and a stream on the main cluster. When I create a mirror of that stream and import and export the necessary services with `nsc` I expect that m…
-
### Name and Version
bitnami/nats 7.18.0
### What architecture are you using?
amd64
### What steps will reproduce the bug?
On my setup with 3 nats instances using Jetstream, one of the …
skoef updated
5 months ago
-
### Background information
- **Dendrite version or git SHA**: 0.6.5
- **Monolith or Polylith?**: Monolith
- **SQLite3 or Postgres?**: Postgres
- **Running in Docker?**: No (but in vm)
- **`…
-
### Expected Behavior
The subjects specified in the stream configuration (application.yml) are created or not created.
Unspecified subjects remain
### Actual Behaviour
Subjects in streams specifi…