R.I.Pienaar
R.I.Pienaar
### Proposed change Today the meta leader owns assigning consumers which has performance implications due to the contention on the meta leader. This should be owned by the Stream leader....
### Proposed change Today users have to assure stream+consumer name combinations are unique across accounts and domains if they wish to do imports between those. Our FC and ACK subjects...
### Proposed change The backup/restore feature needs an entire revisit, probably completely scrapping what we have. Some, but not all, high level goals: * It should be resilient for very...
### Proposed change We need to improve how we handle high subject counts in core nats and streams, these lists should page to disk and be able to hold billions...
### Proposed change To support ADR-44 we need to have a way for clients to require a certain feature level when making an API call. ### Use case Today we...
### Proposed change The `$G` account does not produce connect/disconnect and other events, we should enable this. ### Use case Consistency in management. ### Contribution _No response_
### Proposed change We need to continue the work on Consumer Groups to expand the server feature set, specifically we need to start looking into dynamically partitioning streams rather than...
### Proposed change Include API level information in JSInfo order of preference: * Include it for each peer in the `MetaClusterInfo.Replicas` `PeerInfo` * the meta leader level in `MetaClusterInfo` ###...
### Proposed change Streams do a lot of consistency checks on each publish - ensuring that the message hit a disk on the quorum before marking it as accepted. This...
### Proposed change We should develop a pattern and framework for having feature flags in the server. There could be features we want to enable on just core behaviours but...