Hi All
Erlang Solutions is exploring whether we should provide a paid Riak
annual support service given the uncertainty of what's happening with
Basho. This would allow Riak customers to have continuity of support and
not be left with a forced migration situation.
We are looking to gauge dem
Hi,
Im a software engineer from Germany and testing the performance of a
single-node Riak TS 1.40 via the Java Client at the moment.
Therefore I query statements like select sum(value) from tsdata where
time > '" + day + "' and time < '" + tomorrow + "';"
Now Ive recognised the followi
This might be a relatively benign message, which might be better at debug scope
than info scope. This would have been introduced in 2.0.8 or 2.2.2 or later.
Essentially, there are solq supervisors for each partition/index pair (for each
partition on a node), and when these supervisors start or
When you say "All not have solr on", do you mean not all nodes have search
enabled? If you are measuring Solr index latencies, then you definitely have
Solr on at least one node. Or is this just a typo?
Going on the assumption you have search enabled on all nodes (you should, if
you are usin
Hello
I'm seeing a number of Solr related issues in my error.log:
2017-06-28 06:02:58.520 [error] <0.2094.0>@yz_doc:extract_fields:165 An
exception occurred extracting fields from value with reason
{case_clause,<<200,162,171,163,243,217,229,228,195,79,125,154,98,147,163,118,199,52,170,154,85,31