You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Gian Maria Ricci - aka Alkampfer <al...@nablasoft.com> on 2016/01/11 16:08:42 UTC
WArning in SolrCloud logs
I’ve configured three node in solrcloud, everything seems ok, but in the log I see this kind of warning
SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style replication. Make sure you intend this behavior, it usually indicates a mis-configuration. Master setting is true and slave setting is false
What could be the reason? Is it possible that this happens because solrconfig.xml used to create the collection has a replication handler active?
--
Gian Maria Ricci
Cell: +39 320 0136949
<http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635> <http://www.linkedin.com/in/gianmariaricci> <https://twitter.com/alkampfer> <http://feeds.feedburner.com/AlkampferEng>
RE: WArning in SolrCloud logs
Posted by Gian Maria Ricci - aka Alkampfer <al...@nablasoft.com>.
Perfect, I'll remove the block and check if the warning will be gone.
Thanks.
--
Gian Maria Ricci
Cell: +39 320 0136949
-----Original Message-----
From: Alessandro Benedetti [mailto:abenedetti@apache.org]
Sent: martedì 12 gennaio 2016 10:43
To: solr-user@lucene.apache.org
Subject: Re: WArning in SolrCloud logs
To be honest, that block is not necessary anymore.
As Erick and Shawn were saying that is now implicit and defined by default.
Cheers
On 12 January 2016 at 08:22, Gian Maria Ricci - aka Alkampfer < alkampfer@nablasoft.com> wrote:
> THis is the replication handler configured in solrconfig.xml, there is
> nothing else regarding replication. This configuration is used for a
> single core test installation, then to experiment with SolrCloud I
> simply uploaded the very same configuration to SolrCloud. Do you think
> it could be the replicateAfter and backupAfter settings?
>
> This configuration was taken from an example that explained how to do
> backup to Solr Core with the replication handler.
>
>
> <requestHandler name="/replication"
> class="solr.ReplicationHandler">
> <lst name="master">
> <str name="replicateAfter">optimize</str>
> <str name="backupAfter">optimize</str>
> <str
> name="confFiles">schema.xml,stopwords.txt,elevate.xml</str>
> <str name="commitReserveDuration">00:00:10</str>
> </lst>
> <int name="maxNumberOfBackups">2</int>
> <lst name="invariants">
> <str name="maxWriteMBPerSec">64</str>
> </lst>
> </requestHandler>
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
>
>
> -----Original Message-----
> From: Erick Erickson [mailto:erickerickson@gmail.com]
> Sent: martedì 12 gennaio 2016 02:33
> To: solr-user <so...@lucene.apache.org>
> Subject: Re: WArning in SolrCloud logs
>
> Just show us the solrconfig.xml file, particularly any thing referring
> to replication, it's easier than talking past each other.
>
>
> Best,
> Erick.
>
> On Mon, Jan 11, 2016 at 12:18 PM, Gian Maria Ricci - aka Alkampfer <
> alkampfer@nablasoft.com> wrote:
> > Actually that is a collection I've created uploading into Zookeeper
> > a
> configuration I used for single node, with a replication handler
> activated to backup the core. I did not send any master/slave config
> actually, I just created the collection using collection API and the
> warning is immediately there.
> >
> > --
> > Gian Maria Ricci
> > Cell: +39 320 0136949
> >
> >
> >
> > -----Original Message-----
> > From: Alessandro Benedetti [mailto:abenedetti@apache.org]
> > Sent: lunedì 11 gennaio 2016 17:52
> > To: solr-user@lucene.apache.org
> > Subject: Re: WArning in SolrCloud logs
> >
> > To be honest it seems to me more a wrong usage of java environment
> variables.
> > Is it possible you are sending the enable master/slave config to the
> node ?
> > Strictly talking about the replication request handler, it is
> required for SolrCloud ( there are scenarios where old style
> replication is still used) .
> > But this supposes to happen automatically .
> >
> > Strip of code that cause the warning :
> >
> > if (enableMaster || enableSlave) {
> >> if (core.getCoreDescriptor().getCoreContainer().getZkController()
> >> !=
> >> null) { LOG.warn("SolrCloud is enabled for core " + core.getName() + "
> >> but so is old-style replication. Make sure you" + " intend this
> >> behavior, it usually indicates a mis-configuration. Master setting
> >> is " +
> >> Boolean.toString(enableMaster) + " and slave setting is " + Boolean.
> >> toString(enableSlave));
> >> }
> >> }
> >
> >
> > Cheers
> >
> > On 11 January 2016 at 15:08, Gian Maria Ricci - aka Alkampfer <
> alkampfer@nablasoft.com> wrote:
> >
> >> I’ve configured three node in solrcloud, everything seems ok, but
> >> in the log I see this kind of warning
> >>
> >>
> >>
> >> SolrCloud is enabled for core xxx_shard3_replica1 but so is
> >> old-style replication. Make sure you intend this behav
> ior, it usually indicates
> >> a mis-configuration. Master setting is true and slave setting is
> >> false
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> What could be the reason? Is it possible that this happens because
> >> solrconfig.xml used to create the collection has a replication
> >> handler active?
> >>
> >> --
> >> Gian Maria Ricci
> >> Cell: +39 320 0136949
> >>
> >> [image:
> >> https://ci5.googleusercontent.com/proxy/5oNMOYAeFXZ_LDKanNfoLRHC37m
> >> AZ
> >> k
> >> VVhkPN7QxMdA0K5JW2m0bm8azJe7oWZMNt8fKHNX1bzrUTd-kIyE40CmwT2Mlf8OI=s
> >> 0- d -e1-ft#http://www.codewrecks.com/files/signature/mvp.png]
> >> <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635>
> [image:
> >> https://ci3.googleusercontent.com/proxy/f-unQbmk6NtkHFspO5Y6x4jlIf_
> >> xr
> >> m
> >> GLUT3fU9y_7VUHSFUjLs7aUIMdZQYTh3eWIA0sBnvNX3WGXCU59chKXLuAHi2ArWdAc
> >> Bc
> >> l
> >> KA=s0-d-e1-ft#http://www.codewrecks.com/files/signature/linkedin.jp
> >> g] <http://www.linkedin.com/in/gianmariaricci> [image:
> >> https://ci3.googleusercontent.com/proxy/gjapMzu3KEakBQUstx_-cN7gHJ
> _Gpc
> >> IZNEPjCzOYMrPl-r1DViPE378qNAQyEWbXMTj6mcduIAGaApe9qHG1KN_hyFxQAIkdN
> >> SV T
> >> =s0-d-e1-ft#http://www.codewrecks.com/files/signature/twitter.jpg]
> >> <https://twitter.com/alkampfer> [image:
> >> https://ci5.googleusercontent.com/proxy/iuDOD2sdaxRDvTwS8MO7-CcXchp
> >> NJ
> >> X
> >> 96uaWuvagoVLcjpAPsJi88XeOonE4vHT6udVimo7yL9ZtdrYueEfH7jXnudmi_Vvw=s
> >> 0- d -e1-ft#http://www.codewrecks.com/files/signature/rss.jpg]
> >> <http://feeds.feedburner.com/AlkampferEng> [image:
> >> https://ci6.googleusercontent.com/proxy/EBJjfkBzcsSlAzlyR88y86YXcwa
> >> Kf
> >> n
> >> 3x7ydAObL1vtjJYclQr_l5TvrFx4PQ5qLNYW3yp7Ig66DJ-0tPJCDbDmYAFcamPQehw
> >> g= s 0-d-e1-ft#http://www.codewrecks.com/files/signature/skype.jpg]
> >>
> >>
> >>
> >
> >
> >
> > --
> > --------------------------
> >
> > Benedetti Alessandro
> > Visiting card : http://about.me/alessandro_benedetti
> >
> > "Tyger, tyger burning bright
> > In the forests of the night,
> > What immortal hand or eye
> > Could frame thy fearful symmetry?"
> >
> > William Blake - Songs of Experience -1794 England
>
--
--------------------------
Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti
"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"
William Blake - Songs of Experience -1794 England
Re: WArning in SolrCloud logs
Posted by Alessandro Benedetti <ab...@apache.org>.
To be honest, that block is not necessary anymore.
As Erick and Shawn were saying that is now implicit and defined by default.
Cheers
On 12 January 2016 at 08:22, Gian Maria Ricci - aka Alkampfer <
alkampfer@nablasoft.com> wrote:
> THis is the replication handler configured in solrconfig.xml, there is
> nothing else regarding replication. This configuration is used for a single
> core test installation, then to experiment with SolrCloud I simply uploaded
> the very same configuration to SolrCloud. Do you think it could be the
> replicateAfter and backupAfter settings?
>
> This configuration was taken from an example that explained how to do
> backup to Solr Core with the replication handler.
>
>
> <requestHandler name="/replication"
> class="solr.ReplicationHandler">
> <lst name="master">
> <str name="replicateAfter">optimize</str>
> <str name="backupAfter">optimize</str>
> <str
> name="confFiles">schema.xml,stopwords.txt,elevate.xml</str>
> <str name="commitReserveDuration">00:00:10</str>
> </lst>
> <int name="maxNumberOfBackups">2</int>
> <lst name="invariants">
> <str name="maxWriteMBPerSec">64</str>
> </lst>
> </requestHandler>
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
>
>
> -----Original Message-----
> From: Erick Erickson [mailto:erickerickson@gmail.com]
> Sent: martedì 12 gennaio 2016 02:33
> To: solr-user <so...@lucene.apache.org>
> Subject: Re: WArning in SolrCloud logs
>
> Just show us the solrconfig.xml file, particularly any thing referring to
> replication, it's easier than talking past each other.
>
>
> Best,
> Erick.
>
> On Mon, Jan 11, 2016 at 12:18 PM, Gian Maria Ricci - aka Alkampfer <
> alkampfer@nablasoft.com> wrote:
> > Actually that is a collection I've created uploading into Zookeeper a
> configuration I used for single node, with a replication handler activated
> to backup the core. I did not send any master/slave config actually, I just
> created the collection using collection API and the warning is immediately
> there.
> >
> > --
> > Gian Maria Ricci
> > Cell: +39 320 0136949
> >
> >
> >
> > -----Original Message-----
> > From: Alessandro Benedetti [mailto:abenedetti@apache.org]
> > Sent: lunedì 11 gennaio 2016 17:52
> > To: solr-user@lucene.apache.org
> > Subject: Re: WArning in SolrCloud logs
> >
> > To be honest it seems to me more a wrong usage of java environment
> variables.
> > Is it possible you are sending the enable master/slave config to the
> node ?
> > Strictly talking about the replication request handler, it is
> required for SolrCloud ( there are scenarios where old style replication
> is still used) .
> > But this supposes to happen automatically .
> >
> > Strip of code that cause the warning :
> >
> > if (enableMaster || enableSlave) {
> >> if (core.getCoreDescriptor().getCoreContainer().getZkController() !=
> >> null) { LOG.warn("SolrCloud is enabled for core " + core.getName() + "
> >> but so is old-style replication. Make sure you" + " intend this
> >> behavior, it usually indicates a mis-configuration. Master setting is
> >> " +
> >> Boolean.toString(enableMaster) + " and slave setting is " + Boolean.
> >> toString(enableSlave));
> >> }
> >> }
> >
> >
> > Cheers
> >
> > On 11 January 2016 at 15:08, Gian Maria Ricci - aka Alkampfer <
> alkampfer@nablasoft.com> wrote:
> >
> >> I’ve configured three node in solrcloud, everything seems ok, but in
> >> the log I see this kind of warning
> >>
> >>
> >>
> >> SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style
> >> replication. Make sure you intend this behav
> ior, it usually indicates
> >> a mis-configuration. Master setting is true and slave setting is
> >> false
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> What could be the reason? Is it possible that this happens because
> >> solrconfig.xml used to create the collection has a replication
> >> handler active?
> >>
> >> --
> >> Gian Maria Ricci
> >> Cell: +39 320 0136949
> >>
> >> [image:
> >> https://ci5.googleusercontent.com/proxy/5oNMOYAeFXZ_LDKanNfoLRHC37mAZ
> >> k
> >> VVhkPN7QxMdA0K5JW2m0bm8azJe7oWZMNt8fKHNX1bzrUTd-kIyE40CmwT2Mlf8OI=s0-
> >> d -e1-ft#http://www.codewrecks.com/files/signature/mvp.png]
> >> <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635>
> [image:
> >> https://ci3.googleusercontent.com/proxy/f-unQbmk6NtkHFspO5Y6x4jlIf_xr
> >> m
> >> GLUT3fU9y_7VUHSFUjLs7aUIMdZQYTh3eWIA0sBnvNX3WGXCU59chKXLuAHi2ArWdAcBc
> >> l
> >> KA=s0-d-e1-ft#http://www.codewrecks.com/files/signature/linkedin.jpg]
> >> <http://www.linkedin.com/in/gianmariaricci> [image:
> >> https://ci3.googleusercontent.com/proxy/gjapMzu3KEakBQUstx_-cN7gHJ
> _Gpc
> >> IZNEPjCzOYMrPl-r1DViPE378qNAQyEWbXMTj6mcduIAGaApe9qHG1KN_hyFxQAIkdNSV
> >> T =s0-d-e1-ft#http://www.codewrecks.com/files/signature/twitter.jpg]
> >> <https://twitter.com/alkampfer> [image:
> >> https://ci5.googleusercontent.com/proxy/iuDOD2sdaxRDvTwS8MO7-CcXchpNJ
> >> X
> >> 96uaWuvagoVLcjpAPsJi88XeOonE4vHT6udVimo7yL9ZtdrYueEfH7jXnudmi_Vvw=s0-
> >> d -e1-ft#http://www.codewrecks.com/files/signature/rss.jpg]
> >> <http://feeds.feedburner.com/AlkampferEng> [image:
> >> https://ci6.googleusercontent.com/proxy/EBJjfkBzcsSlAzlyR88y86YXcwaKf
> >> n
> >> 3x7ydAObL1vtjJYclQr_l5TvrFx4PQ5qLNYW3yp7Ig66DJ-0tPJCDbDmYAFcamPQehwg=
> >> s 0-d-e1-ft#http://www.codewrecks.com/files/signature/skype.jpg]
> >>
> >>
> >>
> >
> >
> >
> > --
> > --------------------------
> >
> > Benedetti Alessandro
> > Visiting card : http://about.me/alessandro_benedetti
> >
> > "Tyger, tyger burning bright
> > In the forests of the night,
> > What immortal hand or eye
> > Could frame thy fearful symmetry?"
> >
> > William Blake - Songs of Experience -1794 England
>
--
--------------------------
Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti
"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"
William Blake - Songs of Experience -1794 England
RE: WArning in SolrCloud logs
Posted by Gian Maria Ricci - aka Alkampfer <al...@nablasoft.com>.
THis is the replication handler configured in solrconfig.xml, there is nothing else regarding replication. This configuration is used for a single core test installation, then to experiment with SolrCloud I simply uploaded the very same configuration to SolrCloud. Do you think it could be the replicateAfter and backupAfter settings?
This configuration was taken from an example that explained how to do backup to Solr Core with the replication handler.
<requestHandler name="/replication" class="solr.ReplicationHandler">
<lst name="master">
<str name="replicateAfter">optimize</str>
<str name="backupAfter">optimize</str>
<str name="confFiles">schema.xml,stopwords.txt,elevate.xml</str>
<str name="commitReserveDuration">00:00:10</str>
</lst>
<int name="maxNumberOfBackups">2</int>
<lst name="invariants">
<str name="maxWriteMBPerSec">64</str>
</lst>
</requestHandler>
--
Gian Maria Ricci
Cell: +39 320 0136949
-----Original Message-----
From: Erick Erickson [mailto:erickerickson@gmail.com]
Sent: martedì 12 gennaio 2016 02:33
To: solr-user <so...@lucene.apache.org>
Subject: Re: WArning in SolrCloud logs
Just show us the solrconfig.xml file, particularly any thing referring to replication, it's easier than talking past each other.
Best,
Erick.
On Mon, Jan 11, 2016 at 12:18 PM, Gian Maria Ricci - aka Alkampfer <al...@nablasoft.com> wrote:
> Actually that is a collection I've created uploading into Zookeeper a configuration I used for single node, with a replication handler activated to backup the core. I did not send any master/slave config actually, I just created the collection using collection API and the warning is immediately there.
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
>
>
> -----Original Message-----
> From: Alessandro Benedetti [mailto:abenedetti@apache.org]
> Sent: lunedì 11 gennaio 2016 17:52
> To: solr-user@lucene.apache.org
> Subject: Re: WArning in SolrCloud logs
>
> To be honest it seems to me more a wrong usage of java environment variables.
> Is it possible you are sending the enable master/slave config to the node ?
> Strictly talking about the replication request handler, it is
required for SolrCloud ( there are scenarios where old style replication is still used) .
> But this supposes to happen automatically .
>
> Strip of code that cause the warning :
>
> if (enableMaster || enableSlave) {
>> if (core.getCoreDescriptor().getCoreContainer().getZkController() !=
>> null) { LOG.warn("SolrCloud is enabled for core " + core.getName() + "
>> but so is old-style replication. Make sure you" + " intend this
>> behavior, it usually indicates a mis-configuration. Master setting is
>> " +
>> Boolean.toString(enableMaster) + " and slave setting is " + Boolean.
>> toString(enableSlave));
>> }
>> }
>
>
> Cheers
>
> On 11 January 2016 at 15:08, Gian Maria Ricci - aka Alkampfer < alkampfer@nablasoft.com> wrote:
>
>> I’ve configured three node in solrcloud, everything seems ok, but in
>> the log I see this kind of warning
>>
>>
>>
>> SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style
>> replication. Make sure you intend this behav
ior, it usually indicates
>> a mis-configuration. Master setting is true and slave setting is
>> false
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> What could be the reason? Is it possible that this happens because
>> solrconfig.xml used to create the collection has a replication
>> handler active?
>>
>> --
>> Gian Maria Ricci
>> Cell: +39 320 0136949
>>
>> [image:
>> https://ci5.googleusercontent.com/proxy/5oNMOYAeFXZ_LDKanNfoLRHC37mAZ
>> k
>> VVhkPN7QxMdA0K5JW2m0bm8azJe7oWZMNt8fKHNX1bzrUTd-kIyE40CmwT2Mlf8OI=s0-
>> d -e1-ft#http://www.codewrecks.com/files/signature/mvp.png]
>> <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635> [image:
>> https://ci3.googleusercontent.com/proxy/f-unQbmk6NtkHFspO5Y6x4jlIf_xr
>> m
>> GLUT3fU9y_7VUHSFUjLs7aUIMdZQYTh3eWIA0sBnvNX3WGXCU59chKXLuAHi2ArWdAcBc
>> l
>> KA=s0-d-e1-ft#http://www.codewrecks.com/files/signature/linkedin.jpg]
>> <http://www.linkedin.com/in/gianmariaricci> [image:
>> https://ci3.googleusercontent.com/proxy/gjapMzu3KEakBQUstx_-cN7gHJ
_Gpc
>> IZNEPjCzOYMrPl-r1DViPE378qNAQyEWbXMTj6mcduIAGaApe9qHG1KN_hyFxQAIkdNSV
>> T =s0-d-e1-ft#http://www.codewrecks.com/files/signature/twitter.jpg]
>> <https://twitter.com/alkampfer> [image:
>> https://ci5.googleusercontent.com/proxy/iuDOD2sdaxRDvTwS8MO7-CcXchpNJ
>> X
>> 96uaWuvagoVLcjpAPsJi88XeOonE4vHT6udVimo7yL9ZtdrYueEfH7jXnudmi_Vvw=s0-
>> d -e1-ft#http://www.codewrecks.com/files/signature/rss.jpg]
>> <http://feeds.feedburner.com/AlkampferEng> [image:
>> https://ci6.googleusercontent.com/proxy/EBJjfkBzcsSlAzlyR88y86YXcwaKf
>> n
>> 3x7ydAObL1vtjJYclQr_l5TvrFx4PQ5qLNYW3yp7Ig66DJ-0tPJCDbDmYAFcamPQehwg=
>> s 0-d-e1-ft#http://www.codewrecks.com/files/signature/skype.jpg]
>>
>>
>>
>
>
>
> --
> --------------------------
>
> Benedetti Alessandro
> Visiting card : http://about.me/alessandro_benedetti
>
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
>
> William Blake - Songs of Experience -1794 England
Re: WArning in SolrCloud logs
Posted by Erick Erickson <er...@gmail.com>.
Just show us the solrconfig.xml file, particularly anything referring
to replication,
it's easier than talking past each other.
Best,
Erick.
On Mon, Jan 11, 2016 at 12:18 PM, Gian Maria Ricci - aka Alkampfer
<al...@nablasoft.com> wrote:
> Actually that is a collection I've created uploading into Zookeeper a configuration I used for single node, with a replication handler activated to backup the core. I did not send any master/slave config actually, I just created the collection using collection API and the warning is immediately there.
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
>
>
> -----Original Message-----
> From: Alessandro Benedetti [mailto:abenedetti@apache.org]
> Sent: lunedì 11 gennaio 2016 17:52
> To: solr-user@lucene.apache.org
> Subject: Re: WArning in SolrCloud logs
>
> To be honest it seems to me more a wrong usage of java environment variables.
> Is it possible you are sending the enable master/slave config to the node ?
> Strictly talking about the replication request handler, it is required for SolrCloud ( there are scenarios where old style replication is still used) .
> But this supposes to happen automatically .
>
> Strip of code that cause the warning :
>
> if (enableMaster || enableSlave) {
>> if (core.getCoreDescriptor().getCoreContainer().getZkController() !=
>> null) { LOG.warn("SolrCloud is enabled for core " + core.getName() + "
>> but so is old-style replication. Make sure you" + " intend this
>> behavior, it usually indicates a mis-configuration. Master setting is
>> " +
>> Boolean.toString(enableMaster) + " and slave setting is " + Boolean.
>> toString(enableSlave));
>> }
>> }
>
>
> Cheers
>
> On 11 January 2016 at 15:08, Gian Maria Ricci - aka Alkampfer < alkampfer@nablasoft.com> wrote:
>
>> I’ve configured three node in solrcloud, everything seems ok, but in
>> the log I see this kind of warning
>>
>>
>>
>> SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style
>> replication. Make sure you intend this behavior, it usually indicates
>> a mis-configuration. Master setting is true and slave setting is false
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> What could be the reason? Is it possible that this happens because
>> solrconfig.xml used to create the collection has a replication handler
>> active?
>>
>> --
>> Gian Maria Ricci
>> Cell: +39 320 0136949
>>
>> [image:
>> https://ci5.googleusercontent.com/proxy/5oNMOYAeFXZ_LDKanNfoLRHC37mAZk
>> VVhkPN7QxMdA0K5JW2m0bm8azJe7oWZMNt8fKHNX1bzrUTd-kIyE40CmwT2Mlf8OI=s0-d
>> -e1-ft#http://www.codewrecks.com/files/signature/mvp.png]
>> <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635> [image:
>> https://ci3.googleusercontent.com/proxy/f-unQbmk6NtkHFspO5Y6x4jlIf_xrm
>> GLUT3fU9y_7VUHSFUjLs7aUIMdZQYTh3eWIA0sBnvNX3WGXCU59chKXLuAHi2ArWdAcBcl
>> KA=s0-d-e1-ft#http://www.codewrecks.com/files/signature/linkedin.jpg]
>> <http://www.linkedin.com/in/gianmariaricci> [image:
>> https://ci3.googleusercontent.com/proxy/gjapMzu3KEakBQUstx_-cN7gHJ_Gpc
>> IZNEPjCzOYMrPl-r1DViPE378qNAQyEWbXMTj6mcduIAGaApe9qHG1KN_hyFxQAIkdNSVT
>> =s0-d-e1-ft#http://www.codewrecks.com/files/signature/twitter.jpg]
>> <https://twitter.com/alkampfer> [image:
>> https://ci5.googleusercontent.com/proxy/iuDOD2sdaxRDvTwS8MO7-CcXchpNJX
>> 96uaWuvagoVLcjpAPsJi88XeOonE4vHT6udVimo7yL9ZtdrYueEfH7jXnudmi_Vvw=s0-d
>> -e1-ft#http://www.codewrecks.com/files/signature/rss.jpg]
>> <http://feeds.feedburner.com/AlkampferEng> [image:
>> https://ci6.googleusercontent.com/proxy/EBJjfkBzcsSlAzlyR88y86YXcwaKfn
>> 3x7ydAObL1vtjJYclQr_l5TvrFx4PQ5qLNYW3yp7Ig66DJ-0tPJCDbDmYAFcamPQehwg=s
>> 0-d-e1-ft#http://www.codewrecks.com/files/signature/skype.jpg]
>>
>>
>>
>
>
>
> --
> --------------------------
>
> Benedetti Alessandro
> Visiting card : http://about.me/alessandro_benedetti
>
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
>
> William Blake - Songs of Experience -1794 England
RE: WArning in SolrCloud logs
Posted by Gian Maria Ricci - aka Alkampfer <al...@nablasoft.com>.
Actually that is a collection I've created uploading into Zookeeper a configuration I used for single node, with a replication handler activated to backup the core. I did not send any master/slave config actually, I just created the collection using collection API and the warning is immediately there.
--
Gian Maria Ricci
Cell: +39 320 0136949
-----Original Message-----
From: Alessandro Benedetti [mailto:abenedetti@apache.org]
Sent: lunedì 11 gennaio 2016 17:52
To: solr-user@lucene.apache.org
Subject: Re: WArning in SolrCloud logs
To be honest it seems to me more a wrong usage of java environment variables.
Is it possible you are sending the enable master/slave config to the node ?
Strictly talking about the replication request handler, it is required for SolrCloud ( there are scenarios where old style replication is still used) .
But this supposes to happen automatically .
Strip of code that cause the warning :
if (enableMaster || enableSlave) {
> if (core.getCoreDescriptor().getCoreContainer().getZkController() !=
> null) { LOG.warn("SolrCloud is enabled for core " + core.getName() + "
> but so is old-style replication. Make sure you" + " intend this
> behavior, it usually indicates a mis-configuration. Master setting is
> " +
> Boolean.toString(enableMaster) + " and slave setting is " + Boolean.
> toString(enableSlave));
> }
> }
Cheers
On 11 January 2016 at 15:08, Gian Maria Ricci - aka Alkampfer < alkampfer@nablasoft.com> wrote:
> I’ve configured three node in solrcloud, everything seems ok, but in
> the log I see this kind of warning
>
>
>
> SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style
> replication. Make sure you intend this behavior, it usually indicates
> a mis-configuration. Master setting is true and slave setting is false
>
>
>
>
>
>
>
>
>
>
>
> What could be the reason? Is it possible that this happens because
> solrconfig.xml used to create the collection has a replication handler
> active?
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
> [image:
> https://ci5.googleusercontent.com/proxy/5oNMOYAeFXZ_LDKanNfoLRHC37mAZk
> VVhkPN7QxMdA0K5JW2m0bm8azJe7oWZMNt8fKHNX1bzrUTd-kIyE40CmwT2Mlf8OI=s0-d
> -e1-ft#http://www.codewrecks.com/files/signature/mvp.png]
> <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635> [image:
> https://ci3.googleusercontent.com/proxy/f-unQbmk6NtkHFspO5Y6x4jlIf_xrm
> GLUT3fU9y_7VUHSFUjLs7aUIMdZQYTh3eWIA0sBnvNX3WGXCU59chKXLuAHi2ArWdAcBcl
> KA=s0-d-e1-ft#http://www.codewrecks.com/files/signature/linkedin.jpg]
> <http://www.linkedin.com/in/gianmariaricci> [image:
> https://ci3.googleusercontent.com/proxy/gjapMzu3KEakBQUstx_-cN7gHJ_Gpc
> IZNEPjCzOYMrPl-r1DViPE378qNAQyEWbXMTj6mcduIAGaApe9qHG1KN_hyFxQAIkdNSVT
> =s0-d-e1-ft#http://www.codewrecks.com/files/signature/twitter.jpg]
> <https://twitter.com/alkampfer> [image:
> https://ci5.googleusercontent.com/proxy/iuDOD2sdaxRDvTwS8MO7-CcXchpNJX
> 96uaWuvagoVLcjpAPsJi88XeOonE4vHT6udVimo7yL9ZtdrYueEfH7jXnudmi_Vvw=s0-d
> -e1-ft#http://www.codewrecks.com/files/signature/rss.jpg]
> <http://feeds.feedburner.com/AlkampferEng> [image:
> https://ci6.googleusercontent.com/proxy/EBJjfkBzcsSlAzlyR88y86YXcwaKfn
> 3x7ydAObL1vtjJYclQr_l5TvrFx4PQ5qLNYW3yp7Ig66DJ-0tPJCDbDmYAFcamPQehwg=s
> 0-d-e1-ft#http://www.codewrecks.com/files/signature/skype.jpg]
>
>
>
--
--------------------------
Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti
"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"
William Blake - Songs of Experience -1794 England
Re: WArning in SolrCloud logs
Posted by Alessandro Benedetti <ab...@apache.org>.
To be honest it seems to me more a wrong usage of java environment
variables.
Is it possible you are sending the enable master/slave config to the node ?
Strictly talking about the replication request handler, it is required for
SolrCloud ( there are scenarios where old style replication is still used) .
But this supposes to happen automatically .
Strip of code that cause the warning :
if (enableMaster || enableSlave) {
> if (core.getCoreDescriptor().getCoreContainer().getZkController() != null)
> {
> LOG.warn("SolrCloud is enabled for core " + core.getName() + " but so is
> old-style replication. Make sure you" +
> " intend this behavior, it usually indicates a mis-configuration. Master
> setting is " +
> Boolean.toString(enableMaster) + " and slave setting is " + Boolean.
> toString(enableSlave));
> }
> }
Cheers
On 11 January 2016 at 15:08, Gian Maria Ricci - aka Alkampfer <
alkampfer@nablasoft.com> wrote:
> I’ve configured three node in solrcloud, everything seems ok, but in the
> log I see this kind of warning
>
>
>
> SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style
> replication. Make sure you intend this behavior, it usually indicates a
> mis-configuration. Master setting is true and slave setting is false
>
>
>
>
>
>
>
>
>
>
>
> What could be the reason? Is it possible that this happens because
> solrconfig.xml used to create the collection has a replication handler
> active?
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
> [image:
> https://ci5.googleusercontent.com/proxy/5oNMOYAeFXZ_LDKanNfoLRHC37mAZkVVhkPN7QxMdA0K5JW2m0bm8azJe7oWZMNt8fKHNX1bzrUTd-kIyE40CmwT2Mlf8OI=s0-d-e1-ft#http://www.codewrecks.com/files/signature/mvp.png]
> <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635> [image:
> https://ci3.googleusercontent.com/proxy/f-unQbmk6NtkHFspO5Y6x4jlIf_xrmGLUT3fU9y_7VUHSFUjLs7aUIMdZQYTh3eWIA0sBnvNX3WGXCU59chKXLuAHi2ArWdAcBclKA=s0-d-e1-ft#http://www.codewrecks.com/files/signature/linkedin.jpg]
> <http://www.linkedin.com/in/gianmariaricci> [image:
> https://ci3.googleusercontent.com/proxy/gjapMzu3KEakBQUstx_-cN7gHJ_GpcIZNEPjCzOYMrPl-r1DViPE378qNAQyEWbXMTj6mcduIAGaApe9qHG1KN_hyFxQAIkdNSVT=s0-d-e1-ft#http://www.codewrecks.com/files/signature/twitter.jpg]
> <https://twitter.com/alkampfer> [image:
> https://ci5.googleusercontent.com/proxy/iuDOD2sdaxRDvTwS8MO7-CcXchpNJX96uaWuvagoVLcjpAPsJi88XeOonE4vHT6udVimo7yL9ZtdrYueEfH7jXnudmi_Vvw=s0-d-e1-ft#http://www.codewrecks.com/files/signature/rss.jpg]
> <http://feeds.feedburner.com/AlkampferEng> [image:
> https://ci6.googleusercontent.com/proxy/EBJjfkBzcsSlAzlyR88y86YXcwaKfn3x7ydAObL1vtjJYclQr_l5TvrFx4PQ5qLNYW3yp7Ig66DJ-0tPJCDbDmYAFcamPQehwg=s0-d-e1-ft#http://www.codewrecks.com/files/signature/skype.jpg]
>
>
>
--
--------------------------
Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti
"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"
William Blake - Songs of Experience -1794 England
Re: WArning in SolrCloud logs
Posted by Shawn Heisey <ap...@elyograg.org>.
On 1/11/2016 8:08 AM, Gian Maria Ricci - aka Alkampfer wrote:
>
> I've configured three node in solrcloud, everything seems ok, but in
> the log I see this kind of warning
>
>
>
> SolrCloud is enabled for core xxx_shard3_replica1 but so is old-style
> replication. Make sure you intend this behavior, it usually indicates
> a mis-configuration. Master setting is true and slave setting is false
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> What could be the reason? Is it possible that this happens because
> solrconfig.xml used to create the collection has a replication handler
> active?
>
The message is being logged because the solrconfig.xml file for the
collection includes an explicit replication handler definition, most
likely with a name of "/replication". If your Solr version is new
enough, you do not need to define the replication handler in your
configuration -- it will be automatically configured.
The message is a warning. If SolrCloud is working, then you can put it
on a list to look at later ... but be sure you DO look at it later, and
remove the explicit config once you're on a new enough version. I think
5.0 includes the implicit handlers, so any 5.x version is new enough.
The configs included with 5.x would not have this handler, so I think
you must be using configs based on examples for an older version of Solr.
Thanks,
Shawn