> As this plan was deleted, all IP addresses for the regional endpoint were imme... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		grogers 3 months ago \| parent \| context \| favorite \| on: Summary of the Amazon DynamoDB Service Disruption ... > As this plan was deleted, all IP addresses for the regional endpoint were immediately removed. I feel like I am missing something here... They make it sound like the DNS enactor basically diffs the current state of DNS with the desired state, and then submits the adds/deletes needed to make the DNS go to the desired state. With the racing writers, wouldn't that have just made the DNS go back to an older state? Why did it remove all the IPs entirely?

Aeolun 3 months ago [–]

1. Read state, oh, I need to delete all this.

2. Read state, oh, I need to write all this.

2. Writes

1. Deletes

Or some variant of that anyway. It happens in any system that has concurrent reader/writers and no locks.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact