Competing Consumers not showing on Web UI

EventStoreDB
1

I’ve just started to look at competing consumers and have written a small C# driver app to create and connect to a subscription group. It appears to be working with the events being handled and correct trace being logged by my console app. The Web UI stream browser shows the group within the $persistentSubscriptionConfig stream so I’m assuming all is ok. However there is nothing being displayed under the ‘Competing Consumers’ option of the Web UI.

Is there a command line flag that needs to be set when starting ES for this area to be enabled or could I be missing something else?

I’m running version 3.3.1.0

2

I have had similar issues with the Competing Consumers (but not able to replicate) where Streams don’t appear on the GUI, or other values don’t seem to make sense.
When I restart my ES and GUI, it seems to sort itself out.

If the Stream and Group are browsable, I would just accept that for now.

Hopefully you haven’t spent too much time on this :wink:

Steven

3

Are you getting events pushed over the subscription? Does the stream
that the subscription is tied to exist?

4

yes to both questions.

5

If you curl to

yournode:port/subscriptions and yournode:port/subscriptions/{name}
what do you get? (there is a restful API)

6

When I run ‘yournode:port/subscriptions’ I get the result shown below, however when I add the name I am receiving a 404 Not Found (using postman to hit the API)

[

{

“links”: [

{

“href”: “http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup”,

“rel”: “detail”

}

],

“eventStreamId”: “$stats-127.0.0.1:2113”,

“groupName”: “statsGroup”,

“parkedMessageUri”: “http://127.0.0.1:2113/streams/$persistentsubscription-$stats-127.0.0.1:2113::statsGroup-parked”,

“status”: “Live”,

“averageItemsPerSecond”: 0,

“totalItemsProcessed”: 3,

“lastProcessedEventNumber”: -1,

“lastKnownEventNumber”: 138,

“connectionCount”: 0,

“totalInFlightMessages”: 0

},

{

“links”: [

{

“href”: “http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup1”,

“rel”: “detail”

}

],

“eventStreamId”: “$stats-127.0.0.1:2113”,

“groupName”: “statsGroup1”,

“parkedMessageUri”: “http://127.0.0.1:2113/streams/$persistentsubscription-$stats-127.0.0.1:2113::statsGroup1-parked”,

“status”: “Live”,

“averageItemsPerSecond”: 0,

“totalItemsProcessed”: 31,

“lastProcessedEventNumber”: 29,

“lastKnownEventNumber”: 138,

“connectionCount”: 0,

“totalInFlightMessages”: 0

},

{

“links”: [

{

“href”: “http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup2”,

“rel”: “detail”

}

],

“eventStreamId”: “$stats-127.0.0.1:2113”,

“groupName”: “statsGroup2”,

“parkedMessageUri”: “http://127.0.0.1:2113/streams/$persistentsubscription-$stats-127.0.0.1:2113::statsGroup2-parked”,

“status”: “Live”,

“averageItemsPerSecond”: 0,

“totalItemsProcessed”: 2,

“lastProcessedEventNumber”: 44,

“lastKnownEventNumber”: 138,

“connectionCount”: 0,

“totalInFlightMessages”: 0

}

]

7

and when you go to ...

http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup2

?

Also I think I see the issue $ not escaped.

8

I get the following when I go to http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup2

{

“links”: [

{

“href”: “http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup2”,

“rel”: “detail”

},

{

“href”: “http://127.0.0.1:2113/subscriptions/$stats-127.0.0.1:2113/statsGroup2/replayParked”,

“rel”: “replayParked”

}

],

“config”: {

“resolveLinktos”: true,

“startFrom”: -1,

“messageTimeoutMilliseconds”: 30000,

“extraStatistics”: false,

“maxRetryCount”: 10,

“liveBufferSize”: 500,

“bufferSize”: 500,

“readBatchSize”: 20,

“preferRoundRobin”: true,

“checkPointAfterMilliseconds”: 2000,

“minCheckPointCount”: 10,

“maxCheckPointCount”: 1000,

“maxSubscriberCount”: 10,

“namedConsumerStrategy”: “RoundRobin”

},

“eventStreamId”: “$stats-127.0.0.1:2113”,

“groupName”: “statsGroup2”,

“status”: “Live”,

“averageItemsPerSecond”: 0,

“parkedMessageUri”: “http://127.0.0.1:2113/streams/$persistentsubscription-$stats-127.0.0.1:2113::statsGroup2-parked”,

“totalItemsProcessed”: 2,

“countSinceLastMeasurement”: 0,

“lastProcessedEventNumber”: 44,

“lastKnownEventNumber”: 149,

“readBufferCount”: 104,

“liveBufferCount”: 106,

“retryBufferCount”: 0,

“totalInFlightMessages”: 0,

“connections”: []

}

9

Chris,
Could you possibly open up the developer tools in your browser and inspect the request/response from the competing consumers tab?

I just want to determine where the issue lies.

Thanks!

10

I'm betting this doesn't happen with a non-system stream (no $ in the name).

11

Still getting the same issue when I use a non-system stream (just to point out again, that the subscription and events are being handled, it appears to be a UI issue)

Here is the response body from the browser developer tools:

[

{

“links”: [

{

“href”: “http://127.0.0.1:2113/subscriptions/Sender-580ab977436c460791de40be59ad1c94/senderGroup”,

“rel”: “detail”

}

],

“eventStreamId”: “Sender-580ab977436c460791de40be59ad1c94”,

“groupName”: “senderGroup”,

“parkedMessageUri”: “http://127.0.0.1:2113/streams/$persistentsubscription-Sender-580ab977436c460791de40be59ad1c94::senderGroup-parked”,

“status”: “Live”,

“averageItemsPerSecond”: 0.0,

“totalItemsProcessed”: 2,

“lastProcessedEventNumber”: -1,

“lastKnownEventNumber”: 3,

“connectionCount”: 0,

“totalInFlightMessages”: 0

},

{

“links”: [

{

“href”: “http://127.0.0.1:2113/subscriptions/Sender-580ab977436c460791de40be59ad1c94/senderGroup1”,

“rel”: “detail”

}

],

“eventStreamId”: “Sender-580ab977436c460791de40be59ad1c94”,

“groupName”: “senderGroup1”,

“parkedMessageUri”: “http://127.0.0.1:2113/streams/$persistentsubscription-Sender-580ab977436c460791de40be59ad1c94::senderGroup1-parked”,

“status”: “Live”,

“averageItemsPerSecond”: 0.0,

“totalItemsProcessed”: 1,

“lastProcessedEventNumber”: -1,

“lastKnownEventNumber”: 3,

“connectionCount”: 1,

“totalInFlightMessages”: 0

}

]

12

Ok, I randomly decided to open the Web UI in chrome and it worked.The issue however is still in IE.

13

Will have a look and fix in the next release! thanks for testing Chris!

14

No problem Pieter. Further update, it works in both Edge and Chrome with system streams ($stats-127.0.0.1:2113) but still not in IE.

15

Thanks for the update Chris.

16

Do other streams e.g. "foo" have the same behaviour across browsers?

17

Yes they do Greg, certainly from what I have seen today.

18

hmm

56190479.jpg