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 Jared Griffith <jg...@picsauditing.com> on 2013/09/03 18:12:05 UTC
Re: SolrCloud Set up
I think I have it all sorted out. There are some weird network issues here
where my test set up is, so that may have been part of the over all issue.
Timeouts wouldn't have fixed this issue, that's for sure.
On Sat, Aug 31, 2013 at 7:17 AM, Erick Erickson <er...@gmail.com>wrote:
> bq: Though I am seeing some funkiness that I wasn't seeing with Solr &
> Zookeeper running together
>
> Then I suspect you've set something up inconsistently, _or_ you need to
> extend some timeouts because SolrCloud is being run with separate ZKs by
> quite a few people so I'd be surprised if it were anything except config
> issues.
>
> If you _do_ uncover something in that realm other than timeouts and such,
> we need to know....
>
> Best,
> Erick
>
>
>
>
> On Fri, Aug 30, 2013 at 2:15 PM, Jared Griffith
> <jg...@picsauditing.com>wrote:
>
> > That's what I was thinking. Though I am seeing some funkiness that I
> > wasn't seeing with Solr & Zookeeper running together.
> >
> >
> > On Fri, Aug 30, 2013 at 9:40 AM, Shawn Heisey <so...@elyograg.org> wrote:
> >
> > > On 8/30/2013 9:43 AM, Jared Griffith wrote:
> > >
> > >> One last thing. Is there any real benefit in running SolrCloud and
> > >> Zookeeper separate? I am seeing some funkiness with the separation
> of
> > >> the
> > >> two, funkiness I wasn't seeing when running SolrCloud + Zookeeper
> > together
> > >> as outlined in the Wiki.
> > >>
> > >
> > > For a robust install, you want zookeeper to be a separate process. It
> > can
> > > run on the same server as Solr, but the embedded zookeeper (-DzkRun)
> > should
> > > not be used except for dev and proof of concept work.
> > >
> > > The reason is simple. Zookeeper is the central coordinator for
> > SolrCloud.
> > > In order for it to remain stable, it should not be restarted without
> > good
> > > reason. If you are running zookeeper as part of Solr, then you will be
> > > affecting zookeeper operation anytime you restart that instance of
> Solr.
> > >
> > > Making changes to your Solr setup often requires that you restart Solr.
> > > This includes upgrading Solr and changing some aspects of its
> > > configuration. Some configuration aspects can be changed with just a
> > > collection reload, but others require a full application restart.
> > >
> > > Thanks,
> > > Shawn
> > >
> > >
> >
> >
> > --
> >
> > Jared Griffith
> > Linux Administrator, PICS Auditing, LLC
> > P: (949) 936-4574
> > C: (909) 653-7814
> >
> > <http://www.picsauditing.com>
> >
> > 17701 Cowan #140 | Irvine, CA | 92614
> >
> > Join PICS on LinkedIn and Twitter!
> >
> > <https://twitter.com/PICSAuditingLLC>
> >
>
--
Jared Griffith
Linux Administrator, PICS Auditing, LLC
P: (949) 936-4574
C: (909) 653-7814
<http://www.picsauditing.com>
17701 Cowan #140 | Irvine, CA | 92614
Join PICS on LinkedIn and Twitter!
<https://twitter.com/PICSAuditingLLC>
Re: SolrCloud Set up
Posted by Erick Erickson <er...@gmail.com>.
Yep, that's the one, thanks...
On Tue, Sep 3, 2013 at 1:38 PM, Walter Underwood <wu...@wunderwood.org>wrote:
> Those are the Fallacies of Distributed Computing from L. Peter Deutsch.
> The first fallacy is "The network is reliable."
>
> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing
>
> wunder
>
> On Sep 3, 2013, at 10:26 AM, Erick Erickson wrote:
>
> > Ah, thanks for the closure, it's always nice to know. I used to work
> > with a guy who had a list of "network fallacies", that amounted to
> > "you can't trust them fully"....
> >
> > Erick
> >
> >
> > On Tue, Sep 3, 2013 at 12:12 PM, Jared Griffith
> > <jg...@picsauditing.com>wrote:
> >
> >> I think I have it all sorted out. There are some weird network issues
> here
> >> where my test set up is, so that may have been part of the over all
> issue.
> >> Timeouts wouldn't have fixed this issue, that's for sure.
> >>
> >>
> >> On Sat, Aug 31, 2013 at 7:17 AM, Erick Erickson <
> erickerickson@gmail.com
> >>> wrote:
> >>
> >>> bq: Though I am seeing some funkiness that I wasn't seeing with Solr &
> >>> Zookeeper running together
> >>>
> >>> Then I suspect you've set something up inconsistently, _or_ you need to
> >>> extend some timeouts because SolrCloud is being run with separate ZKs
> by
> >>> quite a few people so I'd be surprised if it were anything except
> config
> >>> issues.
> >>>
> >>> If you _do_ uncover something in that realm other than timeouts and
> such,
> >>> we need to know....
> >>>
> >>> Best,
> >>> Erick
> >>>
> >>>
> >>>
> >>>
> >>> On Fri, Aug 30, 2013 at 2:15 PM, Jared Griffith
> >>> <jg...@picsauditing.com>wrote:
> >>>
> >>>> That's what I was thinking. Though I am seeing some funkiness that I
> >>>> wasn't seeing with Solr & Zookeeper running together.
> >>>>
> >>>>
> >>>> On Fri, Aug 30, 2013 at 9:40 AM, Shawn Heisey <so...@elyograg.org>
> >> wrote:
> >>>>
> >>>>> On 8/30/2013 9:43 AM, Jared Griffith wrote:
> >>>>>
> >>>>>> One last thing. Is there any real benefit in running SolrCloud and
> >>>>>> Zookeeper separate? I am seeing some funkiness with the separation
> >>> of
> >>>>>> the
> >>>>>> two, funkiness I wasn't seeing when running SolrCloud + Zookeeper
> >>>> together
> >>>>>> as outlined in the Wiki.
> >>>>>>
> >>>>>
> >>>>> For a robust install, you want zookeeper to be a separate process.
> >> It
> >>>> can
> >>>>> run on the same server as Solr, but the embedded zookeeper (-DzkRun)
> >>>> should
> >>>>> not be used except for dev and proof of concept work.
> >>>>>
> >>>>> The reason is simple. Zookeeper is the central coordinator for
> >>>> SolrCloud.
> >>>>> In order for it to remain stable, it should not be restarted without
> >>>> good
> >>>>> reason. If you are running zookeeper as part of Solr, then you will
> >> be
> >>>>> affecting zookeeper operation anytime you restart that instance of
> >>> Solr.
> >>>>>
> >>>>> Making changes to your Solr setup often requires that you restart
> >> Solr.
> >>>>> This includes upgrading Solr and changing some aspects of its
> >>>>> configuration. Some configuration aspects can be changed with just a
> >>>>> collection reload, but others require a full application restart.
> >>>>>
> >>>>> Thanks,
> >>>>> Shawn
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Jared Griffith
> >>>> Linux Administrator, PICS Auditing, LLC
> >>>> P: (949) 936-4574
> >>>> C: (909) 653-7814
> >>>>
> >>>> <http://www.picsauditing.com>
> >>>>
> >>>> 17701 Cowan #140 | Irvine, CA | 92614
> >>>>
> >>>> Join PICS on LinkedIn and Twitter!
> >>>>
> >>>> <https://twitter.com/PICSAuditingLLC>
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Jared Griffith
> >> Linux Administrator, PICS Auditing, LLC
> >> P: (949) 936-4574
> >> C: (909) 653-7814
> >>
> >> <http://www.picsauditing.com>
> >>
> >> 17701 Cowan #140 | Irvine, CA | 92614
> >>
> >> Join PICS on LinkedIn and Twitter!
> >>
> >> <https://twitter.com/PICSAuditingLLC>
> >>
>
> --
> Walter Underwood
> wunder@wunderwood.org
>
>
>
>
Re: SolrCloud Set up
Posted by Jared Griffith <jg...@picsauditing.com>.
Thankfully it's none of those but more than likely a bad DHCP server
(Windows) or client (or combo there of) that is causing the network to
freak out. I'll try adjusting the timeouts up to see if it will alleviate
this.
I am seeing that when I try to restart the solr instances sometimes they
seem to not join the cluster at all (nothing in the logs about issues).
Even after restarting the nodes that are reporting down a couple of times,
they never join the cluster again.
I have 3 zookeeper instances on 3 separate physical machines, and 4 solr
instances running on the same machine.
On Tue, Sep 3, 2013 at 10:38 AM, Walter Underwood <wu...@wunderwood.org>wrote:
> Those are the Fallacies of Distributed Computing from L. Peter Deutsch.
> The first fallacy is "The network is reliable."
>
> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing
>
> wunder
>
> On Sep 3, 2013, at 10:26 AM, Erick Erickson wrote:
>
> > Ah, thanks for the closure, it's always nice to know. I used to work
> > with a guy who had a list of "network fallacies", that amounted to
> > "you can't trust them fully"....
> >
> > Erick
> >
> >
> > On Tue, Sep 3, 2013 at 12:12 PM, Jared Griffith
> > <jg...@picsauditing.com>wrote:
> >
> >> I think I have it all sorted out. There are some weird network issues
> here
> >> where my test set up is, so that may have been part of the over all
> issue.
> >> Timeouts wouldn't have fixed this issue, that's for sure.
> >>
> >>
> >> On Sat, Aug 31, 2013 at 7:17 AM, Erick Erickson <
> erickerickson@gmail.com
> >>> wrote:
> >>
> >>> bq: Though I am seeing some funkiness that I wasn't seeing with Solr &
> >>> Zookeeper running together
> >>>
> >>> Then I suspect you've set something up inconsistently, _or_ you need to
> >>> extend some timeouts because SolrCloud is being run with separate ZKs
> by
> >>> quite a few people so I'd be surprised if it were anything except
> config
> >>> issues.
> >>>
> >>> If you _do_ uncover something in that realm other than timeouts and
> such,
> >>> we need to know....
> >>>
> >>> Best,
> >>> Erick
> >>>
> >>>
> >>>
> >>>
> >>> On Fri, Aug 30, 2013 at 2:15 PM, Jared Griffith
> >>> <jg...@picsauditing.com>wrote:
> >>>
> >>>> That's what I was thinking. Though I am seeing some funkiness that I
> >>>> wasn't seeing with Solr & Zookeeper running together.
> >>>>
> >>>>
> >>>> On Fri, Aug 30, 2013 at 9:40 AM, Shawn Heisey <so...@elyograg.org>
> >> wrote:
> >>>>
> >>>>> On 8/30/2013 9:43 AM, Jared Griffith wrote:
> >>>>>
> >>>>>> One last thing. Is there any real benefit in running SolrCloud and
> >>>>>> Zookeeper separate? I am seeing some funkiness with the separation
> >>> of
> >>>>>> the
> >>>>>> two, funkiness I wasn't seeing when running SolrCloud + Zookeeper
> >>>> together
> >>>>>> as outlined in the Wiki.
> >>>>>>
> >>>>>
> >>>>> For a robust install, you want zookeeper to be a separate process.
> >> It
> >>>> can
> >>>>> run on the same server as Solr, but the embedded zookeeper (-DzkRun)
> >>>> should
> >>>>> not be used except for dev and proof of concept work.
> >>>>>
> >>>>> The reason is simple. Zookeeper is the central coordinator for
> >>>> SolrCloud.
> >>>>> In order for it to remain stable, it should not be restarted without
> >>>> good
> >>>>> reason. If you are running zookeeper as part of Solr, then you will
> >> be
> >>>>> affecting zookeeper operation anytime you restart that instance of
> >>> Solr.
> >>>>>
> >>>>> Making changes to your Solr setup often requires that you restart
> >> Solr.
> >>>>> This includes upgrading Solr and changing some aspects of its
> >>>>> configuration. Some configuration aspects can be changed with just a
> >>>>> collection reload, but others require a full application restart.
> >>>>>
> >>>>> Thanks,
> >>>>> Shawn
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Jared Griffith
> >>>> Linux Administrator, PICS Auditing, LLC
> >>>> P: (949) 936-4574
> >>>> C: (909) 653-7814
> >>>>
> >>>> <http://www.picsauditing.com>
> >>>>
> >>>> 17701 Cowan #140 | Irvine, CA | 92614
> >>>>
> >>>> Join PICS on LinkedIn and Twitter!
> >>>>
> >>>> <https://twitter.com/PICSAuditingLLC>
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Jared Griffith
> >> Linux Administrator, PICS Auditing, LLC
> >> P: (949) 936-4574
> >> C: (909) 653-7814
> >>
> >> <http://www.picsauditing.com>
> >>
> >> 17701 Cowan #140 | Irvine, CA | 92614
> >>
> >> Join PICS on LinkedIn and Twitter!
> >>
> >> <https://twitter.com/PICSAuditingLLC>
> >>
>
> --
> Walter Underwood
> wunder@wunderwood.org
>
>
>
>
--
Jared Griffith
Linux Administrator, PICS Auditing, LLC
P: (949) 936-4574
C: (909) 653-7814
<http://www.picsauditing.com>
17701 Cowan #140 | Irvine, CA | 92614
Join PICS on LinkedIn and Twitter!
<https://twitter.com/PICSAuditingLLC>
Re: SolrCloud Set up
Posted by Walter Underwood <wu...@wunderwood.org>.
Those are the Fallacies of Distributed Computing from L. Peter Deutsch. The first fallacy is "The network is reliable."
http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing
wunder
On Sep 3, 2013, at 10:26 AM, Erick Erickson wrote:
> Ah, thanks for the closure, it's always nice to know. I used to work
> with a guy who had a list of "network fallacies", that amounted to
> "you can't trust them fully"....
>
> Erick
>
>
> On Tue, Sep 3, 2013 at 12:12 PM, Jared Griffith
> <jg...@picsauditing.com>wrote:
>
>> I think I have it all sorted out. There are some weird network issues here
>> where my test set up is, so that may have been part of the over all issue.
>> Timeouts wouldn't have fixed this issue, that's for sure.
>>
>>
>> On Sat, Aug 31, 2013 at 7:17 AM, Erick Erickson <erickerickson@gmail.com
>>> wrote:
>>
>>> bq: Though I am seeing some funkiness that I wasn't seeing with Solr &
>>> Zookeeper running together
>>>
>>> Then I suspect you've set something up inconsistently, _or_ you need to
>>> extend some timeouts because SolrCloud is being run with separate ZKs by
>>> quite a few people so I'd be surprised if it were anything except config
>>> issues.
>>>
>>> If you _do_ uncover something in that realm other than timeouts and such,
>>> we need to know....
>>>
>>> Best,
>>> Erick
>>>
>>>
>>>
>>>
>>> On Fri, Aug 30, 2013 at 2:15 PM, Jared Griffith
>>> <jg...@picsauditing.com>wrote:
>>>
>>>> That's what I was thinking. Though I am seeing some funkiness that I
>>>> wasn't seeing with Solr & Zookeeper running together.
>>>>
>>>>
>>>> On Fri, Aug 30, 2013 at 9:40 AM, Shawn Heisey <so...@elyograg.org>
>> wrote:
>>>>
>>>>> On 8/30/2013 9:43 AM, Jared Griffith wrote:
>>>>>
>>>>>> One last thing. Is there any real benefit in running SolrCloud and
>>>>>> Zookeeper separate? I am seeing some funkiness with the separation
>>> of
>>>>>> the
>>>>>> two, funkiness I wasn't seeing when running SolrCloud + Zookeeper
>>>> together
>>>>>> as outlined in the Wiki.
>>>>>>
>>>>>
>>>>> For a robust install, you want zookeeper to be a separate process.
>> It
>>>> can
>>>>> run on the same server as Solr, but the embedded zookeeper (-DzkRun)
>>>> should
>>>>> not be used except for dev and proof of concept work.
>>>>>
>>>>> The reason is simple. Zookeeper is the central coordinator for
>>>> SolrCloud.
>>>>> In order for it to remain stable, it should not be restarted without
>>>> good
>>>>> reason. If you are running zookeeper as part of Solr, then you will
>> be
>>>>> affecting zookeeper operation anytime you restart that instance of
>>> Solr.
>>>>>
>>>>> Making changes to your Solr setup often requires that you restart
>> Solr.
>>>>> This includes upgrading Solr and changing some aspects of its
>>>>> configuration. Some configuration aspects can be changed with just a
>>>>> collection reload, but others require a full application restart.
>>>>>
>>>>> Thanks,
>>>>> Shawn
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Jared Griffith
>>>> Linux Administrator, PICS Auditing, LLC
>>>> P: (949) 936-4574
>>>> C: (909) 653-7814
>>>>
>>>> <http://www.picsauditing.com>
>>>>
>>>> 17701 Cowan #140 | Irvine, CA | 92614
>>>>
>>>> Join PICS on LinkedIn and Twitter!
>>>>
>>>> <https://twitter.com/PICSAuditingLLC>
>>>>
>>>
>>
>>
>>
>> --
>>
>> Jared Griffith
>> Linux Administrator, PICS Auditing, LLC
>> P: (949) 936-4574
>> C: (909) 653-7814
>>
>> <http://www.picsauditing.com>
>>
>> 17701 Cowan #140 | Irvine, CA | 92614
>>
>> Join PICS on LinkedIn and Twitter!
>>
>> <https://twitter.com/PICSAuditingLLC>
>>
--
Walter Underwood
wunder@wunderwood.org
Re: SolrCloud Set up
Posted by Erick Erickson <er...@gmail.com>.
Ah, thanks for the closure, it's always nice to know. I used to work
with a guy who had a list of "network fallacies", that amounted to
"you can't trust them fully"....
Erick
On Tue, Sep 3, 2013 at 12:12 PM, Jared Griffith
<jg...@picsauditing.com>wrote:
> I think I have it all sorted out. There are some weird network issues here
> where my test set up is, so that may have been part of the over all issue.
> Timeouts wouldn't have fixed this issue, that's for sure.
>
>
> On Sat, Aug 31, 2013 at 7:17 AM, Erick Erickson <erickerickson@gmail.com
> >wrote:
>
> > bq: Though I am seeing some funkiness that I wasn't seeing with Solr &
> > Zookeeper running together
> >
> > Then I suspect you've set something up inconsistently, _or_ you need to
> > extend some timeouts because SolrCloud is being run with separate ZKs by
> > quite a few people so I'd be surprised if it were anything except config
> > issues.
> >
> > If you _do_ uncover something in that realm other than timeouts and such,
> > we need to know....
> >
> > Best,
> > Erick
> >
> >
> >
> >
> > On Fri, Aug 30, 2013 at 2:15 PM, Jared Griffith
> > <jg...@picsauditing.com>wrote:
> >
> > > That's what I was thinking. Though I am seeing some funkiness that I
> > > wasn't seeing with Solr & Zookeeper running together.
> > >
> > >
> > > On Fri, Aug 30, 2013 at 9:40 AM, Shawn Heisey <so...@elyograg.org>
> wrote:
> > >
> > > > On 8/30/2013 9:43 AM, Jared Griffith wrote:
> > > >
> > > >> One last thing. Is there any real benefit in running SolrCloud and
> > > >> Zookeeper separate? I am seeing some funkiness with the separation
> > of
> > > >> the
> > > >> two, funkiness I wasn't seeing when running SolrCloud + Zookeeper
> > > together
> > > >> as outlined in the Wiki.
> > > >>
> > > >
> > > > For a robust install, you want zookeeper to be a separate process.
> It
> > > can
> > > > run on the same server as Solr, but the embedded zookeeper (-DzkRun)
> > > should
> > > > not be used except for dev and proof of concept work.
> > > >
> > > > The reason is simple. Zookeeper is the central coordinator for
> > > SolrCloud.
> > > > In order for it to remain stable, it should not be restarted without
> > > good
> > > > reason. If you are running zookeeper as part of Solr, then you will
> be
> > > > affecting zookeeper operation anytime you restart that instance of
> > Solr.
> > > >
> > > > Making changes to your Solr setup often requires that you restart
> Solr.
> > > > This includes upgrading Solr and changing some aspects of its
> > > > configuration. Some configuration aspects can be changed with just a
> > > > collection reload, but others require a full application restart.
> > > >
> > > > Thanks,
> > > > Shawn
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jared Griffith
> > > Linux Administrator, PICS Auditing, LLC
> > > P: (949) 936-4574
> > > C: (909) 653-7814
> > >
> > > <http://www.picsauditing.com>
> > >
> > > 17701 Cowan #140 | Irvine, CA | 92614
> > >
> > > Join PICS on LinkedIn and Twitter!
> > >
> > > <https://twitter.com/PICSAuditingLLC>
> > >
> >
>
>
>
> --
>
> Jared Griffith
> Linux Administrator, PICS Auditing, LLC
> P: (949) 936-4574
> C: (909) 653-7814
>
> <http://www.picsauditing.com>
>
> 17701 Cowan #140 | Irvine, CA | 92614
>
> Join PICS on LinkedIn and Twitter!
>
> <https://twitter.com/PICSAuditingLLC>
>