<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: How do the solr replication work? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107536#M46519</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/11971/wlo.html" nodeid="11971"&gt;@Wing Lo&lt;/A&gt; - The solution may depend on what is actually wrong. It may be that the node is just out of memory. If that's the case, a restart may resolve the issue (but it could occur again). &lt;/P&gt;&lt;P&gt;If the index data is actually corrupt, you can take the bad node offline and the errors will stop.  However, if the index is actually corrupt, you will need to fix/replace the bad data. I have not used this technique, but you might look at this &lt;A href="https://support.lucidworks.com/hc/en-us/articles/202091128-How-to-deal-with-Index-Corruption" target="_blank"&gt;https://support.lucidworks.com/hc/en-us/articles/202091128-How-to-deal-with-Index-Corruption&lt;/A&gt; &lt;/P&gt;</description>
    <pubDate>Thu, 17 Nov 2016 06:48:30 GMT</pubDate>
    <dc:creator>james_jones</dc:creator>
    <dc:date>2016-11-17T06:48:30Z</dc:date>
    <item>
      <title>How do the solr replication work?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107535#M46518</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I wonder how's the replication work on solr? One of the core_node data directory is crashed, will solr automatically recover the lost data? If not, how to do it manually? The replication factor is set to 2 for this collection&lt;/P&gt;&lt;P&gt;Now I am still able to query without error messages but sometime it returns the correct total number of documents and sometime it show roughly 50% of it. &lt;/P&gt;&lt;P&gt;How do I correct this problem?&lt;/P&gt;&lt;P&gt;-Wing &lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 05:15:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107535#M46518</guid>
      <dc:creator>wlo</dc:creator>
      <dc:date>2016-11-17T05:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: How do the solr replication work?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107536#M46519</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/11971/wlo.html" nodeid="11971"&gt;@Wing Lo&lt;/A&gt; - The solution may depend on what is actually wrong. It may be that the node is just out of memory. If that's the case, a restart may resolve the issue (but it could occur again). &lt;/P&gt;&lt;P&gt;If the index data is actually corrupt, you can take the bad node offline and the errors will stop.  However, if the index is actually corrupt, you will need to fix/replace the bad data. I have not used this technique, but you might look at this &lt;A href="https://support.lucidworks.com/hc/en-us/articles/202091128-How-to-deal-with-Index-Corruption" target="_blank"&gt;https://support.lucidworks.com/hc/en-us/articles/202091128-How-to-deal-with-Index-Corruption&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 06:48:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107536#M46519</guid>
      <dc:creator>james_jones</dc:creator>
      <dc:date>2016-11-17T06:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: How do the solr replication work?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107537#M46520</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/2229/jamesjones.html" nodeid="2229"&gt;@james.jones&lt;/A&gt;&lt;P&gt; Thanks for the suggestions. Everything seem working after i restart the Solr. Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 22:35:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107537#M46520</guid>
      <dc:creator>wlo</dc:creator>
      <dc:date>2016-11-17T22:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: How do the solr replication work?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107538#M46521</link>
      <description>&lt;P&gt;Awesome. If it continues to happen you'll need to figure out why you're getting OOM (assuming that was what was happening). Intermittent exceptions are often a symptom of OOM exceptions. Solr loves memory but there are a lot of factors that can contribute to it. Sometimes giving the JVM more memory is the solution, but not always.  Good luck.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 23:09:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-do-the-solr-replication-work/m-p/107538#M46521</guid>
      <dc:creator>james_jones</dc:creator>
      <dc:date>2016-11-17T23:09:16Z</dc:date>
    </item>
  </channel>
</rss>

