Update patch set 3
Patch Set 3: Code-Review+1 (1 comment) Patch-set: 3 Reviewer: Gerrit User 20870 <20870@4a232e18-c5a9-48ee-94c0-e04e7cca6543> Label: Code-Review=+1, 1a162f0ca1b814301aa9990baf04c55556b99a49
This commit is contained in:
parent
46eef48e87
commit
37b0be789f
|
@ -0,0 +1,21 @@
|
|||
{
|
||||
"comments": [
|
||||
{
|
||||
"unresolved": false,
|
||||
"key": {
|
||||
"uuid": "bea421ab_dc26f8f6",
|
||||
"filename": "/PATCHSET_LEVEL",
|
||||
"patchSetId": 3
|
||||
},
|
||||
"lineNbr": 0,
|
||||
"author": {
|
||||
"id": 20870
|
||||
},
|
||||
"writtenOn": "2024-03-22T10:44:05Z",
|
||||
"side": 1,
|
||||
"message": "I think this is okay, but it\u0027s a bit of a sticking plaster; use of the cache time will affect performance in keystone across the board vs consistency in the horizon browser. A better solution (harder) is to have a shared cache across the keystone units, or modify keystone to invalidate caches across instances (via peer, harder still), or attempt to inject some cookie affinity from the keystone unit all the way through haproxy back to the browser.",
|
||||
"revId": "0967f6ec4eacf69a5cee9b7582daed973e1dded4",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
||||
}
|
||||
]
|
||||
}
|
Loading…
Reference in New Issue