R.I.Pienaar

A previous test cycle got these results: So I peer removed a online server, it went offline and was able to come back after restart (couldnt in the past). However...

So we should re-test what happens when an online peer is removed and it comes back after a restart (this is the problem, you remove a online peer it will...

Does seem to behave better now - but still, what do we gain by removing an online node? Soon as someone restarts it it will come back?

I am seeing some inconsistencies with messages on disk after it comes back, like some limits didnt apply or something ``` │ Server │ Cluster │ Domain │ Streams │...

Also after removing n1-nyc while online report jsz still gets given data about it: ``` ├─────────┬─────────┬────────┬─────────┬───────────┬──────────┬─────────┬────────┬─────────┬─────────┬─────────┤ │ Server │ Cluster │ Domain │ Streams │ Consumers │ Messages │ Bytes...

And once it reboots and come back on - it gets no data and all the streams shows only the 2 peers ``` │ Stream │ Storage │ Placement │...

I don’t think these problems are limited to taking off online nodes and bringing tbem back - I think it’s in general issues with nodes coming back

We will do a CLI release soon that bumps to next nats.go. Just waiting for server to complete its release also.

Ongoing discussion here https://github.com/choria-io/general/discussions/47

At the very least we'd have to add a file like this for AIX https://github.com/goss-org/go-ps/blob/master/process_unix.go