Hello,
We detect in our cluster that some is wrong with that, when we shutdown a
single node from the running cluster (bin/riak stop), the connections from the
riak erlang client of remain nodes are disconnected,
This is a log from riak console.log
2014-12-11 10:38:17.915 [error] <0.820.15>
Did you make a change to the index while the node was down? Have you tried
anything else on the cluster, like running repair?
http://docs.basho.com/riak/latest/ops/running/recovery/repairing-indexes/#Repairing-Search-Indexes
On Dec 11, 2014, at 8:50 AM, Garrido wrote:
> Hello,
>
> We detect
Hi Jeffrey,
The process you outline is the current way to deal with schema
changes. I've escalated the need for a better solution since this has
been a common scenario.
--
Luke Bakken
Engineer / CSE
lbak...@basho.com
On Tue, Dec 9, 2014 at 5:29 PM, Jeffrey Peck wrote:
> I have a bucket with ab
There are two projects that are currently in the works to solve this problem:
https://github.com/basho/yokozuna/pull/439
https://github.com/basho/yokozuna/pull/427
They should both be delivered shortly.
Eric
On Dec 9, 2014, at 5:29 PM, Jeffrey Peck wrote:
> I have a bucket with about 5 milli
Hi Geoff,
Are you having issues removing the old "global" index? You should be
able to delete it this way:
curl -XDELETE riak-host:8098/search/index/global
> Is it safe to mess with anything within the Solr admin interface (is there a
> possibility of corruption from Riak -> Solr, or vice versa
Hey Luke.
There are actually some legacy items within Riak that still use the global
search index - so we haven't yet had a need to remove it. It's good to know
that there is a way to remove it though.
And just a side question - I take it you're able to remove a search index
even if there are sti
You can't remove an index if there is still a bucket referencing it via
'search_index'. You must remove that property from every referring bucket first.
Eric
On Dec 11, 2014, at 10:54 AM, Geoff Garbers wrote:
> Hey Luke.
>
> There are actually some legacy items within Riak that still use th
