Riak bind to hostname instead of IP Address!!

[Praveen Baratam]

Hello All,

I found it on the FAQ that using hostnames instead of IP addresses will
incur a overhead! Will it be a significant overhead? I believe that if a
hostname is queried during startup, the same will be used through the life
of the VM or in an optimized case till the DNS TTL expires!!

Best,

Praveen Baratam

about.me 
ᐧ
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: How to use Search.Options in Riak Java client for Solr faceting

[Alex Moore]

Hi Santi,

Riak's Protocol Buffers interface doesn't currently support the full range
of Solr queries, this was done to keep it compatible with the old Riak 1.x
search interface.

If you need to use any search properties beyond those provided by Riak
clients, you'll need to query with a Solr driver over http for the time
being.

I'll let our PM's know that we're seeing a need for other Solr query
options, that way we can hopefully schedule it in soon.

Thanks,
Alex

On Tue, Apr 21, 2015 at 3:00 AM, Santi Kumar  wrote:

> Hi,
> I'm need to use faceting for some of the data in Riak, I know we can use
> it with Search.Options, but I couldn't find a decent way to use that. I was
> looking at any test cases, but couldn't find any. If some body used it, can
> you please post a gist or sample here.
>
> I just need to use enable facet and pass facet fields.
>
> Thanks
> Santi
>
> ___
> 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

Java Client: Thread hangs after strange exception

[Henning Verbeek]

For development, I have a single-node Riak 1.4 cluster that I'm
connecting to with the Java client 2.0.1. Both client and server are
running on the same node, connecting via localhost.

Every now and then, an update operation ... hangs. On the console I
see this strange error:

12:21:46.646 [nioEventLoopGroup-2-1] ERROR
com.basho.riak.client.core.RiakNode - Operation onException() channel:
id:-1348399652 localhost:8087 {}
io.netty.util.concurrent.BlockingOperationException:
DefaultChannelPromise@63f65d07(incomplete)
at 
io.netty.util.concurrent.DefaultPromise.checkDeadLock(DefaultPromise.java:396)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.DefaultChannelPromise.checkDeadLock(DefaultChannelPromise.java:157)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at io.netty.util.concurrent.DefaultPromise.await(DefaultPromise.java:257)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at io.netty.channel.DefaultChannelPromise.await(DefaultChannelPromise.java:129)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at io.netty.channel.DefaultChannelPromise.await(DefaultChannelPromise.java:28)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at com.basho.riak.client.core.RiakNode.doGetConnection(RiakNode.java:667)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at com.basho.riak.client.core.RiakNode.getConnection(RiakNode.java:636)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at com.basho.riak.client.core.RiakNode.execute(RiakNode.java:570)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.core.DefaultNodeManager.executeOnNode(DefaultNodeManager.java:90)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at com.basho.riak.client.core.RiakCluster.execute(RiakCluster.java:201)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at com.basho.riak.client.core.RiakCluster.execute(RiakCluster.java:195)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.api.commands.kv.StoreValue.executeAsync(StoreValue.java:117)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.api.commands.kv.UpdateValue$1.handle(UpdateValue.java:182)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.api.commands.ListenableFuture.notifyListeners(ListenableFuture.java:78)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.api.commands.CoreFutureAdapter.handle(CoreFutureAdapter.java:120)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.core.FutureOperation.fireListeners(FutureOperation.java:131)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.core.FutureOperation.setResponse(FutureOperation.java:170)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at com.basho.riak.client.core.RiakNode.onSuccess(RiakNode.java:824)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
com.basho.riak.client.core.netty.RiakResponseHandler.channelRead(RiakResponseHandler.java:58)
~[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:340)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:326)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:155)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.handler.codec.ByteToMessageCodec.channelRead(ByteToMessageCodec.java:108)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:340)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:326)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:116)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:494)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:461)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101)
[storage-backend-2.1-SNAPSHOT.jar:2.1-SNAPSHOT]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]

12:21:46.653 [nioEventLoopGroup-2-1] WARN
i.n.channel.DefaultChannelPipeline - An exception was thrown by a 

Re: Riak Java Client

[Cosmin Marginean]

Thanks Alex
Will do. The https://github.com/basho/riak-java-client/issues/512 is causing 
issues on several platforms at the moment

Cheers
Cos



On Tuesday, 28 April 2015 at 03:39, Alex Moore wrote:

> Hi Cos,
> 
> We will continue to support and develop the Java client.
> 
> With Roach's departure I'll be taking over development for it.  I've been his 
> understudy of sorts for about a year now, although my focus has been more 
> towards the .NET and PHP clients as of late. 
> 
> >Consequently, if there's no one on this right now, I'm happy to help out 
> >with current and future issues as my time allows it.
> We're happy for any of your help, if you've got any issues / bugs / great 
> ideas just submit an issue on GitHub 
> (https://github.com/basho/riak-java-client/blob/develop/CONTRIBUTING.md) and 
> we'll get the ball rolling from there.
> 
> Thanks,
> Alex
> 
> 
> On Mon, Apr 27, 2015 at 7:04 PM, Cosmin Marginean  (mailto:cosmin...@gmail.com)> wrote:
> > One quick question on the Riak Java Client.
> > 
> > Brian Roach seemed to have been the only active contributor to this. 
> > Recently he mentioned that he's leaving Basho though, so I was wondering if 
> > he'll be maintaining this moving forward.
> > 
> > Since the Riak Java client is now a fundamental part of our ecosystem, I'm 
> > very interested in its destiny (as probably many others are)
> > Consequently, if there's no one on this right now, I'm happy to help out 
> > with current and future issues as my time allows it.
> > 
> > Looking forward to hearing from you
> > 
> > Cheers
> > Cos
> > ___
> > riak-users mailing list
> > riak-users@lists.basho.com (mailto: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