Search results

I don't think you'll see a difference in performance of the core library functionality if you upgrade to the latest. Most of the changes since 3.1.4 have involved adding support for advanced features in the service (GeoServer, PMI, etc.). There was one important fix in 4.2.7 involving client...

OK, so you're still running with a whole lot of threads. We can research to see if there's a similar optimization available for the .NET Core build. But, if possible, I would try moving to the async Cache methods and at least test to see if there's an improvement. I'm almost certain it'll help...

A few questions: How many threads do you see blocked on GatewayMultiplexer.GetGatewayFor()? Hundreds? What operating system are you running on? Is it possible for you to move to async calls and keep your app's thread count down? For background, I looked through old support cases and pieced...

Hi Nadav, just a one-week check-in: have you had an opportunity to deploy 1.0.4 and determine whether it helped?

Thank you. The line number appears related to the fix we made, so I think there's a very good chance it's resolved. I cannot say it's fixed with 100% certainty because we still aren't able to repro this particular exception--the error here is a result of corruption that occurred in the cache at...

Hello again Nadav, We found and resolved an issue in the Scaleout.Collections NuGet package that may explain the exception that you reported. Please update your project to use version 1.0.4--we'll be interested to hear if this resolves the issue. Thanks!

Hi Nadav, We've reviewed error you reported and haven't yet located the source of the problem. Please copy the Scaleout.Collections.pdb file from the attached zip to the web server(s) that are experiencing this issue--it should be copied to the same folder as the Scaleout.Collections.dll file...

Hi Nadav, Thank you for reporting this and supplying the stack trace. We'll investigate and will let you know what we find.

Update: We're changing the server to return an error to the client instead tripping a consistency check and restarting. The exception thrown back to the Cache caller will help track down which type is causing the problem.

Thank you for those answers. I do not yet see a usage pattern or a mistake that you could make that would explain this -- the ObjectDisposedException is complaining about long-lived thread-local resource that the ScaleOut library never disposes. We need to learn more about your environment...

Hi YardenK. This is not a known issue. Is the exception thrown when your app first starts up or does is only occur after your app has been running for a long time? What kind of threading model does your app use? Is this just a regular ASP.NET app serving web requests, or does your app start a...

The two libraries ignore each other's [SossIndex] attributes, so using both should be fine. However, for every indexed property, I would check to make sure that the same HashIndexPriority value is passed into the constructor of both versions of the attribute. But it's interesting that you left...

Did your app’s usage of the [SossIndex] attribute change when you migrated to the Scaleout.Client nuget package? The log indicates that the server encountered an error as an object was being added to the cache--the service was indexing properties marked with the [SossIndex] attribute and found...

Are you experiencing this with the latest release of ScaleOut? Version 5.10.4.359 of the ScaleOut Product Suite addressed this empty screen issue. Otherwise, Oleg's fix (starting the soss_console.exe application with the -RESET flag) will work if you're running version 5.7 or later. If you're...

You can use the Values property or perform a query to get all the objects or keys in a NamedCache. However, please be aware that these approaches will perform a round trip to the ScaleOut service and invoke a parallel query on the distributed store, which involves all hosts. These are expensive...

Hi Bryan, Yes, the service's PerfMon counters will be the best approach on Windows. I don't have experience with DataDog, but a quick Google search shows that its agent can consume Windows performance counters. At a high level, monitoring the ScaleOut StateServer Service\Host Joined counter...

UPDATED 10-Mar-2021: The Scaleout.Client library docs have serialization guidance here: https://static.scaleoutsoftware.com/docs/dotnet_client/articles/serialization/serialization_overview.html Yes, Microsoft introduced this big breaking change in .NET 5. Our .NET libraries have used the...

No, that code should only be run once, typically at application startup. Once you have a Cache instance then it can be reused throughout the app.

Hi Amunike, 1. Your configuration looks good. Assuming you've installed the ScaleOut service on one or more hosts, open the ScaleOut Management Console application on one of the servers and check the store's object count--each new user session should cause the object count to increase by one...

If this exception occurs out of nowhere then it's typically the result of a networking change in your environment. On your client machines, open the soss_client_params.txt file and review the IP addresses in the remote gateway (rem_gw) entries listed there. For each IP address, use...