Wednesday, 2014-09-17

*** kyles_ne has quit IRC00:00
*** kyles_ne has joined #openstack-swift00:01
*** kyles_ne has quit IRC00:05
*** dmsimard is now known as dmsimard_away00:05
*** r-daneel__ has quit IRC00:24
*** dmorita has joined #openstack-swift00:26
*** mwstorer has quit IRC00:27
*** openstackgerrit has quit IRC00:31
*** openstackgerrit has joined #openstack-swift00:33
*** echevemaster has quit IRC00:45
*** kyles_ne has joined #openstack-swift00:51
*** NM has joined #openstack-swift00:56
*** mkollaro1 has quit IRC01:04
*** kyles_ne has quit IRC01:16
*** echevemaster has joined #openstack-swift01:16
*** kyles_ne has joined #openstack-swift01:16
*** addnull has joined #openstack-swift01:17
*** kyles_ne has quit IRC01:21
*** peluse_ has quit IRC01:48
*** kevinbenton has quit IRC01:48
*** echevemaster has quit IRC01:48
*** cebruns has quit IRC01:48
*** acoles has quit IRC01:48
*** smart_developer has quit IRC01:48
*** fbo has quit IRC01:48
*** infotection has quit IRC01:48
*** mitz has quit IRC01:48
*** ondergetekende has quit IRC01:48
*** nottrobin has quit IRC01:48
*** goodes has quit IRC01:48
*** zhiyan has quit IRC01:48
*** xianghui has quit IRC01:48
*** akp has quit IRC01:48
*** astellwag has quit IRC01:48
*** theanalyst has quit IRC01:48
*** otoolee has quit IRC01:48
*** ujjain has quit IRC01:48
*** peluse_ has joined #openstack-swift01:53
*** kevinbenton has joined #openstack-swift01:53
*** echevemaster has joined #openstack-swift01:54
*** cebruns has joined #openstack-swift01:54
*** acoles has joined #openstack-swift01:54
*** smart_developer has joined #openstack-swift01:54
*** fbo has joined #openstack-swift01:54
*** infotection has joined #openstack-swift01:54
*** mitz has joined #openstack-swift01:54
*** ondergetekende has joined #openstack-swift01:54
*** nottrobin has joined #openstack-swift01:54
*** goodes has joined #openstack-swift01:54
*** zhiyan has joined #openstack-swift01:54
*** xianghui has joined #openstack-swift01:54
*** akp has joined #openstack-swift01:54
*** astellwag has joined #openstack-swift01:54
*** theanalyst has joined #openstack-swift01:54
*** otoolee has joined #openstack-swift01:54
*** ujjain has joined #openstack-swift01:54
*** sendak.freenode.net sets mode: +v acoles01:54
*** mitz has quit IRC01:54
*** mitz has joined #openstack-swift01:55
*** NM has quit IRC02:23
*** bill_az has quit IRC02:32
smart_developerIn Swift, what exactly does 'ZBF' mean?02:39
smart_developer(for example, but not limited to: a 'ZBF' process).02:39
Alex_Gaynor"Zero byte file" I believe02:39
*** NM has joined #openstack-swift02:40
smart_developerThanks - then what about zero_byte_fps ?02:40
smart_developerI think ZBF might stand for zero_byte_fps ?02:41
smart_developerI'm trying to understand what zero_byte_fps and ZBF both mean when they are mentioned here:02:43
smart_developer"The auditor already uses fork(), so we decided to use the parallel02:43
smart_developer    model from the replicator.  Concurrency is set by the concurrency02:43
smart_developer    parameter in the auditor stanza, which sets the number of parallel02:43
smart_developer    checksum auditors.  The actual number of parallel auditing processes02:43
smart_developer    is concurrency + 1 if zero_byte_fps is non-zero.02:43
smart_developer02:43
smart_developer    Only one ZBF process is forked, and a new ZBF process is forked as02:43
smart_developer    soon as the current ZBF process finishes.  Thus the last process02:43
smart_developer    running will always be a ZBF process."02:43
zaitcevzero byte files per second02:44
zaitcevduuuuude02:44
smart_developerWhy would be Swift be creating zero byte files, or multiple zero-byte-files if what you're saying is correct? (that zero_byte_fps = zero byte files per second).02:45
*** vu has joined #openstack-swift02:48
zaitcevit's a separate fps for the zbf auditor. Sometimes you want to prevent it from trashing your nodes, since ZBF has no sleep interval02:48
zaitcevAs for where those files come from, it's a mystery, as far as I am concerned anyway.02:49
smart_developerHow would it "trash my nodes" ?02:50
zaitcevA legend upon which Swift was founded spaketh that XFS creates those when its fsck-like code detects corruption.02:50
smart_developerzaitcev : and what do you mean that a zero byte file "has no sleep interval"?02:51
smart_developerzaitcev : So Swift puts a zero byte file wherever it sees a corrupted file ?02:51
zaitcevBut recently I mentioned it to an old XFS developer, who said that it's a stupid myth that just won't die. And in reality the only way to generate zbfs is to crash with open files. Then, the journal replays will create those.02:51
smart_developerSo is the zbf auditor's job to (1) create a zero byte file where a corrupted file exists, or (2) to remove a zero byte file whenever it sees one ?02:53
zaitcevNo, its job is to detect them and delete them, so that suffix hashes get mismatched and then replicator recovers them.02:54
zaitcevAuditor by itself never screws with objects, I think.02:54
zaitcevWell, it might quarantine, I need to look02:54
smart_developerI think I read that the auditor places corrupted files in quarantine.02:55
zaitcevAnd by trash I meant thrash02:55
smart_developerSo, why would the auditor place a zero byte file in quarantine, instead of just deleting it?02:55
*** haomaiwang has quit IRC03:18
*** haomaiwa_ has joined #openstack-swift03:19
*** NM has quit IRC03:22
portantesmart_developer: so first, an object is represented on disk as a directory with a <timestamp>.data file in it03:31
portantewith proper replication to ensure data robustness, there are 1 or more other copies of this setup on another node.03:32
portanteif during file creation of that .data file the system fails before the data is written to disk for the file, but the directory contents were written to disk, (I believe) a zero byte file will result when the disk's journal is replayed03:33
*** haomai___ has joined #openstack-swift03:34
*** haomaiwa_ has quit IRC03:38
portantewhen the auditor detects a zero byte file, it quarantines it (potentially allowing for some kind of post-trauma analysis) allowing the replicator to detect the missing object on that node, restoring it with a copy from one of the other nodes03:38
*** haomai___ has quit IRC03:41
*** haomaiwang has joined #openstack-swift03:41
openstackgerritBilly Olsen proposed a change to openstack/swift: Fix getaddrinfo if dnspython is installed.  https://review.openstack.org/11661803:43
*** haomaiw__ has joined #openstack-swift03:57
*** haomaiwang has quit IRC03:59
*** echevemaster has quit IRC04:00
*** judd7 has quit IRC04:47
goodesgood morning05:12
goodesis anyone familiar with Sahara and list_endpoints?05:14
*** kopparam has joined #openstack-swift05:18
mattoliveraugoodes: morning! ..I'm not sorry05:19
goodesmattoliverau: g'day - too me a few secs to parse your response :-S05:21
mattoliveraugoodes: lol, sorry, I wanted to greet you, but not give your hopes up on answering your questions about sahara :P05:22
goodesThis is not specific to Sahara, I am wondering/guessing if the whole goal of list_endpoints is to allow 'clients' to directly request objects from object servers and reduce latency by not going via the proxy05:22
goodesdoes that sound plausible?05:23
goodesI can wait till the US wakes up05:24
mattoliveraugoodes: oh i see.. so long as you could go directly to the end point (i.e if there is a seperate network your servers were talking on) with an internal client.05:25
mattoliverauif you were using your proxy as a gateway into your swift cluster you couldn't by pass.. and you'd loose all the proxy protection the proxy gives you. But the list_endpoint could be used like that, or for diagnosis.05:27
goodesthe documentation says 'This middleware makes it possible to integrate swift with software that relies on data locality information to avoid network overhead, such as Hadoop.'05:27
goodesbut that would not help within the network if you are going through the proxy - it would only make sense if you are using it to determine which REGION to run the job05:28
mattoliverauSo long as its accessible you could talk directly to them, like the replicators do etc.05:28
mattoliverauSo sure..05:28
mattoliverauIt doesn't solve your problem but there is a concurrent read patch in review which can be used to "hopefully" speed up latency of the proxy.05:29
goodesor ... if you were soo sensitive to latency that you directly requested it from the object server - which it kind of evil and bad05:30
mattoliveraulol, yeah.. the concurrent read helps with the latter a little, send out requests to primary nodes all at once and repond as soon as you get 1 valid reponse.05:31
zaitcevPersonally I consider that Hadoop thing a terrible kludge.05:31
*** haomaiw__ has quit IRC05:31
goodesagree, but BG is an important driver of object, so it can't be ignored05:32
*** haomaiwang has joined #openstack-swift05:32
goodesoops BG == BD == big data05:32
goodesthe concurrent read is doing parallel reads to object servers?05:33
*** haomai___ has joined #openstack-swift05:33
goodeswhat is it using?05:33
mattoliveraugreenthreads05:36
*** haomaiwang has quit IRC05:37
*** ppai has joined #openstack-swift05:38
goodeszaitcev: agree kludge - rather then doing it right trying to make it work like HDFS05:42
goodesmattoliverau: thanks for the help, getting of the train, now I need to work :-S.05:46
mattoliveraugoodes: nps, have a good day :)05:46
*** kopparam has quit IRC05:57
*** bkopilov has quit IRC06:03
*** zaitcev has quit IRC06:14
*** k4n0 has joined #openstack-swift06:26
*** nshaikh has joined #openstack-swift06:28
openstackgerritChristian Schwede proposed a change to openstack/swift: Fix bug in swift-ring-builder list_parts  https://review.openstack.org/12189306:31
*** mahatic has joined #openstack-swift06:41
*** geaaru has joined #openstack-swift06:53
mattoliverauI'm calling it a night. Night all, see talk to some of you at the swift meeting.07:17
*** foexle has joined #openstack-swift07:27
*** bkopilov has joined #openstack-swift07:28
*** jamiehannaford has joined #openstack-swift07:57
*** Dafna has joined #openstack-swift08:29
*** nshaikh has quit IRC09:08
*** addnull has quit IRC09:37
*** mkollaro has joined #openstack-swift09:56
*** aix has joined #openstack-swift09:57
*** addnull has joined #openstack-swift10:27
*** addnull has quit IRC11:12
*** dmorita has quit IRC11:12
*** addnull has joined #openstack-swift11:17
*** judd7 has joined #openstack-swift11:21
*** NM has joined #openstack-swift11:30
*** occupant has quit IRC11:39
*** NM has quit IRC11:39
*** occupant has joined #openstack-swift11:44
*** dmsimard_away is now known as dmsimard11:48
*** NM has joined #openstack-swift11:48
*** NM has quit IRC12:00
*** judd7 has quit IRC12:08
*** jamiehannaford has quit IRC12:08
*** hhuang has joined #openstack-swift12:09
*** jamiehannaford has joined #openstack-swift12:09
*** ttrumm has joined #openstack-swift12:13
*** k4n0 has quit IRC12:14
*** addnull has quit IRC12:28
*** sandywalsh has quit IRC12:37
*** NM has joined #openstack-swift12:48
*** dencaval has quit IRC12:49
*** kopparam has joined #openstack-swift12:55
*** aix has quit IRC13:00
*** kopparam has quit IRC13:03
*** kopparam has joined #openstack-swift13:04
*** miqui has joined #openstack-swift13:06
*** kopparam has quit IRC13:08
*** jamiehannaford has quit IRC13:08
*** jamiehannaford has joined #openstack-swift13:11
*** echevemaster has joined #openstack-swift13:17
*** judd7 has joined #openstack-swift13:19
*** tdasilva has joined #openstack-swift13:23
openstackgerritLorcan Browne proposed a change to openstack/swift: Add "--no-overlap" option to swift-dispersion populate  https://review.openstack.org/11841113:24
*** aix has joined #openstack-swift13:27
*** kopparam has joined #openstack-swift13:34
*** bsdkurt has quit IRC13:36
*** bsdkurt has joined #openstack-swift13:37
*** kopparam has quit IRC13:38
*** judd7 has quit IRC13:39
*** hhuang has quit IRC13:40
*** judd7 has joined #openstack-swift13:46
openstackgerritAlistair Coles proposed a change to openstack/swift: Early checks for data migration config and headers  https://review.openstack.org/12183113:48
tdasilvaacoles: do I need to do anything to make it easier for Gil to squash that patch? wondering if I need to separate the new driver into its own patch???13:49
tdasilvanot sure what the process is like...13:49
acolestdasilva: good morning! yes, it would be helpful if you separated out your driver into another review that is dependent on your current one with the interface refactoring13:57
*** kopparam has joined #openstack-swift13:57
*** nshaikh has joined #openstack-swift13:57
acolestdasilva: just want to check - are you happy for your refactoring to be squashed into gvernik's patch?13:58
tdasilvaacoles: absolutely! :-) he could squash the whole thing if he wanted, no problem13:59
tdasilvaacoles: but I can separate the patches too if you think it makes sense to have the new driver as a new future patch13:59
*** hhuang has joined #openstack-swift14:00
acolestdasilva: great. perhaps we should keep your driver separate for easier review. idk, it might make reviewing easier14:01
tdasilvatrue true14:01
tdasilvai will do that14:01
acolestdasilva: btw gvernik told me out of band that he is happy with those refactorings14:03
tdasilvaacoles: yeah, he mentioned that in a comment too, which is cool...I think mattoliverau also took a look and liked it14:04
openstackgerritChristian Schwede proposed a change to openstack/swift: Limit partition movement when rebalancing  https://review.openstack.org/12142214:04
*** bkopilov has quit IRC14:05
*** ppai has quit IRC14:17
*** judd7 has quit IRC14:21
*** mahatic has quit IRC14:24
*** cschwede has joined #openstack-swift14:34
*** goodes has quit IRC14:36
*** jdaggett has quit IRC14:36
*** zhiyan has quit IRC14:36
*** serverascode has quit IRC14:36
*** Alex_Gaynor has quit IRC14:36
*** mahatic has joined #openstack-swift14:41
openstackgerritLorcan Browne proposed a change to openstack/swift: Add "--no-overlap" option to swift-dispersion populate  https://review.openstack.org/11841114:45
*** Alex_Gaynor has joined #openstack-swift14:48
*** zhiyan has joined #openstack-swift14:48
*** ttrumm_ has joined #openstack-swift14:51
*** goodes_ has joined #openstack-swift14:53
*** jdaggett has joined #openstack-swift14:53
*** serverascode has joined #openstack-swift14:53
*** nshaikh has left #openstack-swift14:54
*** ttrumm has quit IRC14:54
*** judd7 has joined #openstack-swift14:59
*** foexle has quit IRC15:04
*** zaitcev has joined #openstack-swift15:05
*** ChanServ sets mode: +v zaitcev15:05
*** kopparam has quit IRC15:06
*** judd7 has quit IRC15:07
*** judd7 has joined #openstack-swift15:08
*** ttrumm_ has quit IRC15:12
*** tongli has joined #openstack-swift15:14
*** kevinc has joined #openstack-swift15:15
*** AbyssOne is now known as JelleB15:19
*** LarsN has joined #openstack-swift15:19
*** jasondotstar has joined #openstack-swift15:21
*** aix has quit IRC15:28
*** judd7 has quit IRC15:29
*** aix has joined #openstack-swift15:40
*** Victor__ has quit IRC15:47
*** cschwede has quit IRC15:49
*** jamiehannaford has quit IRC15:54
*** chuck_ has joined #openstack-swift15:58
*** judd7 has joined #openstack-swift15:59
*** jamiehannaford has joined #openstack-swift16:01
*** dmsimard is now known as dmsimard_away16:10
*** kyles_ne has joined #openstack-swift16:13
*** hhuang has quit IRC16:16
openstackgerritAlan Erwin proposed a change to openstack/swift: Adding object partition check  https://review.openstack.org/12219416:20
*** vu has quit IRC16:28
*** mwstorer has joined #openstack-swift16:29
*** chuck_ has quit IRC16:50
notmynamehello, everything16:58
notmynameI wasn't online at all yesterday, so I'm catching up this morning16:58
notmynamewhat did I miss?16:58
*** tongli has quit IRC17:00
*** occupant has quit IRC17:00
*** mkollaro has quit IRC17:00
*** briancline has quit IRC17:00
*** fifieldt_ has quit IRC17:00
*** wer has quit IRC17:00
*** tongli has joined #openstack-swift17:00
*** occupant has joined #openstack-swift17:00
*** mkollaro has joined #openstack-swift17:00
*** briancline has joined #openstack-swift17:00
*** fifieldt_ has joined #openstack-swift17:00
*** wer has joined #openstack-swift17:00
*** echevemaster has quit IRC17:00
*** yuan has quit IRC17:00
*** LarsN has quit IRC17:00
*** byeager_away has quit IRC17:00
notmynameswift team meeting in 2 hours in #openstack-meeting17:01
*** gyee has joined #openstack-swift17:02
*** LarsN has joined #openstack-swift17:02
*** echevemaster has joined #openstack-swift17:02
*** yuan has joined #openstack-swift17:02
*** byeager_away has joined #openstack-swift17:02
*** Dafna has quit IRC17:02
*** Dafna has joined #openstack-swift17:02
*** tkay has joined #openstack-swift17:21
*** geaaru has quit IRC17:22
*** tsg has joined #openstack-swift17:29
smart_developerIf allow_versions is not mentioned in the container server config, does that mean it is set to True, or False, by default?17:39
smart_developerIt is the one that specifies whether Object Versioning is enabled or not.17:39
smart_developerhttp://docs.openstack.org/developer/swift/overview_object_versioning.html17:39
smart_developermore info ^17:40
notmynamesmart_developer: what's in the sample config file?17:42
smart_developerhttps://github.com/openstack/swift/blob/master/etc/container-server.conf-sample17:45
smart_developerDoes this accurately reflect what all the default values are, for the Swift configurations?17:45
smart_developerI thought it was just a "sample" file.17:46
smart_developerSame with the ones for proxy-server.conf-sample, account-server.conf-sample, and object-server.conf-sample.17:46
notmynamesmart_developer: yes. the sample config files accurately reflect the defaults. if a value is commented out, it's the default if not specified. if a values isn't commented out, you are required to provide your own17:46
notmynamewe've been pretty good with that over time, but just recently mattoliverau went through and audited the sample configs to ensure they are accurate (and fixed a couple of things)17:47
acolessmart_developer: iirc you do need to explicitly set allow_versions = true17:48
notmynameeg in the container server conf, pipeline (line 61) is required to be specified, but eg node_timeout (line 72) isn't and the default is 317:49
notmynamesmart_developer: so the default value for allow_versions is false, and if you want to enable it you should explicitly set it to true17:49
*** Tyger has joined #openstack-swift17:51
smart_developerAh, I see. Thank you!17:57
openstackgerritThiago da Silva proposed a change to openstack/swift: Moving data migration handling to base driver class  https://review.openstack.org/12172818:00
zaitcevI tried to review a trivial patch by dfg... oops my tree is not passing tests... hack-hack-hack... the day is over, patch is not reviewed. drop dead, raise to alarm, join meetings. patch is still not reviewed18:07
*** jamiehannaford has quit IRC18:10
*** jamiehannaford has joined #openstack-swift18:11
dfgclayg: you there?18:18
openstackgerritChristian Schwede proposed a change to openstack/swift: Limit partition movement when adding a new tier  https://review.openstack.org/12142218:22
openstackgerritChristian Schwede proposed a change to openstack/swift: Return correct number of changed partitions  https://review.openstack.org/12071318:22
claygdfg: ohia18:23
claygdfg: you should tell me to look at your sqlite error limiting branch18:23
openstackgerritChristian Schwede proposed a change to openstack/swift: Limit partition movement when adding a new tier  https://review.openstack.org/12142218:23
dfgclayg: when are you going to look at my error limiting thing? geez18:24
dfgclayg: was going to talk to you about that auditor patch18:24
claygdfg: i know, i'm a totally slacker - thanks for reminding me18:26
claygdfg: the think the quarantines all your disks?  i didn't recognize that guys names - new cat?18:26
dfgclayg: we actually did see this happen. it was kinda weird.18:26
claygdfg: that's crazy, any idea how?18:27
dfgclayg: ya he's a new guy Alan.18:27
claygHI ALAN!  WELCOME TO THE SHIT!18:27
dfgclayg: no not really. file system error?18:27
dfgalthough that doesn't make a ton of sense...18:27
claygdfg: yeah.... maybe... but it seems more likely to look like gibberish than like a valid but incorrect partition?18:28
claygdfg: did you have any luck tracking down the other copies?  all 3 valid and in place?  this one just got stuck in the wrong spot?18:28
claygjesus... how'd you even find it?18:28
dfga customer was getting a 403. the object server though it was a md5 collision- where it checks the metadata path vrs incoming path18:29
dfgbut it wasn't. it was just this weird problem.18:29
claygok... well maybe that's besides the point.  you saw it.  i totally agree the auditor should be the guy to detect it.  i guess the only question is if it should quarantine?  seems to me it'd be more helpful just to move it to the correct part...18:30
* clayg mind just blew up18:30
clayghow did the proxy *find* it if it was in the wrong partition?18:30
claygit was in the right partition.... but the path in metadata... that path shouldn't include the part?!18:30
dfgso like- customer req was to /a/c/o but when it got tot he object server somebody else's shit was sitting where /a/c/o should have been.18:31
dfgthat the object that was there didn't belong there at all. it should have been in a whole different partition18:32
claygholy wtf - thanks dhadas18:32
dfgwe're not crazy worried about this fix. this was mostly just a first bug fix for the new guy to learn the system type of thing. but still- it did happen.18:34
claygthat's weird and scary18:34
dfgya. but its also quite rare18:34
torgomaticsolar flares?18:34
dfgsomething like that- hopefully18:35
claygi still don't quite understand... was it right hash in the wrong part - or the object was in the wrong hashdir (which was in the right part)18:35
claygdfg: alright well new guy simple bug fix or not - don't see why it's more helpful to throw it out than move it to the right place18:36
claygdfg: the container replicator does a part check - and it just replicates the db's where it goes18:36
dfgso because its so off the wall i don't know about the move to the right partition thing. since at the point where this happens we're kinda in crazy territory. idk18:36
claygdfg: the auditor could move the damn thing into the right place and replication would sweep it up like any other handoff18:36
dfgclayg: thats basically what i did manually18:37
dfgi guess moving it to the right place would be ok.18:37
dfgi mean in this case that would have fixed the problem. i just don't know if that will always be the case and should be just quarantine it because its not safe to assume anything at this point18:38
claygdfg: i can think of a couple of ways a proxy might put all three copies in the wrong hashdir but no good idea how only one replica could be become in the wrong place18:39
dfgoh ya- i didn't answer that18:39
claygdfg: ok, well let's get alan licensed up - thanks for all the info18:40
claygdfg: having not seen it myself i'm inclined to trust your experience with the issue - so think about it and comment on the patch18:41
dfgclayg: ok. i should have written down all the details when this happened... i'll comment on the issue though18:43
*** tristanC has joined #openstack-swift18:43
*** elambert has joined #openstack-swift18:47
*** kyles_ne has quit IRC18:48
*** kyles_ne has joined #openstack-swift18:49
notmynamezaitcev: thanks for checking on swiftclient status18:49
zaitcevnotmyname: purely because of stuff like this - http://autoqa.fedoraproject.org/results/864711-autotest/virt08.qa/upgradepath/results/python-swiftclient-2.html18:49
zaitcevnotmyname: If you cut a release, I'll spin it for Fedora Rawhide and then the qa bot will permit me to backport fixes into F20 and F21.18:51
*** kevinc has quit IRC18:51
*** gvernik has joined #openstack-swift18:51
*** kyles_ne has quit IRC18:53
*** aix has quit IRC18:55
*** kota_ has joined #openstack-swift18:56
*** shri has joined #openstack-swift18:57
notmynamezaitcev: ah ok. after the meeting I've got to travel for the afternoon, so i'll probably cut it this evening18:57
*** Kbee has joined #openstack-swift18:59
*** cutforth has joined #openstack-swift19:00
notmynamemeeting time in #openstack-meeting19:00
*** goodes_ is now known as goodes19:02
*** gyee has quit IRC19:02
smart_developerWhat is container-sync, a middleware ?19:14
smart_developerAnd by default is it enabled?19:14
claygsmart_developer: I don't think it's enabled by default - very few middleware's are19:17
notmynamehttp://docs.openstack.org/developer/swift/overview_container_sync.html19:17
claygand it's not just a middleware = there's a background deamon19:17
claygis the meeting like now or did I miss it?19:18
claygtorgomatic: are you feeling better today?19:18
torgomaticclayg: nope19:18
claygtorgomatic: sorry to hear that bro19:18
notmynameclayg: meeting's now19:18
torgomaticclayg: thanks; I guess this is what happens when preschool starts up is the kids all swap germs that they found over the summer19:19
*** kyles_ne has joined #openstack-swift19:20
notmynametorgomatic: sharing is caring19:21
openstackgerritKeshava Bharadwaj proposed a change to openstack/swift: Provides proper error handling on builder unpickle  https://review.openstack.org/12222519:23
*** mwstorer has quit IRC19:30
*** kevinc has joined #openstack-swift19:35
openstackgerritChristian Schwede proposed a change to openstack/swift: Limit partition movement when adding a new tier  https://review.openstack.org/12142219:38
*** tongli has quit IRC19:38
* notmyname has to travel for the rest of the afternoon19:46
notmynameI'll probably be back online tonight19:47
mattoliveraunotmyname: happy travels19:47
* mattoliverau goes back to bed, see y'all in a few hours.19:47
*** cutforth has quit IRC19:49
*** kota_ has quit IRC19:49
*** aix has joined #openstack-swift19:53
*** vu has joined #openstack-swift19:53
*** gvernik has quit IRC19:57
*** vu has quit IRC19:59
*** tsg has quit IRC20:00
*** tsg has joined #openstack-swift20:00
*** kyles_ne has quit IRC20:00
*** kyles_ne has joined #openstack-swift20:00
*** Kbee has quit IRC20:18
*** aix has quit IRC20:23
*** jasondotstar has quit IRC20:26
*** dencaval has joined #openstack-swift20:26
*** jamiehannaford has quit IRC20:27
dencavalHey guys, I'm curious. Does swift-proxy land the data on disk before sending to the storage-nodes?20:27
torgomaticdencaval: no, it's streamed out20:27
dencavaltorgomatic hmm, thank you20:31
smart_developerclayg : I'm not sure if I understood you when you said "and it's not just a middleware = there's a background deamon" in regards to my question about container-sync.20:32
smart_developerCould you clarify ?20:33
*** gyee has joined #openstack-swift20:35
claygthe middleware is there for authorization mainly, the guy pushing the data to the remote cluster is a background daemon container-sync (more like the container-replicator)20:37
smart_developerclayg : Ok, so if container-sync is technically a middleware, then, why is it not specified in container-server.conf as [filter:container-sync], but rather just as [container-sync] ?20:42
claygsmart_developer: that's the daeon part, like [container-replicator] it's daemon has a configuration in the contain-server.conf20:47
*** tdasilva has quit IRC20:47
claygsmart_developer: there *is* a middleware component for authorization and that's configured in the proxy-server.conf20:47
*** mwstorer has joined #openstack-swift20:49
*** miqui has quit IRC20:53
smart_developerclayg : So without having the [filter:container-sync] portion inside proxy-server.conf, there is no point in having just [container-sync] inside container-server.conf ?20:56
torgomaticsmart_developer: do you (A) have two or more distinct Swift clusters, and (B) want to keep a small subset of containers synchronized between them?21:09
*** judd7 has quit IRC21:19
torgomaticif you don't meet both those conditions, then container sync is of no use to you and should be disabled21:23
claygtorgomatic breaks it down for ya21:31
smart_developerI see.22:06
smart_developerThank you very much.22:06
*** ZBhatti has joined #openstack-swift22:10
*** NM has quit IRC22:13
*** smart_developer has left #openstack-swift22:16
*** smart_developer has joined #openstack-swift22:16
*** W9PDS has joined #openstack-swift22:17
mattoliverauMorning.. again22:21
*** mahatic has quit IRC22:24
*** W9PDS has quit IRC22:27
openstackgerritSamuel Merritt proposed a change to openstack/swift: Reject overly-taxing ranged-GET requests  https://review.openstack.org/11757922:48
*** tgohad has joined #openstack-swift23:03
*** tsg has quit IRC23:03
smart_developerShould /var/log/swift.log (Log output of any of the Swift services - proxy, account, container, and object) have owner:group to be root:root, swift:swift, or something else ?23:05
smart_developerIf you're using rsyslog/logrotate to set up the log.23:05
mattoliverausmart_developer: if your using syslog then it should be owned by that user, so it can write, and in a linux world should have the adm group (at least in a debian world), so readonly admins can read logs.23:07
*** kevinc has quit IRC23:39
*** ZBhatti has quit IRC23:44
*** mwstorer has quit IRC23:53
*** NM has joined #openstack-swift23:57
*** tsg has joined #openstack-swift23:59

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