I built the 1.2.0pre3 (and master) and now have secondary index lookups working
in my client api; I am testing search right now but getting errors; is
RpbSearchQueryReq (PBC) implemented in 1.2?
Thanks!
Andrew
On Jun 28, 2012, at 4:26 PM, Andrew Zeneski wrote:
Thanks Sean,
Indeed,
Andrew,
Yes it is, but we have some minor dependency/build issues to resolve. The
next pre-release tag should have the appropriate fixes.
On Fri, Jun 29, 2012 at 12:17 PM, Andrew Zeneski
and...@andrewzeneski.comwrote:
I built the 1.2.0pre3 (and master) and now have secondary index lookups
There are a few things you probably want to look at in regard to how your using
ELB.
If your using the straight ELB offering (e.g. not part of a virtual private
cloud), that's probably your problem. This form of ELB was really only
designed for routing traffic from outside the AWS network to
Thanks Sean,
Would those minor issues explain this error message I get?
client_test.go:230: 0: Error processing incoming message:
error:badarg:[{erlang,list_to_float,
[[0.0,101,43,48]]},
There are other reasons to avoid using an ELB for this purpose I'd like to
add.
ELB works by resolving a DNS name to an A record, so if the ELB instance
goes down or has trouble, you will have trouble as well. This is also the
source of the scaling up issue as it takes time for the DNS records on
Perhaps, but that might some other bug. Can you describe the request you
sent?
BTW, here's the PR that should fix the build/dep problem:
https://github.com/basho/riak_core/pull/204
On Fri, Jun 29, 2012 at 12:33 PM, Andrew Zeneski
and...@andrewzeneski.comwrote:
Thanks Sean,
Would those minor
Sean,
What I am doing is very simple:
1. I install the precommit hook on my test bucket (bin/search-cmd install test)
2. I create a JSON object that looks like this {name: Andrew Zeneski} and
store it in Riak (using my API and the key 1000)
3. I create a RpbSearchQueryReq message, set ONLY the
Dear all,
I have a riak running in only one node for about 6 months without problems.
Yesterday the riak's server was power off without previous halt. Now riak
is crashing in few seconds/minutes after start. In log files I can see
problems with merge and maybe corruption of some data. Is there an
Andrew,
Thanks for the details. It looks like a breakage in the PB service w.r.t.
the internal Search API. I'll look for the source of the issue, but would
you post an issue on the issue tracker in the meantime? Here's the link:
https://github.com/basho/riak_search/issues
On Fri, Jun 29, 2012 at
https://github.com/basho/riak_search/issues/118
On Jun 29, 2012, at 2:47 PM, Sean Cribbs wrote:
Andrew,
Thanks for the details. It looks like a breakage in the PB service w.r.t. the
internal Search API. I'll look for the source of the issue, but would you
post an issue on the issue
Thank you!
On Fri, Jun 29, 2012 at 2:51 PM, Andrew Zeneski and...@andrewzeneski.comwrote:
https://github.com/basho/riak_search/issues/118
On Jun 29, 2012, at 2:47 PM, Sean Cribbs wrote:
Andrew,
Thanks for the details. It looks like a breakage in the PB service w.r.t.
the internal Search
Afternoon, Evening, Morning to All
Today's Recap comes to you live from DevOpsDays in Mountain View. We have
new code, Q A, slides, and more to take you into the weekend.
Enjoy and have a great weekend.
Mark
twitter.com/pharkmillups
Riak Recap for June 25
Thats a very useful information. Thanks guys.
I figured out the problem was with my data loading script. Plus, instead of
going through ELB, I created a pool of connections for each node.
Now I am getting around 1k writes/sec. I think I could further improve this
my using a more powerful machine
Hello all:
I've managed to get my new deployment into an odd state.
I have a three-node cluster.
After installation, I was running the riak-admin join commands.
Node #3 happend to be down because of a configuration error -- but something
seems to have been configured.
Now, when I run stats
Thats a very useful information. Thanks guys.
I figured out the problem was with my data loading script. Plus, instead of
going through ELB, I created a pool of connections for each node.
Now I am getting around 1k writes/sec. I think I could further improve this
my using a more powerful machine
Sean,
Thank you very much for all your help and an extremely fast turn around with
fixes. I have merged those two pull requests with my local branch and compiled
with R15, I am now getting back expected results from the PB search API. 1.2 is
looking very nice!
Thanks again!
Andrew
On Jun
16 matches
Mail list logo
