I was able to get the new collections working dynamically (via Collections
RESTful calls). I was having some other issues with my development
environment that I had to fix up to get it going.
I had to upgrade to 4.5 in order for the aliases to work at all though.
Not sure what the deal was with t
On 10/17/2013 12:51 PM, Christopher Gross wrote:
OK, super confused now.
http://index1:8080/solr/admin/cores?action=CREATE&name=test2&collection=test2&numshards=1&replicationFactor=3
Nets me this:
400
15007
Error CREATEing SolrCore 'test2': Could not find configName
for collection test2 fou
> load the configs into zookeeper,
Yes.
> stop tomcat, add it to the solr.xml file,
and restart tomcat.
To your CREATE URL, add the parameter &collection.configName=
http://wiki.apache.org/solr/SolrCloud#Managing_collections_via_the_Collections_API
Michael Della Bitta
Applications Developer
o
something like:
>
> {"collection":{"AdWorksQuery":"AdWorks"}}
>
> Or access the Zookeeper instance, and do a 'get /aliases.json'.
>
> -Original Message-
> From: Christopher Gross [mailto:cogr...@gmail.com]
> Sent: Thursday, Octobe
nal Message-
From: Christopher Gross [mailto:cogr...@gmail.com]
Sent: Thursday, October 17, 2013 2:40 PM
To: solr-user
Subject: Re: Switching indexes
Also, when I make an alias:
http://index1:8080/solr/admin/collections?action=CREATEALIAS&name=test1-alias&collections=test1
I get a prett
Also, when I make an alias:
http://index1:8080/solr/admin/collections?action=CREATEALIAS&name=test1-alias&collections=test1
I get a pretty useless response:
00
So I'm not sure if it is made. I tried going to:
http://index1:8080/solr/test1-alias/select?q=*:*
but that didn't work. How do I use an
OK, super confused now.
http://index1:8080/solr/admin/cores?action=CREATE&name=test2&collection=test2&numshards=1&replicationFactor=3
Nets me this:
400
15007
Error CREATEing SolrCore 'test2': Could not find configName
for collection test2 found:[xxx, xxx, , x, xx]
400
For that
Thanks Shawn, the explanations help bring me forward to the "SolrCloud"
mentality.
So it sounds like going forward that I should have a more complicated name
(ex: coll1-20131015) aliased to coll1, to make it easier to switch in the
future.
Now, if I already have an index (copied from one location
On 10/16/2013 11:51 AM, Christopher Gross wrote:
> Ok, so I think I was confusing the terminology (still in a 3.X mindset I
> guess.)
>
> From the Cloud->Tree, I do see that I have "collections" for what I was
> calling "core1", "core2", etc.
>
> So, to redo the above,
> Servers: index1, index2,
Ok, so I think I was confusing the terminology (still in a 3.X mindset I
guess.)
>From the Cloud->Tree, I do see that I have "collections" for what I was
calling "core1", "core2", etc.
So, to redo the above,
Servers: index1, index2, index3
Collections: (on each) coll1, coll2
Collection (core?) on
On 10/16/2013 9:44 AM, Christopher Gross wrote:
> Garth,
>
> I think I get what you're saying, but I want to make sure.
>
> I have 3 servers (index1, index2, index3), with Solr living on port 8080.
>
> Each of those has 3 cores loaded with data:
> core1 (old version)
> core1new (new version)
> c
ve entries in /aliases.json
that will tell you what aliases are defined and what they point to.
-Original Message-
From: Christopher Gross [mailto:cogr...@gmail.com]
Sent: Wednesday, October 16, 2013 10:44 AM
To: solr-user
Subject: Re: Switching indexes
Garth,
I think I get what you
lias.
>
> -----Original Message-
> From: Christopher Gross [mailto:cogr...@gmail.com]
> Sent: Wednesday, October 16, 2013 7:05 AM
> To: solr-user
> Subject: Re: Switching indexes
>
> Shawn,
>
> It all makes sense, I'm just dealing with production servers here so
Gross [mailto:cogr...@gmail.com]
Sent: Wednesday, October 16, 2013 7:05 AM
To: solr-user
Subject: Re: Switching indexes
Shawn,
It all makes sense, I'm just dealing with production servers here so I'm trying
to be very careful (shutting down one node at a time is OK, just don't want to
Shawn,
It all makes sense, I'm just dealing with production servers here so I'm
trying to be very careful (shutting down one node at a time is OK, just
don't want to do something catastrophic.)
OK, so I should use that aliasing feature.
On index1 I have:
core1
core1new
core2
On index2 and index
On 10/15/2013 2:17 PM, Christopher Gross wrote:
I have 3 Solr nodes (and 5 ZK nodes).
For #1, would I have to do that on all of them?
For #2, I'm not getting the auto-replication between node 1 and nodes 2 & 3
for my new index.
I have 2 indexes -- just call them "index" and "indexbk" (bk being
Thanks Shawn.
I have 3 Solr nodes (and 5 ZK nodes).
For #1, would I have to do that on all of them?
For #2, I'm not getting the auto-replication between node 1 and nodes 2 & 3
for my new index.
I have 2 indexes -- just call them "index" and "indexbk" (bk being the
backup containing the full data
On 10/15/2013 12:36 PM, Christopher Gross wrote:
In Solr 3.x, whenever I'd reindex content, I'd fill up one instance, copy
the whole "data" directory over to the second (or third) instance and then
restart that Tomcat to get the indexes lined up.
With Solr 4.1, I'm guessing that I can't go and d
18 matches
Mail list logo
