© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Hello !
My bad, you are correct :)
We did set the write affinity to "none" instead of removing it from our configuration, which was perhaps causing the same issue, we probably did a mistake in the configuration when we were testing your workaround.
Now that we have removed it from our configuration, it's all good.
As you can see from the below logs, we are seeing the correct behaviour now.
But it's quite impacting for us, as we are using the region feature in order to provider a better latency/response time to our internal clients to manage their object on different DCs.
It would be great indeed to have this functionnality back, with the write_affinity, which was working perfectly with Kilo version.
As for now, it's a regression for us to not have this post_as_copy feature anymore.
Do you know if it will be difficult to develop a working fix for this ? Or to reimplement it by any chance ?
We would be happy to help and try the fix you can provide to "beta-test" it.
In the meantime, we will probably remove the write_affinity on our production environnement due to this bug, which will cause some latency for some of our clients.
Thanks in advance for your answer.
----------
PUT objet
./chkjmeter.pl -s dc1 -e preprod -p TESTCONTAINER -c NEW -o testsanswriteaf
-------
ENV :preprod
SITE :dc1
RESOURCE :NEW/testsanswr
URL :http://
-------
OBJECT CREATE OK CHECK OK http://
META ADD OK CHECK OK expired on Tue Aug 11 14:21:14 2020, NOW Tue Aug 11 14:04:35 2020
Proxy DC 1
Aug 11 14:04:30 localhost swift-proxy: 127.0.0.1 127.0.0.1 11/Aug/
Aug 11 14:04:30 localhost swift-proxy: 127.0.0.1 127.0.0.1 11/Aug/
Aug 11 14:04:34 localhost swift-proxy: 127.0.0.1 127.0.0.1 11/Aug/
Aug 11 14:04:35 localhost swift-proxy: 127.0.0.1 127.0.0.1 11/Aug/
Storage DC 1
Aug 11 14:04:29 storage01.dc1 swift-object: X - - [11/Aug/
Aug 11 14:04:30 storage01.dc1 swift-object: X - - [11/Aug/
ug 11 14:04:34 storage01.dc1 swift-object: X - - [11/Aug/
Aug 11 14:04:35 storage01.dc1 swift-object: X - - [11/Aug/
Storage DC 2
Aug 11 14:04:29 storage01.dc2 swift-object: X - - [11/Aug/
Aug 11 14:04:34 storage01.dc2 swift-object: X - - [11/Aug/
Storage DC 3
Aug 11 14:04:29 storage01.dc3 swift-object: X - - [11/Aug/
ug 11 14:04:34 storage01.dc3 swift-object: X - - [11/Aug/
----------
/# swift-get-nodes /etc/swift/
Warning: account/container specified but ring not named "container"
Account NEW
Container testsanswriteaf
Object None
Partition 3605
Hash 70aaa9106791d35
Server:Port Device X:6000 d5
Server:Port Device X:6000 d5
Server:Port Device X:6000 d3
Server:Port Device X:6000 d6 [Handoff]
Server:Port Device X:6000 d4 [Handoff]
Server:Port Device X:6000 d4 [Handoff]
curl -g -I -XHEAD "http://
curl -g -I -XHEAD "http://
curl -g -I -XHEAD "http://
curl -g -I -XHEAD "http://
curl -g -I -XHEAD "http://
curl -g -I -XHEAD "http://
Use your own device location of servers:
such as "export DEVICE=/srv/node"
ssh X "ls -lah ${DEVICE:
ssh X "ls -lah ${DEVICE:
ssh X "ls -lah ${DEVICE:
ssh X "ls -lah ${DEVICE:
ssh X "ls -lah ${DEVICE:
ssh X "ls -lah ${DEVICE:
note: `/srv/node*` is used as default value of `devices`, the real value is set in the config file on each storage node.