lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abdel Belkasri <belka...@gmail.com>
Subject Re: Need Help with Solr 6.0 Cross Data Center Replication
Date Mon, 16 May 2016 16:29:54 GMT
Thanks Renaud.

Here is my setup:

1- I have created 2 sites: Main (source) and DR (traget).
2- Both sites are the same before configuring CDCR
3- The collections (source and target) are created before configuring CDCR
4- collections are created using interactive mode: accepting most defaults
except the ports (gettingstarted collection)
5- I have a zookeeper ensemble too.
6- I change the solrconfig.xml, then I upload using the command:
# upload configset to zookeeper
zkcli.bat -cmd upconfig -zkhost  localhost:2181 -confname gettingstarted
-solrhome C:\solr\solr-6-cloud\solr-6.0.0 -confdir
C:\solr\solr-6-cloud\solr-6.0.0\server\solr\configsets\basic_configs\conf

Renaud can you send your confi files...

Thanks,
--Abdel.

On Mon, May 16, 2016 at 12:16 PM, Satvinder Singh <Satvinder.Singh@nc4.com>
wrote:

> Thank you.
>
> To summarize this is what I have, all VMS running on Centos7 :----
>
> Source Side
>         |___ 1 VM running 3 Zookeeper instances on port 2181, 2182 and
> 2183 (ZOOKEEPER 3.4.8)(Java 1.8.0_91)
>         |___ 1 VM running 2 solr 6.0 instances on port 8501, 8502 (Solr
> 6.0) (Java 1.8.0_91)
>         |___ sample_techproducts_config copied as 'liferay', and used to
> create collections, that is where I am
>  modifying the solrconfig.xml
>
>
> Target Side
>         |___ 1 VM running 3 Zookeeper instances on port 2181, 2182 and
> 2183 (ZOOKEEPER 3.4.8)(Java 1.8.0_91)
>         |___ 1 VM running 2 solr 6.0 instances on port 8501, 8502 (Solr
> 6.0) (Java 1.8.0_91)
>         |___ sample_techproducts_config copied as 'liferay', and used to
> create collections, that is where I am
>  modifying the solrconfig.xml
>
>
> Thanks
> Satvinder Singh
> Security Systems Engineer
> Satvinder.Singh@NC4.com
> 703.682.6000 x276 direct
> 703.989.8030 cell
> www.NC4.com
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Renaud Delbru [mailto:renaud@siren.solutions]
> Sent: Monday, May 16, 2016 11:59 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Need Help with Solr 6.0 Cross Data Center Replication
>
> Thanks Satvinder,
> Tomorrow, I'll try to reproduce the issue with your steps and will let you
> know.
>
> Regards
> --
> Renaud Delbru
>
> On 16/05/16 16:53, Satvinder Singh wrote:
> > Hi,
> >
> > So the way I am doing it is, for both for the Target and Source side, I
> took a copy of the sample_techproducts_config configset, can created one
> configset. Then I modified the solrconfig.xml in there, both for the Target
> and Source side. And then created the collection, and I get the errors. I
> get the error if I create a new collection or try to reload an existing
> collection after the solrconfig update.
> > Attached is the log and configs.
> > Thanks
> >
> > Satvinder Singh
> >
> >
> >
> > Security Systems Engineer
> > Satvinder.Singh@NC4.com
> > 703.682.6000 x276 direct
> > 703.989.8030 cell
> > www.NC4.com
> >
> >
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Renaud Delbru [mailto:renaud@siren.solutions]
> > Sent: Monday, May 16, 2016 11:45 AM
> > To: solr-user@lucene.apache.org
> > Subject: Re: Need Help with Solr 6.0 Cross Data Center Replication
> >
> > Hi,
> >
> > I have tried to reproduce the problem, but was unable to.
> > I have downloaded the Solr 6.0 distribution, added to the solr config
> the cdcr request handler and modified the update handler to register the
> CdcrUpdateLog, then start Solr in cloud mode and created a new collection
> using my solr config. The cdcr request handler starts properly and does not
> complain about the update log.
> >
> > Could you provide more background on how to reproduce the issue ? E.g.,
> how do you create a new collection with the cdcr configuration.
> > Are you trying to configure CDCR on collections that were created prior
> to the CDCR configuration ?
> >
> > @Erik: I have noticed a small issue in the CDCR page of the reference
> guide. In the code snippet in Configuration -> Source Configuration, the
> <updateHandler> element is nested within the <requestHandler>.
> >
> > Thanks
> > Regards
> > --
> > Renaud Delbru
> >
> > On 15/05/16 23:13, Abdel Belkasri wrote:
> >> Erick,
> >>
> >> I tried the new configuration. The same issue that Satvinder is
> >> having. The log updater cannot be instantiated...
> >>
> >> class="solr.CdcrUpdateLog"
> >>
> >> for some reason that class is causing a problem!
> >>
> >> Anyway, anyone has a config that works?
> >>
> >> Regards,
> >> --Abdel
> >>
> >> On Fri, May 13, 2016 at 11:57 AM, Erick Erickson
> >> <erickerickson@gmail.com>
> >> wrote:
> >>
> >>> I changed the CDCR doc, Oliver could you take a glance and see if it
> >>> is clear now? All I changed was the sample solrconfig sections....
> >>>
> >>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=626
> >>> 8
> >>> 7462
> >>>
> >>> Thanks,
> >>> Erick
> >>>
> >>> On Fri, May 13, 2016 at 6:23 AM, Oliver Rudolph
> >>> <Oliver.Rudolph@de.ibm.com> wrote:
> >>>> Hi,
> >>>>
> >>>> I had the same problem. The documentation is kind of missleading here.
> >>> You
> >>>> must not add a new <updateHandler> element to your config but
> >>>> update the existing <updateHandler>. All you need to do is add
the
> >>>> class="solr.CdcrUpdateLog" element to the <updateLog> element
> >>>> inside your existing <updateHandler>. Hope this helps!
> >>>>
> >>>>
> >>>> Mit freundlichen Grüßen / Kind regards
> >>>>
> >>>> Oliver Rudolph
> >>>>
> >>>> IBM Deutschland Research & Development GmbH Vorsitzender des
> >>>> Aufsichtsrats: Martina Koederitz
> >>>> Geschäftsführung: Dirk Wittkopp
> >>>> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht
> >>> Stuttgart,
> >>>> HRB 243294
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >
> > Disclaimer: This message is intended only for the use of the individual
> or entity to which it is addressed and may contain information which is
> privileged, confidential, proprietary, or exempt from disclosure under
> applicable law. If you are not the intended recipient or the person
> responsible for delivering the message to the intended recipient, you are
> strictly prohibited from disclosing, distributing, copying, or in any way
> using this message. If you have received this communication in error,
> please notify the sender and destroy and delete any copies you may have
> received.
> >
>
>


-- 
Abdel K. Belkasri, PhD

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message