Nothing in the logs it's like it didn't happen.
So I think I need to address my logging levels log4j
On Tue, Jun 5, 2018, 12:35 AM Jeff Courtade wrote:
> Yes unix.
>
> It was an amazing moment.
>
>
>
> On Mon, Jun 4, 2018, 11:28 PM Erick Erickson
> wrote:
>
>> bq. To be clear I deleted the
Yes unix.
It was an amazing moment.
On Mon, Jun 4, 2018, 11:28 PM Erick Erickson
wrote:
> bq. To be clear I deleted the actual index files out from under the
> running master
>
> I'm assuming *nix here since Windows won't let you delete a file that
> has an open file handle...
>
> Did you the
bq. To be clear I deleted the actual index files out from under the
running master
I'm assuming *nix here since Windows won't let you delete a file that
has an open file handle...
Did you then restart the master? Aside from any checks about refusing
to replicate an empty index, just deleting the
Check the logs. I bet it says something like “refusing to fetch empty index.”
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jun 4, 2018, at 1:41 PM, Jeff Courtade wrote:
>
> I am thankful for that!
>
> Could you point me at something that explain
I am thankful for that!
Could you point me at something that explains this maybe?
J
On Mon, Jun 4, 2018, 4:31 PM Shawn Heisey wrote:
> On 6/4/2018 12:15 PM, Jeff Courtade wrote:
> > This was strange as I would have thought the replica would have
> replicated
> > an empty index from the master.
On 6/4/2018 12:15 PM, Jeff Courtade wrote:
> This was strange as I would have thought the replica would have replicated
> an empty index from the master.
Solr actually has protections in place to specifically PREVENT index
replication when the master has an empty index. This is so that a
accident
This is what I thought too.
It happened on all 5 really weird behavior. I entirely expected blank
indexes on the replica
On Mon, Jun 4, 2018, 2:38 PM Aman Tandon wrote:
> Hi Jeff,
>
> I suppose there should be slave configuration in solrconfig files which
> says to ping master to check for the
Hi Jeff,
I suppose there should be slave configuration in solrconfig files which
says to ping master to check for the version and get the modified files.
If replication is configured in slave you will see commands getting
triggered and you could get some idea from there.
Also you could paste tha
To be clear I deleted the actual index files out from under the running
master
On Mon, Jun 4, 2018, 2:25 PM Jeff Courtade wrote:
> So are you saying it should have?
>
> It really acted like a normal function this happened on 5 different pairs
> in the same way.
>
>
> On Mon, Jun 4, 2018, 2:23 PM
So are you saying it should have?
It really acted like a normal function this happened on 5 different pairs
in the same way.
On Mon, Jun 4, 2018, 2:23 PM Aman Tandon wrote:
> Could you please check the replication request commands in solr logs of
> slave and see if it is complaining anything.
>
Could you please check the replication request commands in solr logs of
slave and see if it is complaining anything.
On Mon, Jun 4, 2018, 23:45 Jeff Courtade wrote:
> Hi,
>
> This I think is a very simple question.
>
> I have a solr 4.3 master slave setup.
>
> Simple replication.
>
> The master
Hi,
This I think is a very simple question.
I have a solr 4.3 master slave setup.
Simple replication.
The master and slave were both running and synchronized up to date
I went on the master and deleted the index files while solr was running.
solr created new empty index files and continued to
12 matches
Mail list logo
