Closed phho closed 2 years ago
Attach whole nats server configuration and jwt directory. Please unzip it and start nats-server with the configuration, then try to publish more than 1000 messages. We have tried to reproduce the same issue in Windows, linux and container environment test-creds.zip nats-server-cfg-and-jwt.zip
If there is anything you are not clear about the issue, please let me know whether need to provide more information, thanks.
@phho sorry, this is totally my fault. When making this I forgot to export/import the flow control API and didn't notice it as I sent only a few messages...
This should fix your issue:
nsc add export --account TEST --name FC-API --service --response-type Stream --subject '$JS.FC.>'
nsc add import --account IMPORTER --src-account TEST --name Remote-FC-API --service --remote-subject '$JS.FC.>'
# push and inspect streams (mirror crossacc should have 1000 messages now)
nsc push -A -u nats://localhost:4222
nats stream report --creds keys/creds/myoperator/TEST/tuser.creds
nats stream report --creds keys/creds/myoperator/IMPORTER/iuser.creds
Please let me know if it does.
This area is still very complicated to set up, which is why we already decided to improve that going forward. Please watch the nats-server release notes for changes in this area.
Hi @matthiashanel, Mirror stream works now after adding the flow control API export/import configs. Thanks.
Defect
Follow the document (https://github.com/nats-io/jetstream-leaf-nodes-demo#connect-streams-cross-accounts) to configure mirror stream from another account's stream. It's not fully synced even after a long time.
nats-server -DV
outputVersions of
nats-server
and affected client libraries used:OS/Container environment:
Steps or code to reproduce the issue:
It is different from the documents (https://github.com/nats-io/jetstream-leaf-nodes-demo#connect-streams-cross-accounts), we only used one nats-sever and not in cluster mode to simplify the reproduction.
Completed the account relationship as below diagram and update to nats-server, the next test will see the problem of message synchronization.
Attach nsc nkey files and server config. nsc-and-server-config.zip
Expected result:
Actual result: