> On Feb 9, 2015, at 10:02 AM, Edgar Veiga wrote:
>
> Thanks Christopher,
>
> BTW, A few more questions:
> - If something goes wrong during the process of joining the nodes, is it
> possible to make a rollback? If true, how?
There is no way to currently rollback this process; however, nodes
Thanks Christopher,
BTW, A few more questions:
- If something goes wrong during the process of joining the nodes, is it
possible to make a rollback? If true, how?
- Should I look again to the leveldb configurations. It has been working
pretty smoothly for more than one year, but 6 more nodes sugge
> On Feb 6, 2015, at 1:53 AM, Edgar Veiga wrote:
>
> It is expected that the total amount of data per node lowers quite a lot,
> correct? I'm doubling the size of the cluster (6 more nodes).
>
> I ask this because the actual 6 machines have 1.5Tb in disks, but the new
> ones ( for now) have o
It is expected that the total amount of data per node lowers quite a lot,
correct? I'm doubling the size of the cluster (6 more nodes).
I ask this because the actual 6 machines have 1.5Tb in disks, but the new ones
( for now) have only 1Tb.
Best regards
—
Sent from my iPhone
On Sat, J
I just closed https://github.com/basho/riak/issues/667
riak-2.0.5 will address it
Thanks for the report and sorry for the inconvenience.
On 21 Jan 2015, at 19:28, Alexander Popov wrote:
> Actually, problematic node is production. but when shit happens i was migrate
> all data ( export/import)
Yeah, after sending the email I realized both! :)
Thanks! Have a nice weekend
On 24 January 2015 at 21:46, Sargun Dhillon wrote:
> 1) Potentially re-enable AAE after migration. As your cluster gets
> bigger, the likelihood of any node failing in the cluster goes up.
> Replica divergence only
1) Potentially re-enable AAE after migration. As your cluster gets
bigger, the likelihood of any node failing in the cluster goes up.
Replica divergence only becomes scarier in light of this. Losing data
!= awesome.
6) There shouldn't be any problems, but for safe measures you should
probably upgr
Sargun,
Regarding 1) - AAE is disabled. We had a problems with it and there's a lot
of threads here in the mailing list regarding this. AAE won't stop using
more and more disk space and the only solution was disabling it! Since then
the cluster has been pretty stable...
Regarding 6) Can you or an
Several things:
1) If you have data at rest that doesn't change, make sure you have
AAE, and it's ran before your cluster is manipulated. Given that
you're running at 85% space, I would be a little worried to turn it
on, because you might run out of disk space. You can also pretty
reasonably put th
Hi Alexander! Thanks for the reply.
Ring actual size: 256;
Total amount of data on cluster: ~6.6TB (~1.1TB per node)
Best regards,
Edgar
On 24 January 2015 at 20:42, Alexander Sicular wrote:
> I would probably add them all in one go so you have one vnode migration
> plan that gets executed. Wh
I would probably add them all in one go so you have one vnode migration plan
that gets executed. What is your ring size? How much data are we talking about?
It's not necessarily the number of keys but rather the total amount of data and
how quickly that data can move en mass between machines.
Hi everyone!
I have a riak cluster, working in production for about one year, with the
following characteristics:
- Version 1.4.8
- 6 nodes
- leveldb backend
- replication (n) = 3
~ 3 billion keys
My ssd's are reaching 85% of capacity and we have decided to buy 6 more nodes
to expand the cluste
Actually, problematic node is production. but when shit happens i was
migrate all data ( export/import) to clean setup.
so i can experiment with old node.
It have not source installation, from package.
I will try compile it tomorrow.
On Wed, Jan 21, 2015 at 9:01 PM, Russell Brown wrote:
> There
There’s a branch of riak_dt here https://github.com/basho/riak_dt/pull/111
Since you’re running against a source install (I assume in development, or
test?) would you be so kind as to try this branch and see if it solves your
issue?
Many thanks
Russell
On 20 Jan 2015, at 15:12, Alexander Popo
Thanks.
On Tue, Jan 20, 2015 at 5:07 PM, Russell Brown wrote:
> FYI https://github.com/basho/riak/issues/667
>
> I’ll get to work on it at once, we might be able to hit the 2.0.5 build
> date at the end of the week.
>
> On 20 Jan 2015, at 14:04, Russell Brown wrote:
>
> > I’ll open a ticket for
FYI https://github.com/basho/riak/issues/667
I’ll get to work on it at once, we might be able to hit the 2.0.5 build date at
the end of the week.
On 20 Jan 2015, at 14:04, Russell Brown wrote:
> I’ll open a ticket for it. We changed the internal structure of both Maps and
> Sets, and tested t
I’ll open a ticket for it. We changed the internal structure of both Maps and
Sets, and tested that they were backwards compatible, but clearly missed
something.
On 20 Jan 2015, at 13:54, Alexander Popov wrote:
> Upgraded riak 2.0.2-> 2.0.4
> trying to add nodes to cluster( was single node )
Upgraded riak 2.0.2-> 2.0.4
trying to add nodes to cluster( was single node )
all new nodes located on another host, but multi-nodes installation from
source
each new node have config settings tuned like
nodename = riak1@10.0.0.28
platform_data_dir = /var/lib/riak1
listener.http.internal = 0.0.0.0
18 matches
Mail list logo
