Live data from Hacker News

Call me maybe: Aerospike

aphyr.com

31–40 of 132 posts

Re: Call me maybe: Aerospike

#31
post #22

Earlier quoted context omitted.

Can you add any detail to this anecdote? It's interesting and important, but detail might help steer others appropriately. What kind of inconsistency? What kind of fluctuation?

I'm current working in AdTech. We are using counters to keep track of a lot of things that are important to us (e.g., reasons for not bidding on a given campaign, money spent within a given transaction, number of bid requests we get by exchange, etc). I personally have found two different, yet very similar, data fluctuations. The first I found when debugging an issue. I noticed the counters going up, dip down, then c…

Isn't this exactly what the article found? (search for split-brain)

Re: Call me maybe: Aerospike

#32
post #24
post #22

Earlier quoted context omitted.

I'm current working in AdTech. We are using counters to keep track of a lot of things that are important to us (e.g., reasons for not bidding on a given campaign, money spent within a given transaction, number of bid requests we get by exchange, etc). I personally have found two different, yet very similar, data fluctuations. The first I found when debugging an issue. I noticed the counters going up, dip down, then c…

Very strange. I've never encountered something like that with any database or cache. Wonder if it's somehow related to the way that your cluster is setup? How big is this cluster? Are you writing and reading to the entire cluster, or do you have certain nodes that you write to and others that you read from?

I have to admit, I'm not 100% on the entire configuration. However...

We have two clusters of 8 nodes each. Each cluster is setup with 2 factor replication. The clusters are setup with cross datacenter replication.

Your read / write question is a little hard to answer. In Aerospike, a given key will always reside on the same node, something to do with how they optimize their storage. Which means that anytime you write to, or read from, a given key your query will always be routed to the same node.

Re: Call me maybe: Aerospike

#34
post #19

If you're big enough to require something like Aerospike, you're rich enough to build something like F1.

You couldn't even hire a couple of experienced engineers let alone come close to affording to build F1. There are several zeros in the cost difference.

Re: Call me maybe: Aerospike

#36
post #19

If you're big enough to require something like Aerospike, you're rich enough to build something like F1.

I can think of quite a few companies that are big enough to require something like Aerospike, but wouldn't be willing to outfit all their machines with a GPS receiver.

Re: Call me maybe: Aerospike

#37
post #24
post #22

Earlier quoted context omitted.

I'm current working in AdTech. We are using counters to keep track of a lot of things that are important to us (e.g., reasons for not bidding on a given campaign, money spent within a given transaction, number of bid requests we get by exchange, etc). I personally have found two different, yet very similar, data fluctuations. The first I found when debugging an issue. I noticed the counters going up, dip down, then c…

Very strange. I've never encountered something like that with any database or cache. Wonder if it's somehow related to the way that your cluster is setup? How big is this cluster? Are you writing and reading to the entire cluster, or do you have certain nodes that you write to and others that you read from?

The analysis in the article shows that Aerospike is designed, intentionally or not, as a loosely accurate data store. It doesn't matter how you set it up or use it.

Re: Call me maybe: Aerospike

#38
Can't say I'm surprised.

Their CTO Brian has got to be one of the most obnoxious, arrogant neckbeards I've ever had the misfortune of working with.

Though in the valley these days unbridled and unwarranted confidence in your product is often an asset.

Re: Call me maybe: Aerospike

#39
post #16

I currently work for a company that uses Aerospike quite heavily. In the past couple weeks, we have begun to notice data inconsistencies in our counters. We are seeing fluctuations in the data, despite having no decrement operations. We have the enterprise edition of Aerospike, allowing us to be in constant contact with their support team and developers. A couple weeks later, and we still have no idea why this is hap…

What is the rationale for storing monetary values in this sort of system? Not being snarky, just legitimately curious what scale of service could possibly necessitate that and what solutions didn't work beforehand.
Post reply on HN