> 3.Maintain a master shard index: This technique involves using a single > master table that maps various values to specific shards. It is very > flexible, and meets a wide variety of application situations. However, this > option often delivers lower performance as it requires an extra lookup for > each sharded SQL Statement.
Range based approach is the actually very flexible application specific way to shard. You can literally allow applications to adapt in any way they want to. Just that the lookup table need not be on the master server. [...] > 3.Rebalancing: In some cases, the sharding scheme chosen for a database has > to be changed. This could happen because the sharding scheme was improperly > chosen (e.g. partitioning users by zip code) or the application outgrows the > database even after being sharded. In such cases, the database shards will > have to be rebalanced which means the partitioning scheme changed and all > existing data moved to new locations. Doing this without incurring down time > is extremely difficult. > > I would really appreciate if somebody from drizzle community is willing to > share ideas regarding handling these issues. I am quite sure you are following my thread of discussion. Very likely, Stewart, and I have something there. -- Anurag Priyam http://about.me/yeban/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
