Are we saying it has to do something with stop and restarting replica's
otherwise I haven't seen/heard any issues with document updates and
forwarding to replica's...
Thanks,
Susheel
On Thu, Nov 1, 2018 at 12:58 PM Erick Erickson
wrote:
> So this seems like it absolutely needs a JIRA
> On
So this seems like it absolutely needs a JIRA
On Thu, Nov 1, 2018 at 9:39 AM Kevin Risden wrote:
>
> I pushed 3 branches that modifies test.sh to test 5.5, 6.6, and 7.5 locally
> without docker. I still see the same behavior where the latest updates
> aren't on the replicas. I still don't kno
I pushed 3 branches that modifies test.sh to test 5.5, 6.6, and 7.5 locally
without docker. I still see the same behavior where the latest updates
aren't on the replicas. I still don't know what is happening but it happens
without Docker :(
https://github.com/risdenk/test-solr-start-stop-replica-c
Erick - Yea thats a fair point. Would be interesting to see if this fails
without Docker.
Kevin Risden
On Thu, Nov 1, 2018 at 11:06 AM Erick Erickson
wrote:
> Kevin:
>
> You're also using Docker, right? Docker is not "officially" supported
> although there's some movement in that direction and
Kevin:
You're also using Docker, right? Docker is not "officially" supported
although there's some movement in that direction and if this is only
reproducible in Docker than it's a clue where to look
Erick
On Wed, Oct 31, 2018 at 7:24 PM Kevin Risden wrote:
>
> I haven't dug into why this is
Could it be related to reloading a collection? I need to do some
testing, but it just occurred to me that reload was done at least once
during the period the cluster had been up.
Regards,
Ere
Ere Maijala kirjoitti 30.10.2018 klo 12.03:
Hi,
We had the same happen with PULL replicas with Solr
So I just added PRs 5.5, 6.6, 7.1, 7.2, 7.3, 7.4, and 7.5. They all seem to
have the exact same behavior... I don't have much more insight here but it
doesn't seem to be correct.
Kevin Risden
On Thu, Nov 1, 2018 at 9:45 AM Kevin Risden wrote:
> Ahhh your PR triggered an idea. I'll open a few P
Ahhh your PR triggered an idea. I'll open a few PRs adjusting the Solr
version from latest back to earlier 7.x versions. See which version the
problem was introduced in.
Kevin Risden
On Thu, Nov 1, 2018 at 9:17 AM Jeremy Smith wrote:
> Thanks so much for looking into this and cleaning up my c
Thanks so much for looking into this and cleaning up my code.
I added a pull request to show some additional strange behavior. If we restart
solr-1, making solr-2 the leader, the out of date value of [10] gets propagated
back to solr-1. Perhaps this will give a hint as to what is going on.
_
Thank you Erick and Daniel for your prompt responses. We were trying a few
things (moving to G1GC, optimizing by throwing away some fields that need
not be indexed & stored) and hence the late response.
First of all, thought of giving a overview of the environment... We have a
four node Solr Cloud
On Wed, 2018-10-31 at 13:42 +0200, Sofiya Strochyk wrote:
> q=&fl=&start=0&sort= expression>&fq=&rows=24&version=2.2&wt=json
Not much to see here, perhaps because you are not allowed to share it?
Maybe we can try and isolate the cause? Could you try different runs,
where you change different comp
Vadim,
Thanks for the suggestion.
For the test case, of spinning up solr 7.5 locally with the security.json
upload, I went ahead and tried to change both the request and response
header sizes as you mentioned and restarting.
Unfortunately, it does not seem to fix the issue for me. The error that
12 matches
Mail list logo
