Hi,
we have some issues with 2i queries like that:
seffenberg@kriak46-1:~$ while :; do curl -s
localhost:8098/buckets/conversation/index/createdat_int/0/23182680 | ruby
-rjson -e "o = JSON.parse(STDIN.read); puts o['keys'].size"; sleep 1; done
13853
13853
0
557
557
557
13853
0
...
So I trie
One thing I realized right now.. the new node is on wheezy whereas all
other 12 nodes are running squeeze.. but shouldn't be a problem, right?
On Tue, Jul 29, 2014 at 08:35:15AM +, Effenberg, Simon wrote:
> Hi,
>
> we have some issues with 2i queries like that:
>
> seffenberg@kriak46-1:~$ wh
Hi Simon,
There are some (maybe related) Level DB fixes in 1.4.9 and 1.4.10, I
don't think there isn't any harm for you to do a rolling upgrade since
nothing major changed, just bug fixes, here is the release notes' link
for reference:
https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md
Already started to prepare everything for it.. :)
On Tue, Jul 29, 2014 at 09:43:22AM +0100, Guido Medina wrote:
> Hi Simon,
>
> There are some (maybe related) Level DB fixes in 1.4.9 and 1.4.10, I don't
> think there isn't any harm for you to do a rolling upgrade since nothing
> major changed, ju
Said to say but the issue stays the same.. even after the upgrade to
1.4.10.
Any ideas what is happening here?
Cheers
Simon
On Tue, Jul 29, 2014 at 08:46:42AM +, Effenberg, Simon wrote:
> Already started to prepare everything for it.. :)
>
> On Tue, Jul 29, 2014 at 09:43:22AM +0100, Guido M
Thanks Joseph and Sean!
I did give it a quick try with override approach, then 'riak-admin
ensemble-status' did return enabled/active...but when I try to insert a new
entry the server just crashed. After few trials and server restart, the
setting somehow got auto reverted back. Now I am back w/ n
Is the requirement for having AAE enabled now removed for strong consistency?
On Mon, Jul 28, 2014 at 4:55 PM, Joseph Blomstedt wrote:
> This means the consistency sub-system is not enabled/active. You can
> verify this with the output of `riak-admin ensemble-status`.
>
> To enable strong consist
In short, not really. Solr is at best near realtime (NRT). By default, it takes
Solr one second to soft commit the value to its index. This timing can be
lowered, but note that the lower the number, the more it impacts overall system
performance. One second is the general top speed, but feel fre
> Is the requirement for having AAE enabled now removed for strong consistency?
Yes. AAE is no longer required to use strong consistency as of RC1.
The strong consistency subsystem now maintains it's own completely
separate set of Merkle trees that are used very differently than how
normal Riak AA
Sounds like disk corruption to me.
Bryan Hunt - Client Services Engineer - Basho Technologies Limited - Registered
Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
On 29 Jul 2014, at 13:06, Effenberg, Simon wrote:
> Said to say but the issue stays the same.. even after the upgrad
Hi Simon,
Does the problem persist if you run it again?
Does it happen if you run it against any other partition?
Best Regards,
Bryan
Bryan Hunt - Client Services Engineer - Basho Technologies Limited - Registered
Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
On 29 Jul 2014
Hi,
I tried it on two different nodes with one partition each. Both multiple times
before the upgrade and after the upgrade.
I will try it on other machines in a minute but because I tried it already on
two different nodes and one of them is 2 weeks old and stored on a HP 3par I
bet that this
I tried it now with one partition on 6 different machines and everywhere the
same result: index_scan_timeout and the info: bad argument in call to
eleveldb:async_get (2x) or async_write (4x).
Von Samsung Mobile gesendet
Ursprüngliche Nachricht
Von: "Effenberg, Simon"
Datum:3
13 matches
Mail list logo
