we have a SolrCloud with 3 nodes. we add documents to leader node and use
commitwithin(100secs) option in SolrJ to add documents. AutoSoftCommit in
SolrConfig is 1000ms.
Transaction logs on replicas grew bigger than the index and we ran out of
disk space in few days. Leader's tlogs are very small
we have a SolrCloud with 3 nodes. we add documents to leader node and use
commitwithin(100secs) option in SolrJ to add documents. AutoSoftCommit in
SolrConfig is 1000ms.
Transaction logs on replicas grew bigger than the index and we ran out of
disk space in few days. Leader's tlogs are very small
We were trying to migrate to 4.5 from 4.0 and faced similar issue as well.
I saw the ticket raised by Chris and tried setting formdataUploadLimitInKB
to a higher value and which did not resolve this issue.
We use Solr 4.0.0 currently and no additional container settings are
required. But it is ver
we have a similar error as this thread.
http://www.mail-archive.com/solr-user@lucene.apache.org/msg90748.html
Tried tomcat setting from this post. We used exact setting sepecified
here. we merge 500 documents at a time. I am creating a new thread
because Michael is using Jetty where as we use Tom
rrors when I put a second server in the cloud.
> Single servers (external zookeeper, but no cloud partner) works just fine.
>
> I suppose my next step is to try Tomcat, but according to your post, it
> will not help!
>
> Any help is appreciated,
>
> M.
>
> - Origina
t; - Mark
>
> > On Oct 29, 2013, at 12:36 AM, Sai Gadde wrote:
> >
> > Hi Michael,
> >
> > I downgraded to Solr 4.4.0 and this issue is gone. No additional settings
> > or tweaks are done.
> >
> > This is not a fix or solution I guess but, in our case
Our index is aggregated content from various sites on the web. We want good
user experience by showing multiple sites in the search results. In our
setup we are seeing most of the results from same site on the top.
Here is some information regarding queries and schema
site - String
gt; http://wiki.apache.org/solr/**FieldCollapsing<http://wiki.apache.org/solr/FieldCollapsing>
> https://cwiki.apache.org/**confluence/display/solr/**Result+Grouping<https://cwiki.apache.org/confluence/display/solr/Result+Grouping>
>
> -- Jack Krupansky
>
> -Original M
boost still in place.
Thanks in advance
On Sun, Sep 8, 2013 at 6:36 AM, Furkan KAMACI wrote:
> What do you mean with "*these limitations" *Do you want to make multiple
> grouping at same time?
>
>
> 2013/9/6 Sai Gadde
>
> > Thank you Jack for the suggestion.
Perfect. This is exactly what we need!
I wish there is an option for plugin (or) if there is some feature like
this in mainstream Solr release.
Still this is a great resource for us. Thanks Marc for pointing to very
useful information.
Thanks all for the help.
On Tue, Sep 10, 2013 at 5:30 PM
as you describe. Also,
> there have been a lot of changes since 4.0, if you have the bandwidth you
> might
> try with a current build.
>
> Best
> Erick
>
>
> On Fri, Jan 4, 2013 at 2:02 AM, Sai Gadde wrote:
>
> > I have a single collection and shard in my Sol
ed now).
>
> Why do you want to force a full replication? If you have
> a suspicious replica, just shut it down and delete it's index
> directory and start it up back up again perhaps?
>
> Best
> Erick
>
>
> On Sat, Jan 5, 2013 at 1:33 AM, Sai Gadde wrote:
>
>
are fine. Personally I prefer autocommit because then you can
> just "forget" about commits.
>
> Tomás
>
>
> On Thu, Jan 10, 2013 at 7:51 AM, gadde wrote:
>
> > we have a SolrCloud with 3 nodes. we add documents to leader node and use
> > commit
13 matches
Mail list logo
