Hayley Campbell

Hi @mmuller99, how much memory does the instance have available? Is it possible that the instance is running out of memory and killing the process?

@mmuller99 Thanks for the additional info While the index merges are unlikely to be the cause, you may want to set the `MaxAutoMergeIndexLevel` setting to a lower value to prevent...

We should also remember to port any changes done here to 20.10: https://github.com/EventStore/EventStore/issues/2977

We have decided to leave the reader thread auto-configuration as-is. The reader thread counts are generally correctly set for the size of the machine, provided that the machine is set...

We also need to take other caches into account when configuring the streamInfoCache rather than just basing it on the available memory. For example, if you change the chunk cache,...

@timothycoleman and @shaan1337 does https://github.com/EventStore/EventStore/pull/3569 cover this issue?

Thank you @dev-rowbot Just for clarification, did the projections that were affected go into any sort of faulted state? If not, we may still want to look into correctly handling...

Hi @StevenBlair123 to answer the initial issue, increasing the `ProjectionExecutionTimeout` is currently the correct way to resolve the error you're seeing. How long the projection code takes to execute depends...

Thanks for reporting this @rastrup! I can confirm that I'm seeing the same behaviour on 20.10.5 and on the 20.10 release branch. It works on 21.10.2, and I get the...

@oskardudycz it doesn't look like the next position is being sent from the server yet