Yes, removing the absolute value cured the problem, but I feel like there
should be a better option than the "default". Given multiple collections,
there should be some ability within the API to lay down the directory
structure in a different way e.g. ./collection/shard as opposed to the
current a
Those are paths? /data/solr off the root?
When using the collections api, you really don't want to set an absolute data
dir - it should be relative, I'd just take the default. Then, even though many
shards shard that solrconfig and data dir, they will all find a nice home
relative to the instan
So, upgraded to 4.2 this morning. I had gotten to the point where I okay
with the collection creation process in 4.1 using the API vice the solr.xml
file in 4.0, but now 4.2 doesn't seem to want to create the instanceDir?
e.g. the Dashboard reports the following when my solr.data.dir is set to
/d
On Mar 28, 2013, at 7:30 PM, Shawn Heisey wrote:
> Can't you leave numShards out completely, then include a numShards parameter
> on a collection api CREATE url, possibly giving a different numShards to each
> collection?
>
> Thanks,
> Shawn
>
Yes - that's why I say the collections API is t
On 3/28/2013 4:23 PM, Mark Miller wrote:
True - though I think for 4.2. numShards has never been respected in the
Can't you leave numShards out completely, then include a numShards
parameter on a collection api CREATE url, possibly giving a different
numShards to each collection?
Thanks,
Sh
That's my kind of release!
Sent from my Verizon Wireless Phone
- Reply message -
From: "Mark Miller"
To:
Subject: Solrcloud 4.1 Collection with multiple slices only use
Date: Thu, Mar 28, 2013 6:34 pm
On Mar 28, 2013, at 6:30 PM, Chris R wrote:
> I'll probably move up to 4.2 tomorr
On Mar 28, 2013, at 6:30 PM, Chris R wrote:
> I'll probably move up to 4.2 tomorrow.
4.2.1 should be ready as soon as I have time to publish it - we have a passing
vote and I think we are close to 72 hours after. I just have to stock up on
some beer first - Robert tells me it's like a 20 beer
Interesting, I've been doing battle with it while coming from a 4.0
environment. I only had a single collection then and just created the
solr.xml files for each server up front. They each supported a half dozen
cores for a single collection.
As for 4.1 and collections API, the only issue I've h
True - though I think for 4.2. numShards has never been respected in the wrote:
> So, by using the numshards at initialization time, using the sample
> collection1 solr.xml, I'm able to create a sharded and distributed index.
> Also, by removing any initial cores from the solr.xml file, i'm able
So, by using the numshards at initialization time, using the sample
collection1 solr.xml, I'm able to create a sharded and distributed index.
Also, by removing any initial cores from the solr.xml file, i'm able to use
the collections API via the web to create multiple collection with sharded
index
I realized my error shortly, more docs, better spread. I continued to do some
testing to see how I could manually lay out the shards in what I thought was a
more organized manner and with more descriptive names than the numshards
parameter alone produced. I also gen'd up a few thousand docs a
First, three documents isn't enough to really test. The formula for
assigning shards is to hash on the unique ID. It _is_ possible that
all three just happened to land on the same shard. If you index all 32
docs in the example dir and they're all on the same shard, we should
talk.
Second, a regula
So - I must be missing something very basic here and I've gone back to the
Wiki example. After setting up the two shard example in the first tutorial
and indexing the three example documents, look at the shards in the Admin
UI. The documents are stored in the index where the update with directed
Interesting, I saw some comments about numshards, but it wasnt ever
specific enough to catch.my attention. I will give it a try tomorrow.
Thanks.
On Mar 25, 2013 11:35 PM, "Mark Miller" wrote:
> I'm guessing you didn't specify numShards. Things changed in 4.1 - if you
> don't specify numShards i
I'm guessing you didn't specify numShards. Things changed in 4.1 - if you don't
specify numShards it goes into a mode where it's up to you to distribute
updates.
- Mark
On Mar 25, 2013, at 10:29 PM, Chris R wrote:
> I have two issues and I'm unsure if they are related:
>
> Problem: After se
15 matches
Mail list logo
