Stopping solrq supervisor in log; What is this?

Anybody seen this in their logs? yz_solrq_sup:stop_queue_pair:130 Stopping solrq supervisor for index <<"search1">> Searching using the index still works, however I am getting log notices for most my indexes? If you know, please tell me... Thank you! Sincerely, Robert

Re: Riak install on instance with multiple OTP's

g, and multiple installs of it, I might suggest using kerl (https://github.com/kerl/kerl). It's an excellent tool for dealing with the problem. On Sat, May 21, 2016 at 12:01 PM, Robert Latko wrote: Hi all, Quick question: I have an instance with OTP18 and I want to make it a Riak Node. I D

Re: Riak install on instance with multiple OTP's

ls of it, I might suggest using kerl (https://github.com/kerl/kerl). It's an excellent tool for dealing with the problem. On Sat, May 21, 2016 at 12:01 PM, Robert Latko wrote: Hi all, Quick question: I have an instance with OTP18 and I want to make it a Riak Node. I DL/install the OTP16 p

Riak install on instance with multiple OTP's

Hi all, Quick question: I have an instance with OTP18 and I want to make it a Riak Node. I DL/install the OTP16 patch 8 for Riak 2.1.4. How then do I use make rel to use OTP16 instead of the default OTP18?? Thanks in advance. Sincerely, Robert __

Re: cannot start solr, no logs

Hi Saran, I have a 5 node AWS c3.2xlarge instance cluster running ubuntu 14.04lts and I have my solr set to the below (yeah I know, but -Xmx will never get the full 16g's!) ; search.solr.jvm_options = -d64 -Xms1g -Xmx16g -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:G1HeapRegionSize=8m -XX

Re: ring_creation_size & ring_partition_number error joining 2.1.3 node to 2.1.1 cluster

it, change the conf for a ring size of 256, then start, then stage, plan, and commit. I am still not sure the relation ship with ring size and ring partitions. Sincerely, Robert On 03/06/2016 02:10 PM, Robert Latko wrote: Hi All, I've got a cluster in 2.1.1 and was wanting to join a

ring_creation_size & ring_partition_number error joining 2.1.3 node to 2.1.1 cluster

Hi All, I've got a cluster in 2.1.1 and was wanting to join a 2.1.3 node to it I am getting the following error: # ./bin/riak-admin cluster join a-backend@10.0.0.199 Failed: a-backend@10.0.0.199 has a different ring_creation_size So... for the new 2.1.3 # ./bin/riak-admin status | grep ring ri

Riak 2.1.3 with levelDB and EC2 instances

Hi all, I have used M3.2xlarge instances in the past because of the compute(8CPU)/memory(30GB RAM)combo. I also played around with C3.8xlarge's using similar to test against the same dataset for performance and was able to double the performance. I am to create a new cluster with 1.5 mil rec

Riak2.1.1/java.lang.OutOfMemoryError

e.codecs.lucene41.Lucene41PostingsWriter.encodeTerm(Lucene41PostingsWriter.java:572) at org.apache.lucene.codecs.BlockTreeTermsWriter$TermsWriter.writeBlock(BlockTreeTermsWriter.java:882) at org.apache.lucene.codecs.BlockTreeTermsWriter$TermsWriter.writeBlocks(BlockTreeTermsWriter.java:579) Sincerely, Robert Latko ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com