Hello,
Does anyone have innostore set up under multi_backend? I can't seem to get
it to work properly with multi_backend.
I tried adding it under the multi_backend, but it won't use any parameters
passed in in the third parameter. If I set it up as an application, you
can't select it as a backend
Hi Dan,
the error I've been trying to fix for the past week wasn't riak's fault
it's a bug in Erlang R13B04.
Sean helped me yesterday via IRC to get riak-search working on R14B
which fixed it for me.
You can read more about that erlang bug on the erlang-bugs mailing list:
http://www.erlang.or
On Mon, Nov 22, 2010 at 11:47 AM, Mark Phillips wrote:
>
> We just added a page to the wiki (this very morning, in fact) with
> rolling upgrade instructions for Debian, Redhat and Solaris.
>
> http://wiki.basho.com/display/RIAK/Rolling+Upgrades
Are there any restrictions, incompatibilities betwee
On Tue, Nov 23, 2010 at 7:43 AM, Colin Surprenant
wrote:
> Are there any restrictions, incompatibilities between versions which
> could break a rolling upgrade?
Good question. In our internal testing we have started verifying that
sequential releases (i.e. 0.12 -> 0.13) support the rolling upgrad
Is it possible to update only headers on an object?
In writing the Riak spring-data support, I'm having to update objects in their
entirety to manage relationships between them. In one operation I might create
an object and in another, I might add a link to it (after I've saved the new
child ob
On Tue, Nov 23, 2010 at 10:18 AM, David Smith wrote:
> In our internal testing we have started verifying that
> sequential releases (i.e. 0.12 -> 0.13) support the rolling upgrades
> cleanly.
Great stuff. May I suggest to add this fact into the rolling upgrade wiki page?
> Given the leap of the
Hi Jon,
Unfortunately, it is not possible to update just the metadata of the object;
updating the entire object is required. One possible alternative is to store
the metadata and body as two separate objects which would allow you to
update the metadata without resending the body.
Some initial tho
On Tue, Nov 23, 2010 at 8:58 AM, Colin Surprenant
wrote:
>
> Would upgrading (rolling or offline) sequentially from 0.10 to 0.11 to
> 0.12 be "easier" to manage potential compatibility issues?
As on of my colleagues (Grant) just pointed out to me, a rolling
upgrade of 0.10 -> 0.13 won't work due
You are correct, the innostore backend is not using the parameters passed to
it by multi_backend:
https://issues.basho.com/show_bug.cgi?id=890
Rather than modifying the innostore.app file you can configure the default
innostore settings in your Riak app.config file:
[
{riak_core, [...riak_core set
(many profuse apologies to Dan - hit "reply" instead of "reply all")
Alrighty, I've done a little more digging. When I throttle the writes
heavily (2/sec) and set R and W to 1 all around, the cluster works just fine
after I restart the node for about 15-20 seconds. Then the read request
hangs fo
Just a thought ... have you verified your switch, cables, nics, etc
On 24 November 2010 09:33, Jay Adkisson wrote:
> (many profuse apologies to Dan - hit "reply" instead of "reply all")
>
> Alrighty, I've done a little more digging. When I throttle the writes
> heavily (2/sec) and set R and W t
Hi Dan,
I'm using riak_search 0.13.0 and innostore 1.0.2, btw.
If I add the default innostore configuration like on the configuration page,
and also add an entry for innostore in the multi_backend I get this error on
startup:
{{{badmatch,
{error,
{eagain
Can you provide the different app.configs you are using?
Thanks,
Dan
Daniel Reverri
Developer Advocate
Basho Technologies, Inc.
d...@basho.com
On Tue, Nov 23, 2010 at 5:59 PM, Joseph Lambert
wrote:
> Hi Dan,
>
> I'm using riak_search 0.13.0 and innostore 1.0.2, btw.
>
> If I add the default in
This:
{riak_kv, [
{multi_backend, [
{<<"inno">>, riak_kv_innostore_backend, []}
]}
]},
{innostore, [
{data_home_dir, "/var/lib/riak/innostore"},
{log_group_home_dir, "/var/lib/riak/inno-log"},
{buffer_pool_size, 429496729
Can you provide the full app.config? I'd like to see if multi backend has
been setup correctly.
Thanks,
Dan
Daniel Reverri
Developer Advocate
Basho Technologies, Inc.
d...@basho.com
On Tue, Nov 23, 2010 at 6:35 PM, Joseph Lambert
wrote:
> This:
>
> {riak_kv, [
>
> {multi_backend,
Attached is app.config, below is copy/pasted the multi_backend part
{storage_backend, riak_kv_multi_backend},
{multi_backend_default, <<"bitcask">>},
{multi_backend, [
{<<"bitcask">>, riak_kv_bitcask_backend, [{data_root,
"/var/lib/riak/bitcask"}]},
2010/11/23 David Smith
> On Tue, Nov 23, 2010 at 8:58 AM, Colin Surprenant
> wrote:
> >
> > Would upgrading (rolling or offline) sequentially from 0.10 to 0.11 to
> > 0.12 be "easier" to manage potential compatibility issues?
>
> As on of my colleagues (Grant) just pointed out to me, a rolling
>
17 matches
Mail list logo
