You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by "Damick, Jeffrey" <Je...@neustar.biz> on 2010/10/25 21:45:39 UTC
keys_cached percent?
Does 0.7 not support percentages in the keys_cached (in the yaml config)? (I'm on 0.7.0b2 so maybe it has been fixed?)
thanks
Re: keys_cached percent?
Posted by Edward Capriolo <ed...@gmail.com>.
On Mon, Oct 25, 2010 at 9:43 PM, Damick, Jeffrey
<Je...@neustar.biz> wrote:
> Sure - so percents aren’t supported anymore in 0.7.x, which is fine, I just
> wanted to clarify.
>
> thanks
>
>
> On 10/25/10 9:31 PM, "Aaron Morton" <aa...@thelastpickle.com> wrote:
>
> To cache 100% set the value to 1. The comments in the yaml below do
> explicitly say this, but its discussed here
> http://wiki.apache.org/cassandra/StorageConfiguration?highlight=(keys)|(cached)
>
> Aaron
>
>
> On 26 Oct, 2010,at 02:02 PM, "Damick, Jeffrey" <Je...@neustarbiz>
> wrote:
>
> I tried a few variations, but when it set it to: 100% or “100%” or similar
> I get:
>
> ERROR 19:37:31,898 Fatal error: null; Can't construct a java object for
> tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot
> create property=keyspaces for
> JavaBean=org.apache.cassandra.config.Config@32955cd5; Cannot create
> property=column_families for
> JavaBean=org.apache.cassandra.config.RawKeyspace@31b446d1; Cannot create
> property=keys_cached for
> JavaBean=org.apache.cassandra.config.RawColumnFamily@c68c26c; For input
> string: "100%"
> Bad configuration; unable to start server
>
> It looks like if it’s yaml it doesn’t pass through the
> FBUtils.parseDoubleOrPercent(), and since the bean has a double the yaml
> deserializer is blowing up... Just a guess..
>
> -jeff
>
>
> On 10/25/10 3:51 PM, "Aaron Morton" <aa...@thelastpickle.com> wrote:
>
> It should do, this is the comment from the yaml
>
> # - keys_cached: specifies the number of keys per sstable whose
> # locations we keep in memory in "mostly LRU" order. (JUST the key
> # locations, NOT any column values.) Specify a fraction (value less
> # than 1) or an absolute number of keys to cache. Defaults to 200000
> # keys.
>
> Is it not working?
> Aaron
>
>
> On 26 Oct, 2010,at 08:45 AM, "Damick, Jeffrey" <Je...@neustar.biz>
> wrote:
>
> Does 0.7 not support percentages in the keys_cached (in the yaml config)?
> (I’m on 07.0b2 so maybe it has been fixed?)
>
> thanks
>
>
>
>
% IS supported .50 is 50%
Re: keys_cached percent?
Posted by "Damick, Jeffrey" <Je...@neustar.biz>.
Sure - so percents aren't supported anymore in 0.7.x, which is fine, I just wanted to clarify.
thanks
On 10/25/10 9:31 PM, "Aaron Morton" <aa...@thelastpickle.com> wrote:
To cache 100% set the value to 1. The comments in the yaml below do explicitly say this, but its discussed here http://wiki.apache.org/cassandra/StorageConfiguration?highlight=(keys)|(cached)
Aaron
On 26 Oct, 2010,at 02:02 PM, "Damick, Jeffrey" <Je...@neustarbiz> wrote:
I tried a few variations, but when it set it to: 100% or "100%" or similar I get:
ERROR 19:37:31,898 Fatal error: null; Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=keyspaces for JavaBean=org.apache.cassandra.config.Config@32955cd5; Cannot create property=column_families for JavaBean=org.apache.cassandra.config.RawKeyspace@31b446d1; Cannot create property=keys_cached for JavaBean=org.apache.cassandra.config.RawColumnFamily@c68c26c; For input string: "100%"
Bad configuration; unable to start server
It looks like if it's yaml it doesn't pass through the FBUtils.parseDoubleOrPercent(), and since the bean has a double the yaml deserializer is blowing up... Just a guess..
-jeff
On 10/25/10 3:51 PM, "Aaron Morton" <aa...@thelastpickle.com> wrote:
It should do, this is the comment from the yaml
# - keys_cached: specifies the number of keys per sstable whose
# locations we keep in memory in "mostly LRU" order. (JUST the key
# locations, NOT any column values.) Specify a fraction (value less
# than 1) or an absolute number of keys to cache. Defaults to 200000
# keys.
Is it not working?
Aaron
On 26 Oct, 2010,at 08:45 AM, "Damick, Jeffrey" <Je...@neustar.biz> wrote:
Does 0.7 not support percentages in the keys_cached (in the yaml config)? (I'm on 07.0b2 so maybe it has been fixed?)
thanks
Re: keys_cached percent?
Posted by Aaron Morton <aa...@thelastpickle.com>.
To cache 100% set the value to 1. The comments in the yaml below do explicitly say this, but its discussed here http://wiki.apache.org/cassandra/StorageConfiguration?highlight=(keys)|(cached)
Aaron
On 26 Oct, 2010,at 02:02 PM, "Damick, Jeffrey" <Je...@neustar.biz> wrote:
I tried a few variations, but when it set it to: 100% or “100%” or similar I get:
ERROR 19:37:31,898 Fatal error: null; Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=keyspaces for JavaBean=org.apache.cassandra.config.Config@32955cd5; Cannot create property=column_families for JavaBean=org.apache.cassandra.config.RawKeyspace@31b446d1; Cannot create property=keys_cached for JavaBean=org.apache.cassandra.config.RawColumnFamily@c68c26c; For input string: "100%"
Bad configuration; unable to start server
It looks like if it’s yaml it doesn’t pass through the FBUtils.parseDoubleOrPercent(), and since the bean has a double the yaml deserializer is blowing up... Just a guess..
-jeff
On 10/25/10 3:51 PM, "Aaron Morton" <aa...@thelastpickle.com> wrote:
It should do, this is the comment from the yaml
# - keys_cached: specifies the number of keys per sstable whose
# locations we keep in memory in "mostly LRU" order. (JUST the key
# locations, NOT any column values.) Specify a fraction (value less
# than 1) or an absolute number of keys to cache. Defaults to 200000
# keys.
Is it not working?
Aaron
On 26 Oct, 2010,at 08:45 AM, "Damick, Jeffrey" <Je...@neustar.biz> wrote:
Does 0.7 not support percentages in the keys_cached (in the yaml config)? (I’m on 0.7.0b2 so maybe it has been fixed?)
thanks
Re: keys_cached percent?
Posted by "Damick, Jeffrey" <Je...@neustar.biz>.
I tried a few variations, but when it set it to: 100% or "100%" or similar I get:
ERROR 19:37:31,898 Fatal error: null; Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=keyspaces for JavaBean=org.apache.cassandra.config.Config@32955cd5; Cannot create property=column_families for JavaBean=org.apache.cassandra.config.RawKeyspace@31b446d1; Cannot create property=keys_cached for JavaBean=org.apache.cassandra.config.RawColumnFamily@c68c26c; For input string: "100%"
Bad configuration; unable to start server
It looks like if it's yaml it doesn't pass through the FBUtils.parseDoubleOrPercent(), and since the bean has a double the yaml deserializer is blowing up... Just a guess..
-jeff
On 10/25/10 3:51 PM, "Aaron Morton" <aa...@thelastpickle.com> wrote:
It should do, this is the comment from the yaml
# - keys_cached: specifies the number of keys per sstable whose
# locations we keep in memory in "mostly LRU" order. (JUST the key
# locations, NOT any column values.) Specify a fraction (value less
# than 1) or an absolute number of keys to cache. Defaults to 200000
# keys.
Is it not working?
Aaron
On 26 Oct, 2010,at 08:45 AM, "Damick, Jeffrey" <Je...@neustar.biz> wrote:
Does 0.7 not support percentages in the keys_cached (in the yaml config)? (I'm on 0.7.0b2 so maybe it has been fixed?)
thanks
Re: keys_cached percent?
Posted by Aaron Morton <aa...@thelastpickle.com>.
It should do, this is the comment from the yaml
# - keys_cached: specifies the number of keys per sstable whose
# locations we keep in memory in "mostly LRU" order. (JUST the key
# locations, NOT any column values.) Specify a fraction (value less
# than 1) or an absolute number of keys to cache. Defaults to 200000
# keys.
Is it not working?
Aaron
On 26 Oct, 2010,at 08:45 AM, "Damick, Jeffrey" <Je...@neustar.biz> wrote:
Does 0.7 not support percentages in the keys_cached (in the yaml config)? (I’m on 0.7.0b2 so maybe it has been fixed?)
thanks