Timeline for What happens to Sitecore - Solr query handling when a core is corrupted in Solr slave in a Master - slave setup?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2019 at 10:35 | vote | accept | Mahesh Varma | ||
| May 29, 2019 at 15:06 | comment | added | sitecorium | @YENUGUDHATIMAHESHVARMA Investigation into the issue itself doesn't really fit within the scope of your original question. If you are happy with the answer, I suggest further discussing your problems either in a chat, in the #solr channel in Sitecore Slack or by raising a new question demonstrating your findings so far. | |
| May 29, 2019 at 14:35 | comment | added | Mahesh Varma | Coming to "try querying the index manually". Sorry I am a bit layman here. I tried doing it in master by selecting query under the specific core in core selector available in solr dashboard (web interface). But in slave the whole core is missing so I couldn't do this. Is this correct way of doing it? Can you please let me know the correct way of doing it if this is not! | |
| May 29, 2019 at 14:32 | comment | added | Mahesh Varma | Missing core just hit me like a bolt from the blue. I tried checking logs only to find that core is corrupted. Do you know any reasons why this happens? I couldn't find any reason and after an extensive search in google, came to a conclusion that a core can be corrupted because of many reasons like sudden shut down or restart of server while indexes are updating etc., please let me know if you have any info on this too! | |
| May 29, 2019 at 13:21 | history | edited | sitecorium | CC BY-SA 4.0 |
added 19 characters in body
|
| May 29, 2019 at 13:09 | history | answered | sitecorium | CC BY-SA 4.0 |