Files
nats-server/server
Matthias Hanel c56f3b9fbd Adding account purge operation (#3319)
* Adding account purge operation

The new request is available for the system account.
The subject to send the request to is $JS.API.ACCOUNT.PURGE.*
With the name of the account to purge instead of the wildcard.

Also added directory cleanup code such that server do not
end up with empty streams directories and account dirs that
only contain streams

Also adding ACCOUNT to leaf node domain rewrite table

Addresses #3186 and #3306 by providing a way to
get rid of the streams for existing and non existing accounts

Signed-off-by: Matthias Hanel <mh@synadia.com>
2022-08-05 18:24:19 +02:00
..
2022-07-05 09:33:12 +01:00
2022-07-05 09:33:12 +01:00
2022-07-28 17:25:37 -06:00
2022-07-28 17:25:37 -06:00
2022-01-21 11:03:19 -08:00
2022-07-06 13:16:13 -07:00
2022-07-06 13:16:13 -07:00
2022-08-04 18:01:26 -07:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:28:00 +01:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:28:00 +01:00
2020-02-25 19:53:09 -05:00
2021-11-15 17:23:08 -07:00
2022-03-17 17:53:06 -06:00
2022-02-04 13:32:18 -08:00
2022-04-01 17:55:33 -06:00
2019-05-06 15:41:38 -07:00
2022-08-05 07:52:23 -07:00
2022-07-25 11:31:12 -07:00
2022-01-21 11:03:19 -08:00
2020-06-12 10:03:47 -06:00
2022-08-02 18:06:39 -06:00
2018-10-06 14:06:14 -07:00
2022-03-17 17:53:06 -06:00
2021-11-15 17:23:08 -07:00
2021-11-15 17:23:08 -07:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:33:12 +01:00
2021-09-01 14:55:26 -07:00
2022-07-05 09:28:00 +01:00
2019-12-12 11:58:24 -07:00
2022-06-24 09:17:12 -07:00
2022-07-28 17:25:37 -06:00
2022-07-28 17:25:37 -06:00
2022-03-25 12:11:55 -06:00

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.go and start with TestJetStreamCluster
  • Super-cluster tests should go into jetstream_super_cluster_test.go and start with TestJetStreamSuperCluster

Not following this convention means that some tests may not be executed on Travis.