Search results

  1. R

    Moving from ScaleOut StateServer with GeoServer to ScaleOut StateServer

    We would like to know what is the best approach of moving from ScaleOut StateServer with GeoServer to ScaleOut StateServer (without GeoServer). We don't need anymore the GeoServer functionality. Can we just add new instances of regular ScaleOut StateServer and then remove the existing ones with...
  2. R

    threads blocking on read to scaleout server after moving to .NET 5

    Thanks a lot Mark. We'll try that out. Just to be sure - the optimized version ( corresponding to the one that's working for us in .NET framework ) is the one with forceManagedLocking = true right ?
  3. R

    threads blocking on read to scaleout server after moving to .NET 5

    Hi Marc, Maybe it's indeed related to the access patterns of our app - having a mixture of both sync and async calls. The failure manifests in lot of threads blocked while waiting for a connection to free up : Not Flagged 25944 2042 Worker Thread Worker Thread...
  4. R

    threads blocking on read to scaleout server after moving to .NET 5

    Hi Mark, Unfortunately that ( collections 1.0.4 ) , and moving most of our flows to async didn't help either. There are some locations which are more difficult to move to async , and it seems it's failing on them now- Not Flagged 25944 2042 Worker Thread Worker Thread...
  5. R

    threads blocking on read to scaleout server after moving to .NET 5

    Hello Mark, We want to try out the switch to async soon - do you think upgrading to the latest nuget version of the client could be helpful as well ( as mentioned , we currently use version 3.1.4 )? Thanks
  6. R

    threads blocking on read to scaleout server after moving to .NET 5

    Thanks Mark. We'll try switching to using async - should be relatively straightforward. If that doesn't work , we'd be happy if you could research applying to .NET Core an optimization similar to the one you did for the .NET framework build , which was very helpful. We'll keep you posted. Thanks !
  7. R

    threads blocking on read to scaleout server after moving to .NET 5

    Hello Mark, Thanks for your response. 1. The threads counts was about 500. 2. The clients run on Windows , and the Scaleout servers are on Linux. 3. Back then when you did the optimizations for .NET framework as regards to the locking replacement , you advised that we'd better also use the...
  8. R

    threads blocking on read to scaleout server after moving to .NET 5

    Hello, We've upgraded our apps which were using .NET Framework 4.7.2 successfully for a long time, to .NET 5. As a consequence our apps functionality degraded significantly and while analyzing the dumps we noticed a lot of threads stuck on 13032 506 Worker Thread Worker Thread...
  9. R

    Usage of SOSS with Nuget

    Hi, Thank you for your answer. When we migrated to the nuget package, basically we added the following attributes: [NugetSossIndex, LegacySossIndex] which are defined as: using NugetSossIndex = Scaleout.Client.QuerySupport.SossIndexAttribute; using LegacySossIndex =...
  10. R

    Usage of SOSS with Nuget

    Hi, We have a cluster with 4 SOSS nodes. In the past we used the DLL and recently we move to use the Nuget package DLL. After we upgraded or code to work with the Nuget, we're getting the following error once in 2-3 days: (from the log) 21/07/08 03:11:06 - Service: internal consistency check...
Top