Is there any more information in these logs that you can share? For example,
is this the only entry with this exception? Or are there more? Are there any
associated stack traces? An EOF exception can come from many different
scenarios.
Is there anything in the Riak console.log that looks suspicious?
Finally, you might want to take a look at what is going on inside of riak when
you get into this state (slow writes to Solr), by looking at Riak stats.
You get get to Riak stats via curl, e.g.,
curl http://localhost:8098/stats | python -m json.tool
Stats you might want to pay special attention to:
riak_kv_vnodeq (min, max, median, etc) -- the aggregate length of the vnode
queues. Long vnode queues may mean your vnode is locked waiting on Solr
vnode_put_fsm_time (mean, media, percentile, etc) The amount of time spent on
average waiting for a vnode put to complete. Long times may also be indicative
of waits writing into Solr.
How is query performance, when reading from Solr? Are you sure all of the data
is making it into Solr? If AAE is turned on, do you see a lot of spurious AAE
activity?
-Fred
> On Oct 1, 2015, at 11:37 AM, ilyas <i.serg...@keepsolid.com> wrote:
>
> upd:
> There are errors in in solr log:
>
> org.apache.solr.common.SolrException;null:org.eclipse.jetty.io.EofException
>
>
>
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
