Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

single server JS does show direct consumer when it shouldn't (clustered JS does not do that) #2213

Closed
matthiashanel opened this issue May 12, 2021 · 0 comments · Fixed by #2214
Assignees

Comments

@matthiashanel
Copy link
Contributor

config used (ignore the names saying leaf, this is a single server cluster):

port: 4111
server_name: leaf-server-1
jetstream {
	store_dir="./store_leaf_1"
}

cluster {
  name: leaf
}

include ./accounts.conf

Steps to reproduce:

  1. add a stream
  2. add a source stream sourcing first stream
  3. first stream now lists extra consumer
> nats -s nats://rmt:rmt@localhost:4111 s ls
No Streams defined
> nats -s nats://rmt:rmt@localhost:4111 s add
? Stream Name test
? Subjects to consume test
? Storage backend file
? Retention Policy Limits
? Discard Policy Old
? Stream Messages Limit -1
? Message size limit -1
? Maximum message age limit -1
? Maximum individual message size -1
? Duplicate tracking time window 2m
? Replicas 1
Stream test was created

Information for Stream test created 2021-05-12T00:18:40-04:00

Configuration:

             Subjects: test
     Acknowledgements: true
            Retention: File - Limits
             Replicas: 1
       Discard Policy: Old
     Duplicate Window: 2m0s
     Maximum Messages: unlimited
        Maximum Bytes: unlimited
          Maximum Age: 0.00s
 Maximum Message Size: unlimited
    Maximum Consumers: unlimited


State:

             Messages: 0
                Bytes: 0 B
             FirstSeq: 0
              LastSeq: 0
     Active Consumers: 0
> nats -s nats://rmt:rmt@localhost:4111 s add  --source test
X Sorry, your reply was invalid: Value is required
? Stream Name agg
? Storage backend file
? Retention Policy Limits
? Discard Policy Old
? Stream Messages Limit -1
? Message size limit -1
? Maximum message age limit -1
? Maximum individual message size -1
? Duplicate tracking time window 2m
? Replicas 1
? Adjust source "test" start No
? Import "test" from a different JetStream domain No
? Import "test" from a different account No
Stream agg was created

Information for Stream agg created 2021-05-12T00:18:59-04:00

Configuration:

     Acknowledgements: true
            Retention: File - Limits
             Replicas: 1
       Discard Policy: Old
     Duplicate Window: 2m0s
     Maximum Messages: unlimited
        Maximum Bytes: unlimited
          Maximum Age: 0.00s
 Maximum Message Size: unlimited
    Maximum Consumers: unlimited
              Sources: test


State:

             Messages: 0
                Bytes: 0 B
             FirstSeq: 0
              LastSeq: 0
     Active Consumers: 0
> nats -s nats://rmt:rmt@localhost:4111 c ls
? Select a Stream test
Consumers for Stream test:

	abCyIUyQ

> nats -s nats://rmt:rmt@localhost:4111 c info test
? Select a Consumer abCyIUyQ
Information for Consumer test > abCyIUyQ created 2021-05-12T00:22:25-04:00

Configuration:

    Delivery Subject: $JS.S.1o9KHHEE
         Deliver All: true
          Ack Policy: None
       Replay Policy: Instant
  Maximum Deliveries: 1
      Idle Heartbeat: 2.00s
        Flow Control: true

Cluster Information:

                Name: leaf
              Leader: leaf-server-1

State:

   Last Delivered Message: Consumer sequence: 0 Stream sequence: 0
     Acknowledgment floor: Consumer sequence: 0 Stream sequence: 0
         Outstanding Acks: 0
     Redelivered Messages: 0
     Unprocessed Messages: 0

>
derekcollison added a commit that referenced this issue May 12, 2021
We do not want to report consumers that were created for the purpose of sources or mirrors.

Signed-off-by: Derek Collison <derek@nats.io>
derekcollison added a commit that referenced this issue May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants