3 ms·
Well, let's try to imagine if BNS pooped out a corrupt update. Would every BNS client just silently pass on it, or would they all instantly suicide? I'm honestl
by thedance 7y ago
Well, let's try to imagine if BNS pooped out a corrupt update. Would every BNS client just silently pass on it, or would they all instantly suicide? I'm honestly not sure it's the former.
- jchw 7y agoI don’t understand this hypothetical perhaps because I don’t know what “BNS” is in this context. However, I think it’s reasonable to assume that if you have a key-value store and you haven’t modified it to validate your scheme, that there’s no guarantee the scheme will be valid across the database, and if your code doesn’t tolerate these conditions, eventually a bug will reveal that.
- thedance 7y agohttps://landing.google.com/sre/sre-book/chapters/production-environment/ https://landing.google.com/sre/sre-book/chapters/production-...
- jchw 7y agoI did not know BNS was publicly known so apologies for playing stupid. Of course BNS is at least designed for this specific use case. So this particular error, which imo is schema validation related, is not likely to occur. I am sure some seasoned Google SREs have a good grasp on what would happen if BNS was spitting out junk, but my guess is it would at least cause outages of some kind if not crashloops.
- ufmace 7y agoSeems it's Borg Naming Service. I guess Borg is some Google-specific thing.