Websocket level2 - too many L2 streams requested in a single session

Started seeing a new error today:

{'type': 'error', 'message': 'too many L2 streams requested in a single session'}

When subscribing to 25 streams/container…

I dont see any API doc changes for this, so is this expected? If so, what is the new max?

For reference 25 streams per python container has been working well for months (Sub second flushes to DB) with < 0.1 cpu and 80mb allocated to each container…

Looks like the dev team rolled it back, and 25 is working again

Glad I didnt have to chop up my container :relieved:

1 Like