mirror of
https://github.com/gogrlx/nats-server.git
synced 2026-04-02 03:38:42 -07:00
e1f0361b98
This can be helpful after a partial cluster restart since in that case the server name may not be known. However "server report jetstream" would report the peer ID that then can be used. For instance here is the output after a cluster restart where server "C" is not restarted. ``` nats -s nats://sys:pwd@localhost:4222 server report jetstream ... ╭────────────────────────────────────────────────────────────────────────────────────────────────╮ │ RAFT Meta Group Information │ ├─────────────────────────────────────────────────────┬────────┬─────────┬────────┬────────┬─────┤ │ Name │ Leader │ Current │ Online │ Active │ Lag │ ├─────────────────────────────────────────────────────┼────────┼─────────┼────────┼────────┼─────┤ │ A │ yes │ true │ true │ 0.00s │ 0 │ │ B │ │ true │ true │ 0.53s │ 0 │ │ Server name unknown at this time (peerID: jZ6RvVRH) │ │ false │ false │ 0.00s │ 0 │ ╰─────────────────────────────────────────────────────┴────────┴─────────┴────────┴────────┴─────╯ ``` With a change to the NATS CLI we could have something like: ``` nats -s nats://sys:pwd@localhost:4222 server raft peer-remove jZ6RvVRH --by_id ``` Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Tests
Tests that run on Travis have been split into jobs that run in their own VM in parallel. This reduces the overall running time but also is allowing recycling of a job when we get a flapper as opposed to have to recycle the whole test suite.
JetStream Tests
For JetStream tests, we need to observe a naming convention so that no tests are omitted when running on Travis.
The script runTestsOnTravis.sh will run a given job based on the definition found in ".travis.yml".
As for the naming convention:
- All JetStream tests name should start with
TestJetStream - Cluster tests should go into
jetstream_cluster_test.goand start withTestJetStreamCluster - Super-cluster tests should go into
jetstream_super_cluster_test.goand start withTestJetStreamSuperCluster
Not following this convention means that some tests may not be executed on Travis.