Delete operation in swift-bench failed, when proxy affinity is enable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Ksenia Svechnikova |
Bug Description
ProblemType: Bug
DistroRelease: Ubuntu 12.04 LTS
Package: swift 1.9.0
On SAIO after enable proxy affinity:
[app:proxy-server]
use = egg:swift#proxy
allow_account_
account_autocreate = true
sorting_method = affinity
read_affinity = r1z1=100
write_affinity = r1
With 2 regions in the ring:
Devices: id region zone ip address port replication ip replication port name weight partitions balance meta
0 1 1 127.0.0.1 6010 127.0.0.1 6010 sdb1 1.00 131072 0.00
1 1 2 127.0.0.1 6020 127.0.0.1 6020 sdb2 1.00 131072 0.00
2 2 3 127.0.0.1 6030 127.0.0.1 6030 sdb3 1.00 131072 0.00
3 2 4 127.0.0.1 6040 127.0.0.1 6040 sdb4 1.00 131072 0.00
Swift-bench passed with failures, because the deletion work after replication has moved things to their proper homes.
swift@regions:
swift-bench 2013-07-08 13:38:58,262 INFO Auth version: 1.0
swift-bench 2013-07-08 13:38:58,969 INFO Auth version: 1.0
swift-bench 2013-07-08 13:39:01,591 INFO 1 PUTS [0 failures], 0.4/s
swift-bench 2013-07-08 13:39:16,727 INFO 60 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:39:31,960 INFO 112 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:39:47,072 INFO 170 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:40:02,137 INFO 224 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:40:17,230 INFO 274 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:40:32,339 INFO 323 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:40:47,490 INFO 381 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:41:02,624 INFO 439 PUTS [0 failures], 3.6/s
swift-bench 2013-07-08 13:41:17,880 INFO 486 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:41:33,129 INFO 533 PUTS [0 failures], 3.5/s
swift-bench 2013-07-08 13:41:48,215 INFO 579 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:42:03,287 INFO 628 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:42:18,630 INFO 681 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:42:33,833 INFO 740 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:42:49,667 INFO 789 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:43:04,873 INFO 831 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:43:20,091 INFO 879 PUTS [0 failures], 3.4/s
swift-bench 2013-07-08 13:43:35,210 INFO 920 PUTS [0 failures], 3.3/s
swift-bench 2013-07-08 13:43:50,405 INFO 967 PUTS [0 failures], 3.3/s
swift-bench 2013-07-08 13:43:58,731 INFO 1000 PUTS **FINAL** [0 failures], 3.3/s
swift-bench 2013-07-08 13:43:58,731 INFO Auth version: 1.0
swift-bench 2013-07-08 13:44:00,735 INFO 340 GETS [0 failures], 170.0/s
swift-bench 2013-07-08 13:44:15,737 INFO 3199 GETS [0 failures], 188.1/s
swift-bench 2013-07-08 13:44:30,752 INFO 5228 GETS [0 failures], 163.3/s
swift-bench 2013-07-08 13:44:45,753 INFO 7745 GETS [0 failures], 164.7/s
swift-bench 2013-07-08 13:45:00,753 INFO 9805 GETS [0 failures], 158.1/s
swift-bench 2013-07-08 13:45:03,620 INFO 10000 GETS **FINAL** [0 failures], 154.1/s
swift-bench 2013-07-08 13:45:03,620 INFO Auth version: 1.0
swift-bench 2013-07-08 13:45:05,672 INFO 110 DEL [12 failures], 53.8/s
swift-bench 2013-07-08 13:45:20,689 INFO 921 DEL [21 failures], 54.0/s
swift-bench 2013-07-08 13:45:21,976 INFO 1000 DEL **FINAL** [21 failures], 54.5/s
swift-bench 2013-07-08 13:45:21,976 INFO Auth version: 1.0
proxy.error:
Jun 26 13:58:36 regions proxy-server Handoff requested (2) (txn: tx30cf1da0b4784
Jun 26 13:58:36 regions proxy-server Handoff requested (2) (txn: txcdd5c483faf84
Jun 26 13:58:36 regions proxy-server Handoff requested (2) (txn: tx0bb91eeba5d04
Jun 26 13:58:36 regions proxy-server Handoff requested (2) (txn: txf860bc3943a14
Jul 8 13:36:22 regions proxy-server SIGTERM received
Jul 8 13:36:22 regions proxy-server Exited
Jul 8 13:37:15 regions proxy-server Started child 29295
Jul 8 13:38:46 regions proxy-server Handoff requested (1) (txn: txdf236cf5c0cb4
Jul 8 13:38:46 regions proxy-server Handoff requested (2) (txn: txdf236cf5c0cb4
Jul 8 13:39:03 regions proxy-server ERROR with Container server 127.0.0.1:6021/sdb2 re: Trying to HEAD /v1/AUTH_
Jul 8 13:39:03 regions proxy-server ERROR with Container server 127.0.0.1:6041/sdb4 re: Trying to HEAD /v1/AUTH_
Jul 8 13:45:03 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: txe82e5239b3654
Jul 8 13:45:04 regions proxy-server Object DELETE returning 503 for (404, 204) (txn: txf8eaa22100f64
Jul 8 13:45:04 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: tx7c4fbfe097094
Jul 8 13:45:04 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: txabcadddcbcb24
Jul 8 13:45:04 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: txb545dcc4e5f54
Jul 8 13:45:04 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: txeb3872e6a1e84
Jul 8 13:45:08 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: txc81de90b4cba4
Jul 8 13:45:08 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: tx73dce0eb38484
Jul 8 13:45:08 regions proxy-server Object DELETE returning 503 for (204, 404) (txn: tx197af5afff254
Jul 8 13:45:08 regions proxy-server Object DELETE returning 503 for (404, 204) (txn: tx5d5839e0e5364
Changed in swift: | |
status: | In Progress → Fix Released |
Changed in swift: | |
status: | Fix Released → Fix Committed |
Changed in swift: | |
milestone: | none → 1.10.0-rc1 |
status: | Fix Committed → Fix Released |
Changed in swift: | |
milestone: | 1.10.0-rc1 → 1.10.0 |
no longer affects: | python-swiftclient |
It seems like maybe this is a two replica ring, can you confirm?
Seems like there's a link missing from the builder output.
-Clay