Received: by 10.42.80.3 with SMTP id t3mr2282952ick.24.1347703404546; Sat, 15 Sep 2012 03:03:24 -0700 (PDT) X-BeenThere: project-voldemort@googlegroups.com Received: by 10.231.51.106 with SMTP id c42ls11049606ibg.3.gmail; Sat, 15 Sep 2012 03:03:23 -0700 (PDT) Received: by 10.43.105.135 with SMTP id dq7mr2282594icc.3.1347703403551; Sat, 15 Sep 2012 03:03:23 -0700 (PDT) Received: by 10.43.105.135 with SMTP id dq7mr2282593icc.3.1347703403533; Sat, 15 Sep 2012 03:03:23 -0700 (PDT) Return-Path: Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by gmr-mx.google.com with ESMTPS id wo9si1219705igc.1.2012.09.15.03.03.23 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Sep 2012 03:03:23 -0700 (PDT) Received-SPF: pass (google.com: domain of ctas...@gmail.com designates 209.85.214.172 as permitted sender) client-ip=209.85.214.172; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ctas...@gmail.com designates 209.85.214.172 as permitted sender) smtp.mail=ctas...@gmail.com; dkim=pass header...@gmail.com Received: by obbwc20 with SMTP id wc20so9319847obb.17 for ; Sat, 15 Sep 2012 03:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iK/XVxDJAxG7EmPf3UpJM1MJ+ZRhR3a//vAY9X4V/TI=; b=pdEEk3YzdqMKOjuZrrdNdUClwC0FcU5xdCkfqc5vDD1Nfjiv5OhJVTl60PTdecDlxG BwLxJRoOc31NvzTqDMbqXGR+uHGYBHrf2q4lYgeE9grhd/6uoz3TvTQF20GsCY29WPqy FBWbkIuAV2dOoagD+7eGXtxnvlYudgSF/pa51w/ZHIA/XVrEozMomjSqWfse6OTIbRJr 9S5IWeaqPwUcAG+x3uoIqlWwoJJknr7quj/UunTKGrbkRDIp/CjicZi9RQU5ugR2QCR4 mbbF6ntwF22VK1p3it3YMNsK9afyh0pRIWlRdx4Fjv/+OTYntNblO/f3bDHHJyJRO8N9 Gi8A== MIME-Version: 1.0 Received: by 10.182.110.67 with SMTP id hy3mr6885654obb.52.1347703403165; Sat, 15 Sep 2012 03:03:23 -0700 (PDT) Received: by 10.60.43.35 with HTTP; Sat, 15 Sep 2012 03:03:23 -0700 (PDT) In-Reply-To: <1f1b2a77-d275-4c3c-8419-09babf6d9333@googlegroups.com> References: <8e4994a5-5821-4c84-897f-13d12cf1eac9@googlegroups.com> <1f1b2a77-d275-4c3c-8419-09babf6d9333@googlegroups.com> Date: Sat, 15 Sep 2012 12:03:23 +0200 Message-ID: Subject: Re: [project-voldemort] Re: Voldemort 0.96 new configuration options From: Carlos Tasada To: project-voldemort@googlegroups.com Content-Type: multipart/alternative; boundary=f46d0445171d9bb8f404c9baa67f --f46d0445171d9bb8f404c9baa67f Content-Type: text/plain; charset=ISO-8859-1 Thanks a lot Lei, looking forward for this info :) Also the news that you're already working in the next release with BDB changes are really exciting :) On Fri, Sep 14, 2012 at 10:30 PM, Lei Gao wrote: > Hi Carlos, > > Those timeout parameters are used to specify operation-specific timeout > for a client. We will update the documentation on it. > > I recommend that you don't spend too much time on those bdb specific > parameters because they are associated with the BDB JE storage enhancements > that will be officially released in the next major release, when > documentation will be available for those newly added parameters. > > Thanks, > > Lei > > > On Friday, September 14, 2012 1:37:30 AM UTC-7, ctasada wrote: >> >> Hi guys, >> >> With the 0.96 release there are some new configuration options in >> Voldemort that are not documented. >> >> Server Properties: >> * Removed in 0.96 >> - bdb.cleaner.lazy.migration >> - bdb.cache.evictln >> - bdb.minimize.scan.impact >> >> * Added in 0.96 >> - bdb.minimum.shared.cache >> - fetcher.max.bytes.per.sec >> - fetcher.min.bytes.per.sec >> - fetcher.reporting.interval.**bytes >> - hdfs.fetcher.buffer.size >> - client.routing.get.timeout.ms >> - client.routing.getall.timeout.**ms >> - client.routing.put.timeout.ms >> - client.routing.getversions.**timeout.ms >> - client.routing.delete.timeout.**ms >> - client.routing.allow.partial.**getall >> - enable.jmx.clustername >> - service.interruptible >> >> Added memory-footprint to stores.xml >> >> Client properties: >> - getall_routing_timeout_ms >> - put_routing_timeout_ms >> - get_routing_timeout_ms >> - getversions_routing_timeout_**ms >> - delete_routing_timeout_ms >> - allow_partial_getalls >> >> Some of these new properties look really interesting and I'm already >> investigating them, but I would like to hear, if possible, your comments >> regarding the different case scenarios and the stability of them. >> >> Note: This documentation should be also added to the wiki and/or website. >> >> Thanks, >> Carlos. >> > -- > > > --f46d0445171d9bb8f404c9baa67f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks a lot Lei, looking forward for this info :)

Also = the news that you're already working in the next release with BDB chang= es are really exciting :)

On Fri, Sep 14,= 2012 at 10:30 PM, Lei Gao <gao...@gmail.com> wrote:
Hi Carlos,

Those timeout parameters a= re used to specify operation-specific timeout for a client. We will update = the documentation on it.

I recommend that you don't spend too much time on those bdb specifi= c parameters because they are associated with the BDB JE storage enhancemen= ts that will be officially released in the next major release, when documen= tation will be available for those newly added parameters.

Thanks,

Lei


On Fr= iday, September 14, 2012 1:37:30 AM UTC-7, ctasada wrote:
Hi guys,

With the 0.96 release there are some new config= uration options in Voldemort that are not documented.

<= div>Server Properties:
* Removed in 0.96
=A0 - bdb.clea= ner.lazy.migration
=A0 - bdb.cache.evictln
=A0 - bdb.minimize.scan.impact
=

* Added in 0.96
=A0 - bdb.minimum.shared.cach= e
=A0 - fetcher.max.bytes.per.sec
=A0 - fetcher.min.byt= es.per.sec
=A0 - fetcher.reporting.interval.bytes
=A0 - hdfs.fet= cher.buffer.size
=A0 - client.ro= uting.allow.partial.getall
=A0 - enable.jmx.clustername
=A0 - service.interruptible=A0

Added memory-fo= otprint to stores.xml

Client properties:
=A0 -=A0getall_routing_timeout_ms
=A0 -=A0put_routing_timeout_ms=
=A0 -=A0get_routing_timeout_ms
=A0 -=A0getversions_routing_timeou= t_ms
=A0 -=A0delete_routing_timeout_ms
=A0 -=A0a= llow_partial_getalls

Some of these new properties = look really interesting and I'm already investigating them, but I would= like to hear, if possible, your comments regarding the different case scen= arios and the stability of them.

Note: This documentation should be also added to the wi= ki and/or website.

Thanks,
Carlos.
=

--
=A0
=A0

--f46d0445171d9bb8f404c9baa67f--