We have a load balanced environment and the number of members registered is about 15000.
When registering, the user is sent an email with a GUID that we use to find them and verify their email. Initially we were finding the user with (in essence):
This all worked fine on dev with only a small set of members, but with thousands of members this method times out and an exception is returned.
To get around this I created an Examine index that indexed this GUID, and that all works fine, once the index has been updated. I'm guessing if this was a single server I could update the index easily enough when the member is created and our code is running. However I need the index to update on all the load balanced servers at the same time so when the follow the link the random server they hit has the updated index.
Does anyone have any suggestions?
Maybe I shouldn't be using an Examine index and one of the services instead?
Members, Examine and load balancing
Hi all,
We have a load balanced environment and the number of members registered is about 15000.
When registering, the user is sent an email with a GUID that we use to find them and verify their email.
Initially we were finding the user with (in essence):
Member.GetAllAsList().SingleOrDefault(m => m.getProperty("verificationGuid").Value.ToString() == code);
This all worked fine on dev with only a small set of members, but with thousands of members this method times out and an exception is returned.
To get around this I created an Examine index that indexed this GUID, and that all works fine, once the index has been updated. I'm guessing if this was a single server I could update the index easily enough when the member is created and our code is running. However I need the index to update on all the load balanced servers at the same time so when the follow the link the random server they hit has the updated index.
Does anyone have any suggestions?
Maybe I shouldn't be using an Examine index and one of the services instead?
TIA,
Craig.
is working on a reply...