[
https://issues.apache.org/jira/browse/SOLR-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771552#action_12771552
]
Shalin Shekhar Mangar commented on SOLR-1533:
---------------------------------------------
bq. Trying to understand the need for this (I might have missed the discussion
on the ML?).
No, there was no discussion on the ML though this has been an item on the wiki
for some time now.
{quote}
Isn't the creator of the core in control of the data dir (
http://wiki.apache.org/solr/CoreAdmin#CREATE ) and thus their distribution?
Or is the goal of this to remove the logic and knowledge from the client and
let Solr control where core's data is going to be placed, depending on the
"core data distribution policy"?
{quote}
Yes, the creator can specify the dataDir during core creation. The problem is
that maintaining exact filesystem path information in addition to the actual
host/port/core name mapping in an external system is a huge pain. Also, Solr
has more information about the system e.g. how many directories in a given
bucket. It is far easier to have Solr manage it. The strategy for distribution
can be made pluggable if you want.
> Partition data directories into multiple "bucket" directories
> -------------------------------------------------------------
>
> Key: SOLR-1533
> URL: https://issues.apache.org/jira/browse/SOLR-1533
> Project: Solr
> Issue Type: New Feature
> Components: multicore
> Reporter: Shalin Shekhar Mangar
> Fix For: 1.5
>
>
> Provide a way to partition data directories into multiple "bucket"
> directories. For example, instead of creating 10,000 data directories inside
> one base data directory, Solr can assign a core to one of 4 base directories,
> thereby distributing them.
> The underlying problem is that with large number of indexes, we see slower
> and slower system performance as one goes on increasing the number of cores,
> thereby increasing the number of directories in the single data directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
