Have you tried get_range_slice on trunk instead? get_key_range's design is kind of fundamentally broken, so we're deprecating it in favor of get_range_slice starting in 0.5. (gkr will still be in the 0.5 series, but probably not after that.)
On Mon, Nov 23, 2009 at 11:03 AM, Dan Di Spaltro <[email protected]> wrote: > I am trying to use get_key_range for an offline type job over about > 18k keys and it keeps timing out. My current setup is 3x4G memory > machines with OPP and a replication factor of 2, and an rpctimeout of > 180s. To combat this I've actually made the KeyCachedFraction 100 > to see if this could help, and no matter how few of the key ranges I > want, I am unable to get any response from the system. > > get_slice's work fine, among all the other commands, I just can't seem > to get get_key_range working. My current workload has few keys and > lots of columns. > > Any advice to debug this would be appreciated. > > -- > Dan Di Spaltro >
