Confirmed users
964
edits
CloudServices/Sync/Atomic IO: Difference between revisions
CloudServices/Sync/Atomic IO (view source)
Revision as of 23:23, 14 September 2016
, 14 September 2016→Plan for shipping Sync Atomic IO in Firefox
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
# Server is ready for client to be developed against (not officially ready for client testing) | # Server is ready for client to be developed against (not officially ready for client testing) | ||
# Server test pass 2 - server can handle production traffic for at least one node. | # Server test pass 2 - server can handle production traffic for at least one node. | ||
## no more than 10% regression in queries per sec | |||
## no regression in count of 503 statuses emitted. | |||
## no blockers | |||
## Need to fix sharding issue, merge all code to master, and final test pass | |||
## Ops run live traffic testing to baseline performance chars | |||
## Tune record size config from data around test nodes. | |||
# Server is deployed to production (server can handle atomic and partial writes from client based on header) | # Server is deployed to production (server can handle atomic and partial writes from client based on header) | ||
# Client can land in Nightly using production sync server. Server is backward compatible and sends atomic IO support header. | # Client can land in Nightly using production sync server. Server is backward compatible and sends atomic IO support header. | ||
| Line 17: | Line 21: | ||
* Client support is not blocked and active for Android, iOS, and Desktop. | * Client support is not blocked and active for Android, iOS, and Desktop. | ||
* <strike>Karl/Bobm to define "Test Pass 2"</strike> | * <strike>Karl/Bobm to define "Test Pass 2"</strike> | ||
* Need test plan for roll back scenarios, server switches headers from support to no-atomic writes support. | |||