Thank you for your quick responses.
Here are the bucket properties (using the default):
{"props":{"name”:"test","allow_mult":false,"basic_quorum":false,"big_vclock":50,"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"dw":"quorum","last_write_wins":false,"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},"n_val":3,"notfound_ok":true,"old_vclock":86400,"postcommit":[],"pr":0,"precommit":[],"pw":0,"r":"quorum","rw":"quorum","small_vclock":50,"w":"quorum","young_vclock":20}}
From the client perspective, the write call receives a success. There are no
console or error log messages on the riak nodes at the time the issue occurs.
Is there a lower level way to debug if the write succeeded?
The meta returned from the client:
{ host: '10.0.1.10',
port: '8098',
links: [],
resource: 'riak',
clientId: 'riak-js',
contentEncoding: 'utf8',
accept: 'multipart/mixed,application/json;q=0.7, */*;q=0.5',
callback: [Function],
logger: undefined,
encodeUri: false,
bucket: ’test',
key: '1382538564S9420',
contentType: 'application/json',
clientStream: undefined,
_headers:
{ vary: 'Accept-Encoding',
server: 'MochiWeb/1.1 WebMachine/1.10.0 (never breaks eye contact)',
date: 'Wed, 23 Oct 2013 19:17:28 GMT',
'content-type': 'application/json',
'content-length': '0' },
_cacheHeaders: false,
contentLength: '0',
transferEncoding: undefined,
vclock: undefined,
lastMod: undefined,
contentRange: undefined,
acceptRanges: undefined,
date: 'Wed, 23 Oct 2013 19:17:28 GMT',
statusCode: 204 }
Thanks again!
Dave
On Oct 23, 2013, at 2:42 PM, Brian Sparrow <[email protected]> wrote:
> In addition to Andrew’s question, what are the bucket properties for the
> bucket you are doing the writes against?
>
> Thanks,
>
> --
> Brian Sparrow
> Developer Advocate
> Basho Technologies
>
> Sent with Sparrow
>
> On Wednesday, October 23, 2013 at 2:40 PM, Andrew Thompson wrote:
>
>> On Wed, Oct 23, 2013 at 02:36:11PM -0400, David Greenstein wrote:
>>>
>>> Hello All,
>>>
>>> I have a Riak cluster with 5 nodes on AWS m1.large instances, all using EBS
>>> deadline scheduling. The cluster is accessed via node.js and the riak-js
>>> library using the HTTP protocol. I’ve tried it with and without connection
>>> pooling. All software has been updated to the latest versions.
>>>
>>> Occasionally, riak seems to not store an object I try to save. I have run
>>> tcpdump on the node receiving the request to ensure it is receiving the
>>> http packets with the correct JSON from the client. When the issue occurs
>>> the node is in fact receiving the request with the correct JSON.
>>>
>>> Has anyone else experienced an issue like this? Any hints on how to debug
>>> the situation would be greatly appreciated.
>>
>> What are your read and write quorums, and does the write report that it
>> suceeded?
>>
>> Andrew
>>
>> _______________________________________________
>> riak-users mailing list
>> [email protected]
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
> _______________________________________________
> riak-users mailing list
> [email protected]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
