Monday, 2018-02-05

*** jakeyip has quit IRC00:37
*** threestrands has joined #openstack-swift00:43
*** tovin07_ has joined #openstack-swift00:49
*** andybotting has quit IRC01:01
*** mtreinish has quit IRC01:58
*** mtreinish has joined #openstack-swift01:59
*** threestrands has quit IRC02:01
*** itlinux has joined #openstack-swift02:06
kota_good morning02:07
*** threestrands has joined #openstack-swift02:16
*** threestrands has quit IRC02:16
*** threestrands has joined #openstack-swift02:16
mattoliveraukota_: morning02:17
kota_mattoliverau: o/02:17
kota_mattoliverau: in this morning I found the next Vancouver summit hotel information is available at https://www.openstack.org/summit/vancouver-2018/travel/ .02:18
kota_even i just finished to get accepted about my hotel at Dublin PTG :/02:18
*** itlinux has quit IRC02:37
mattoliverauthey're keen. At least giving information as soon as possible is good. Though I think it'll be a long while before I hear from my employer letting me know if I can go or not.02:39
kota_mattoliverau: yeah, I'll try it soon as possible02:40
*** cshastri has joined #openstack-swift03:39
*** itlinux has joined #openstack-swift03:47
*** psachin has joined #openstack-swift04:06
*** threestrands has quit IRC04:07
*** itlinux has quit IRC04:12
*** threestrands has joined #openstack-swift04:19
*** threestrands has quit IRC04:19
*** threestrands has joined #openstack-swift04:19
*** threestrands has quit IRC04:36
*** threestrands has joined #openstack-swift04:37
*** ukaynar has joined #openstack-swift04:55
*** kei_yama has quit IRC05:03
*** kei_yama has joined #openstack-swift05:06
*** threestrands has quit IRC05:07
*** threestrands has joined #openstack-swift05:42
*** links has joined #openstack-swift05:46
*** threestrands has quit IRC05:47
*** threestrands has joined #openstack-swift05:47
*** links has quit IRC05:49
*** links has joined #openstack-swift05:51
*** gkadam has joined #openstack-swift05:52
*** links has quit IRC05:59
*** links has joined #openstack-swift06:00
*** threestrands_ has joined #openstack-swift06:04
*** threestrands_ has quit IRC06:04
*** threestrands_ has joined #openstack-swift06:04
*** threestrands has quit IRC06:06
*** links has quit IRC06:14
*** links has joined #openstack-swift06:16
*** m_kazuhiro has joined #openstack-swift06:35
m_kazuhirogood morning06:37
*** pcaruana has joined #openstack-swift07:04
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Fix inconsistency of account info in expirer's unit tests  https://review.openstack.org/54073507:07
*** m_kazuhiro_ has joined #openstack-swift07:15
*** rcernin has quit IRC07:18
*** m_kazuhiro has quit IRC07:19
*** d0ugal has quit IRC07:42
*** armaan has joined #openstack-swift07:44
*** d0ugal has joined #openstack-swift08:07
*** ukaynar has quit IRC08:09
*** hoonetorg has quit IRC08:15
*** silor has joined #openstack-swift08:18
*** cbartz has joined #openstack-swift08:23
*** d0ugal has quit IRC08:26
*** hoonetorg has joined #openstack-swift08:28
*** tesseract has joined #openstack-swift08:28
*** kei_yama has quit IRC08:32
*** HCLTech-SSW has joined #openstack-swift08:38
*** d0ugal has joined #openstack-swift08:48
*** threestrands_ has quit IRC08:54
*** frti has joined #openstack-swift09:40
acolesgood morning09:52
*** silor has quit IRC10:13
*** tovin07_ has quit IRC10:15
*** m_kazuhiro_ has quit IRC10:19
*** kallenp has joined #openstack-swift10:38
*** kallenp has left #openstack-swift10:39
*** Key has joined #openstack-swift10:47
KeyHaving a s3 api issue10:50
KeyExact same problem as https://bugs.launchpad.net/swift/+bug/169526210:50
openstackLaunchpad bug 1695262 in OpenStack Object Storage (swift) "swift3 middleware not working " [Undecided,New]10:50
*** hseipp has joined #openstack-swift10:51
Keynone of the solutions works10:51
*** HCLTech-SSW has quit IRC11:19
*** armaan has quit IRC11:32
*** armaan has joined #openstack-swift11:51
*** pcaruana has quit IRC12:02
*** hseipp has quit IRC12:42
*** hseipp has joined #openstack-swift12:51
*** psachin has quit IRC12:56
*** cshastri has quit IRC13:21
*** armaan has quit IRC13:48
*** armaan has joined #openstack-swift13:48
*** d0ugal has quit IRC13:55
*** hseipp has quit IRC14:09
*** hseipp has joined #openstack-swift14:14
*** d0ugal has joined #openstack-swift14:30
*** hseipp has quit IRC14:54
*** armaan has quit IRC14:58
*** armaan has joined #openstack-swift14:59
KeyHaving a s3 api issue15:17
KeyExact same problem as https://bugs.launchpad.net/swift/+bug/169526215:17
openstackLaunchpad bug 1695262 in OpenStack Object Storage (swift) "swift3 middleware not working " [Undecided,New]15:17
Keynone of the solutions works15:18
*** bob_cheesey has joined #openstack-swift15:18
*** Supun has joined #openstack-swift15:25
Key<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><RequestId>txf468d08f436a49c9a8149-005932a3fc</RequestId></Error>15:45
KeyNone of the ec3 credentials created from cli on pike works15:46
Key*ec215:47
*** armaan has quit IRC15:49
*** Key has quit IRC16:01
*** Supun has quit IRC16:06
*** Supun has joined #openstack-swift16:06
openstackgerritJames E. Blair proposed openstack/swift master: Zuul: Remove project name  https://review.openstack.org/54091516:15
*** itlinux has joined #openstack-swift16:37
*** links has quit IRC16:37
notmynamegood morning.16:40
notmynamelooks like the 2.17.0 has landed!16:40
*** itlinux has quit IRC16:40
*** gkadam has quit IRC16:47
*** itlinux has joined #openstack-swift16:48
*** gyee has joined #openstack-swift16:55
*** frti has quit IRC17:04
*** cbartz has quit IRC17:05
*** d0ugal has quit IRC17:15
*** d0ugal has joined #openstack-swift17:23
*** Supun has quit IRC17:24
*** ukaynar has joined #openstack-swift17:38
*** d0ugal has quit IRC18:13
*** d0ugal has joined #openstack-swift18:27
*** itlinux has quit IRC18:31
*** armaan has joined #openstack-swift18:42
*** d0ugal has quit IRC18:59
*** itlinux has joined #openstack-swift19:07
openstackgerritJohn Dickinson proposed openstack/swift master: made changelog section breaks more consistent  https://review.openstack.org/54097819:18
*** d0ugal has joined #openstack-swift19:23
*** tesseract has quit IRC19:36
*** frti has joined #openstack-swift20:01
*** armaan_ has joined #openstack-swift20:04
*** armaan has quit IRC20:04
*** ukaynar has quit IRC20:04
*** armaan_ has quit IRC20:04
*** armaan has joined #openstack-swift20:05
*** itlinux has quit IRC20:06
*** mrjk_ has joined #openstack-swift20:18
*** itlinux has joined #openstack-swift20:23
mrjk_Hi!20:31
mrjk_We have an issue with our swift cluster, and I come here to get some advice. We have a policy with 2.5 replicats and few nodes associated to this policy (5). It happens replicator failed few days ago on node4 and we had a config issue on node5 (hash prefix and hash suffix was not set, so everything was copied, and directly pushed into quarentine. The quarentine folders has been unfortunately emptied since). We rebalanced 3 times before discovering the20:31
mrjk_problem. Everything is fine for object with 3 replicats, but not for objects with two replicats which would have been moved from node4 to node5 during the three rebalances. So now, we basically hit some 404 for the missing objects.20:31
mrjk_As the replicator was broken on node4, we strongly think all data are still on node4 (has they are deleted only once they have been replicated), but we are wondering what we could do to recover these unreplicated objects, and place them correctly on the good servers (not only node05 has there were 3 rebalance). Right know, we didn't restarted the replicator services, but we are thinking about two solutions:20:32
mrjk_1) Restart the replicator on node4, by hopping everything will get back on place (but we have strong doubts as we rebalanced 3 times)20:32
mrjk_2) Redeploy the setp by step the last three rebalanced rings on node04 (but we don't know if that will success either), and restart replicator service.20:32
mrjk_Do you have any advice to give me? (I would be very very gratefull)20:32
*** onovy has quit IRC20:33
mrjk_s/replicats/replicas/g20:38
*** onovy has joined #openstack-swift20:39
*** spiette has joined #openstack-swift20:40
notmynamemrjk_: replication will still continue to move stuff to the right place. at first guess, your first option sounds better20:59
mrjk_@notmyname, Even if 3 ring rebalances has passed since the replicator on node4 hung ?21:01
notmynamethe reason you want to replicate after every rebalance is to limit the data movement per replication cycle. the replicator can still move the data in the right place after multiple rebalanaces; it's just more likely that more data has to move21:02
mrjk_notmyname, How does the replicator know where to find the source of the object to replicate if the object is orphaned? The handoff partitions?21:04
notmynamereplication is push-based. so it finds whatever it has on its local drives and looks up where it's supposed to be in the cluster. if it doesn't match remotely, it will push local data to the other node. replication never pulls data from other places21:05
mrjk_We did find references to the orphaned object deep in the list of handoffs (swift-get-nodes -a ) but not in primary handoffs. How does it know where to find where to find the object?21:06
notmynamewhat do you mean by "orphaned"?21:07
mrjk_We had lost access to some objects (404) due to a chain of events on two nodes at the same time. This affected objects in the ring that only had 2 replicas and were on both of those nodes.21:08
mrjk_storage policy replica count is 2.521:08
notmynameso you're saying orphaned to refer to objects that are stored somewhere in the cluster but currently are returning 404s?21:09
mrjk_Correct. Node5 swift.conf was deployed w/ a bad hash and node4 replicator hung. We quickly noticed for node5, but node4 had a hung replicator for about 7 days and we rebalanced 3 times since.21:09
notmynameok, those are two separate issues with different resolutions, but let's focus on the latter (since you said you figured out the former already)21:10
mrjk_So objects that got onto Node5 while it's swift.conf was bad *and* whose second copy happened to be on Node4 are orphaned21:10
mrjk_Happened to be on Node4 at that time I mean.21:11
notmynamein this case, you'd make sure every node has the most up-to-date ring and make sure replication is running everywhere. monitor the replication process and tune to make sure it goes as quickly as possible21:11
notmynameah21:11
notmynamefor the other problem, the one where you had the bad hash, that's more tricky21:12
mrjk_We should also note that we deleted the quarantine directories on Node5 since we didn't think we would need them (we didn't know about the replicator problem on Node4 at the time)21:12
notmynameok21:12
notmynamequarantine should have only been holding stuff that had detected bit rot. not misplaced data21:12
mrjk_No no, it was directory hash not matching ERROR due to bad hash prefix in swift.conf21:13
mrjk_A sample log from the time: an 29 23:08:21 msr-iaas-obj05 object-auditor: Quarantined object /srv/node/D22/objects/68286/1bb/855f2a9dee3d92c8b3b2abfd998c31bb/1481798668.55028.data: Hash of name in metadata does not match directory name21:15
mrjk_I guess the question is since these orphaned objects have correct references deep in the list of handoffs, will the replicator know to use the full list of handoffs?21:17
*** ukaynar has joined #openstack-swift21:21
*** rcernin has joined #openstack-swift21:26
*** itlinux has quit IRC21:45
*** itlinux has joined #openstack-swift21:54
openstackgerritMerged openstack/swift master: Fix inconsistency of account info in expirer's unit tests  https://review.openstack.org/54073522:25
openstackgerritMerged openstack/swift master: Zuul: Remove project name  https://review.openstack.org/54091522:26
*** armaan has quit IRC22:26
*** armaan has joined #openstack-swift22:27
*** early has quit IRC22:31
*** frti has quit IRC22:32
mattoliveraumorning22:33
*** early has joined #openstack-swift22:33
*** ukaynar has quit IRC22:42
mrjk_Ok, after some analysis, we found that restarting the service solve our problem. Thank for your help notmyname :)22:45
*** saint_ has joined #openstack-swift22:47
*** itlinux has quit IRC22:48
*** ukaynar has joined #openstack-swift22:53
openstackgerritSamuel Merritt proposed openstack/swift master: Add fallocate_reserve to account and container servers.  https://review.openstack.org/54105822:56
*** saint_ has quit IRC23:14
*** ukaynar has quit IRC23:16
*** threestrands has joined #openstack-swift23:19
*** ukaynar has joined #openstack-swift23:24
*** ukaynar has quit IRC23:36
*** ukaynar has joined #openstack-swift23:37
*** ukaynar has quit IRC23:47
*** ukaynar has joined #openstack-swift23:49

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!