Rob,
Riak Search doesn't have a traditional term-frequency count. It has
something similar but it's an estimate and it is much more expensive than a
simple table lookup. Even if it did have term-frequency it doesn't really
expose it to the outside world. Not only that, but the standard analyzer
I've been able to log a better error message regarding this:
2013-03-28 22:08:07 =ERROR REPORT
** Generic server disksup terminating
** Last message in was {'EXIT',#Port<0.1415>,normal}
** When Server state ==
[{data,[{"OS",{unix,linux}},{"Timeout",180},{"Threshold",80},{"DiskData",[{"/",
I'm using Riak 1.3 and levelDB. I found out this thread, I'm not sure if this
is somehow related:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2012-September/009425.html
--
View this message in context:
http://riak-users.197444.n3.nabble.com/Unexpected-Riak-1-3-crash-tp4027359p40
More info here: https://github.com/basho/riak/issues/301
--
View this message in context:
http://riak-users.197444.n3.nabble.com/Unexpected-Riak-1-3-crash-tp4027359p4027407.html
Sent from the Riak Users mailing list archive at Nabble.com.
___
riak-u
That's an interesting result. Once it's fully rebalanced, I'd turn it
back on and see if the fallback handoffs still fail. If they do, I'd
recommend using memory limits, rather than TTL to limit growth (also,
remember that memory limits are *per vnode*, rather than per node).
They're slower, but
Evan,
As recommended by you, I disabled the TTL on the memory backends and did a
rolling restart of the cluster. Now, things are rebalancing quite nicely.
Do you think I can turn the TTL back on once the rebalancing completes? I'd
like to ensure that the vnodes in memory don't keep growing forever
For anyone in or near Austin: Mark Phillips, Seth Thomas and I will be at Data
Day tomorrow, and Seth and I will be hosting a meetup in three weeks at Mass
Relevance. Please feel free to stop by either event and say hi.
http://www.meetup.com/Austin-Riak-Meetup/
I will be hosting more meetups i
