he problem is still there.
> >
> >
> > -Original message-
> > > From:Mark Miller
> > > Sent: Fri 14-Dec-2012 19:05
> > > To: solr-user@lucene.apache.org
> > > Subject: Re: Strange data-loss problem on one of our cores
> > &
em is still there.
>
>
> -Original message-
> > From:Mark Miller
> > Sent: Fri 14-Dec-2012 19:05
> > To: solr-user@lucene.apache.org
> > Subject: Re: Strange data-loss problem on one of our cores
> >
> > Have you filed a JIRA issue for this that I
i notice a discrepancy after some time i am sure to report it. I doubt i'll
find it before 2013, if the problem is still there.
-Original message-
> From:Mark Miller
> Sent: Fri 14-Dec-2012 19:05
> To: solr-user@lucene.apache.org
> Subject: Re: Strange data-loss problem on
problem.
>
> -Original message-
>> From:John Nielsen
>> Sent: Fri 14-Dec-2012 12:31
>> To: solr-user@lucene.apache.org
>> Subject: Re: Strange data-loss problem on one of our cores
>>
>> How did you solve the problem?
>>
>>
&
On Dec 14, 2012, at 7:09 AM, John Nielsen wrote:
> Is there a
> parameter I can add to the GET requests that will lock the request to a
> specific node in the cluster, treating the server receiving the request as
> a standalone server as opposed to a member of a cluster?
The param dist=false w
an also use luke for this. It returns the same stats as in the
> interface:
> http://host:port/solr/corename/admin/luke
>
> -Original message-
> > From:John Nielsen
> > Sent: Fri 14-Dec-2012 13:16
> > To: solr-user@lucene.apache.org
> > Subject: Re: Str
s. It returns the same stats as in the interface:
http://host:port/solr/corename/admin/luke
-Original message-
> From:John Nielsen
> Sent: Fri 14-Dec-2012 13:16
> To: solr-user@lucene.apache.org
> Subject: Re: Strange data-loss problem on one of our cores
>
> I'm build
gt; Sent: Fri 14-Dec-2012 12:31
> > To: solr-user@lucene.apache.org
> > Subject: Re: Strange data-loss problem on one of our cores
> >
> > How did you solve the problem?
> >
> >
> > --
> > Med venlig hilsen / Best regards
> >
> > *J
We did not solve it but reindexing can remedy the problem.
-Original message-
> From:John Nielsen
> Sent: Fri 14-Dec-2012 12:31
> To: solr-user@lucene.apache.org
> Subject: Re: Strange data-loss problem on one of our cores
>
> How did you solve the problem?
>
ene.apache.org
> > Subject: Re: Strange data-loss problem on one of our cores
> >
> > I did a manual commit, and we are still missing docs, so it doesn't look
> > like the search race condition you mention.
> >
> > My boss wasn't happy when i mention
ne.apache.org
> Subject: Re: Strange data-loss problem on one of our cores
>
> I did a manual commit, and we are still missing docs, so it doesn't look
> like the search race condition you mention.
>
> My boss wasn't happy when i mentioned that I wanted to try out unrelease
I did a manual commit, and we are still missing docs, so it doesn't look
like the search race condition you mention.
My boss wasn't happy when i mentioned that I wanted to try out unreleased
code. Ill get him won over though and return with my findings. It will
probably be some time next week.
Th
Couple things to start:
By default SolrCloud distributes updates a doc at a time. So if you have 1
shard, whatever node you index too, it will send updates to the other.
Replication is only used for recovery, not distributing data. So for some
reason, there is an IOException when it tries to fo
Hi all,
We are seeing a strange problem on our 2-node solr4 cluster. This problem
has resultet in data loss.
We have two servers, varnish01 and varnish02. Zookeeper is running on
varnish02, but in a separate jvm.
We index directly to varnish02 and we read from varnish01. Data is thus
replicated
14 matches
Mail list logo
