Revision 4a1821de doc/design-2.1.rst
b/doc/design-2.1.rst | ||
---|---|---|
118 | 118 |
|
119 | 119 |
An interested client can query a value by making a request to a subset of the |
120 | 120 |
cluster master candidates. It will then wait to get a few responses, and use |
121 |
the one with the highest configuration serial number (which will be always |
|
122 |
included in the answer). If some candidates are stale, or we are in the middle |
|
123 |
of a configuration update, various master candidates may return different |
|
124 |
values, and this should make sure the most recent information is used. |
|
121 |
the one with the highest configuration serial number. Since the configuration |
|
122 |
serial number is increased each time the ganeti config is updated, and the |
|
123 |
serial number is included in all answers, this can be used to make sure to use |
|
124 |
the most recent answer, in case some master candidates are stale or in the |
|
125 |
middle of a configuration update. |
|
125 | 126 |
|
126 | 127 |
In order to prevent replay attacks queries will contain the current unix |
127 | 128 |
timestamp according to the client, and the server will verify that its |
Also available in: Unified diff