Re: Dynamically Switching from Ordered Partitioner to Random?
Point taken. Was thinking of switching in parallel using a 2nd cassandra instance (perhaps on the same set of machines). This way if loadbalancing is too slow, I can try this version. From: Stu Hood To: [email protected] Sent: Fri, March 5, 2010 11:48:28 AM Subject: Re: Dynamically Switching from Ordered Partitioner to Random? But rather than switching, you should definitely try the 'loadbalance' approach first, and see whether OrderPP works out for you. -Original Message- From: "Chris Goffinet" Sent: Friday, March 5, 2010 1:43pm To: [email protected] Subject: Re: Dynamically Switching from Ordered Partitioner to Random? At this time, you have to re-import the data. -Chris On Fri, Mar 5, 2010 at 11:42 AM, shiv shivaji wrote: > I started with the ordered partitioner as I was hoping to make use of the > map-reduce functionality. However, my data was likely lopped onto 2 key > machines with most of it on one (as seen from another thread. There were > also machine failures to blame for the uneven distribution). One solution > which I am trying is to load balance. Is there any other thing I can try to > convert the partitioner to random on a live system? > > I know this sounds like an odd request. Curious about my options though. I > did see a post mentioning that one can compute the md5 hash of each key and > then insert using that and have a mapping table from key to md5 hash. > Unfortunately, the data is already loaded using an ordered partitioner and I > was wondering if there is a way to switch to random now. > > Shiv > -- Chris Goffinet
Re: Dynamically Switching from Ordered Partitioner to Random?
But rather than switching, you should definitely try the 'loadbalance' approach first, and see whether OrderPP works out for you. -Original Message- From: "Chris Goffinet" Sent: Friday, March 5, 2010 1:43pm To: [email protected] Subject: Re: Dynamically Switching from Ordered Partitioner to Random? At this time, you have to re-import the data. -Chris On Fri, Mar 5, 2010 at 11:42 AM, shiv shivaji wrote: > I started with the ordered partitioner as I was hoping to make use of the > map-reduce functionality. However, my data was likely lopped onto 2 key > machines with most of it on one (as seen from another thread. There were > also machine failures to blame for the uneven distribution). One solution > which I am trying is to load balance. Is there any other thing I can try to > convert the partitioner to random on a live system? > > I know this sounds like an odd request. Curious about my options though. I > did see a post mentioning that one can compute the md5 hash of each key and > then insert using that and have a mapping table from key to md5 hash. > Unfortunately, the data is already loaded using an ordered partitioner and I > was wondering if there is a way to switch to random now. > > Shiv > -- Chris Goffinet
Re: Dynamically Switching from Ordered Partitioner to Random?
At this time, you have to re-import the data. -Chris On Fri, Mar 5, 2010 at 11:42 AM, shiv shivaji wrote: > I started with the ordered partitioner as I was hoping to make use of the > map-reduce functionality. However, my data was likely lopped onto 2 key > machines with most of it on one (as seen from another thread. There were > also machine failures to blame for the uneven distribution). One solution > which I am trying is to load balance. Is there any other thing I can try to > convert the partitioner to random on a live system? > > I know this sounds like an odd request. Curious about my options though. I > did see a post mentioning that one can compute the md5 hash of each key and > then insert using that and have a mapping table from key to md5 hash. > Unfortunately, the data is already loaded using an ordered partitioner and I > was wondering if there is a way to switch to random now. > > Shiv > -- Chris Goffinet
Dynamically Switching from Ordered Partitioner to Random?
I started with the ordered partitioner as I was hoping to make use of the map-reduce functionality. However, my data was likely lopped onto 2 key machines with most of it on one (as seen from another thread. There were also machine failures to blame for the uneven distribution). One solution which I am trying is to load balance. Is there any other thing I can try to convert the partitioner to random on a live system? I know this sounds like an odd request. Curious about my options though. I did see a post mentioning that one can compute the md5 hash of each key and then insert using that and have a mapping table from key to md5 hash. Unfortunately, the data is already loaded using an ordered partitioner and I was wondering if there is a way to switch to random now. Shiv
