MongoDB and DataStax, In the Rearview Mirror

Re:MongoDB and DataStax, In the Rearview Mirror by threeseed on Wednesday June 25, 2014 @09:28AM (#7943723)

That's odd. I was under the impression that DataStax Java drivers had knowledge of the cluster and so weren't sending requests to random nodes.

http://www.datastax.com/doc-source/developer/java-apidocs/co...

[ Parent | on HN ]

Re:MongoDB and DataStax, In the Rearview Mirror by rsvihla on Wednesday June 25, 2014 @11:00AM (#7944352)

You actually have to use it though. TokenAware is one of many policies most of which can be layered on top of one another. Just depends on how they had the driver configured.

[ Parent | on HN ]

Re:MongoDB and DataStax, In the Rearview Mirror by jbellis on Wednesday June 25, 2014 @11:12AM (#7944436)

Token aware is the default now, but Thumbtack benchmarked with the two year old Thrift client instead.

[ Parent | on HN ]

Re:MongoDB and DataStax, In the Rearview Mirror by ddispaltro on Wednesday June 25, 2014 @10:54AM (#7944288)

I know the Astyanax driver from Netflix supports a "token aware" strategy. Here is a link to the docs:

https://github.com/Netflix/astyanax/wiki/Configuration

Depending on how the consistency level is set it could potentially save a "route" to the other host.

[ Parent | on HN ]

Re:MongoDB and DataStax, In the Rearview Mirror by cbsmith on Wednesday June 25, 2014 @12:26PM (#7944967)

Some drivers do. Some drivers don't. Before DataStax started providing their own driver, the default Cassandra driver didn't.

[ Parent | on HN ]