I have 2 instances of Tridion 2013 on 2 nodes behind an F5 load balancer. However, when I try to search, its very inconsistent/not accurate between both nodes. I never get the same results given the exact same criteria.
I have ran these commands via powershell on both nodes:
(Get-TcmRepository).ID | Sync-TcmSearchIndex -verbose restarted IIS, COM+ and services and still see no differences as prior.
Also, I have looked into:
but per the documentation, it seems as though the setup is for an outscaled solution. Can this still be done in my scenario?
Tough part about it is, that its hard to test in a lower or single instance environment, so I am stepping on glass in a higher clustered (load balanced) setup; otherwise, I would be firing pistols at the hip.
I have also looked into
http://localhost:8983/#/tridion Solr Admin and I can see how the
Statistics are displayed and also how a
Master node could replicate to a
Slave node in a given scenario, but I cannot connect the dots within my setup.
I have performed db maintenance scripts that did not make any differences to the search:
I have cross checked the indexes rebuild date and time, looks fine and as same as the script execution time. DB level everything looks fine as well..
Anyone have any quick guides out there on a Tridion search optimization tutorial in a load balanced scenario like mine? Or what about 3 nodes? A
Master node that gets replicated out to 2
Configuring a Search Host Master Server within the doc here,
Step #6 - In the
security-role element, find the
role-name element to identify the user group. All Slave Servers must configure the same Master Server user, who must be a Windows local user and a member of this user group.
<security-role> <role-name>servermaster\SDLSearchUsers</role-name> </security-role>
Maybe this is just poorly worded, but I cannot seem to grasp this step. The group
SDLSearchUsers exists on both nodes and contains the
Search is still not accurate on the clustered url when returning results of items that were created on each node intentionally.