Search results

Hi Mark, After the original report the restarts continued but their frequency reduced without any action from our side. Also this time, the same behavior - a few days with many restarts and somehow it got stable. We do store multiple types in the same cache. We use inheritance, but we don't...

Hi, In the last few days we experience many issues with missing objects in the cache. It happens every few hours. We noticed in the SOSS logs that there were restarts. We saw these restarts in all the SOSS servers at the same time, so the whole cluster did reset. I added a file with 3 events...

Hi Mark, As you suggested, we tried to change the partitionCount param. It used to be 10, so we changed it to 64. We had the same issue, same bottleneck, so we changed it to 128. It seemed to behave better, but Yesterday we had the same issue again - one of our apps has spikes of threads (from...

Hi Mark, we tried one more time to deploy it. This time we changed other frequent flows to use async reads from the cache, so the majority of our code uses async calls to SOSS. It still behaves the same - one of our apps has spikes of threads (from ~100 to ~1000). Each time it happens on a...

Hi Mark, it will probably take more than a month until it will be deployed. I'll keep you updated.

Ok I'll update the Scaleout.Collections to 1.0.4 and I'll keep tracking it. Thank you!

Hi Mark, Thank you for the quick answer and for the help. I was waiting for it to reproduce after I added the pdb file, and here is the stack trace with the line numbers: "System.NullReferenceException","priority":11,"message":"Object reference not set to an instance of an object.\ \ at...

Hi, In the last 2 weeks we noticed that from time to time we have picks of a few minutes of NullReferenceException errors that come from inside the scaleout client. It doesn't happen every day, but sometimes it happens a few times a day. System.NullReferenceException "message":"Object...