[
https://issues.apache.org/jira/browse/BLUR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron McCurry closed BLUR-260.
------------------------------
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=a9cbc37425587ffac37c7085841cfed4e367d621
https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=a97d97906bca7230e56334f4b58684725575739f
> Rework shard layout strategy
> ----------------------------
>
> Key: BLUR-260
> URL: https://issues.apache.org/jira/browse/BLUR-260
> Project: Apache Blur
> Issue Type: Improvement
> Components: Blur
> Affects Versions: 0.3.0, 0.2.1
> Reporter: Aaron McCurry
> Priority: Blocker
> Fix For: 0.3.0, 0.2.1
>
>
> This issue is to resolve the excessive movement of shards during a failure as
> well as when a new shard server is brought online.
> This current strategy uses the knowledge of the current online shard server
> list as well as the total of list of shard server to calculate the location
> any given shard. The benefit of the current implementation is that no
> central process is needed to calculate the locations. However the drawback
> to this strategy is that when a new server is added to the available servers,
> it can cause most of the shards of a given table to relocate to another
> server. Obviously this is a problem when new servers come online and added
> to the cluster regularly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
