- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 9 2022
- Fix some variable names and exception handling.
- Update library map.
May 5 2022
When this mechanism is removed (by commenting out the logic that cares about the 25% limit), we'd expect Drydock to build 8 resources at a time (limited by number of taskmasters). It actually builds ~1-4...
We may fopen() an additional stdout and/or stderr handle, but do not fclose() it?
I am suspicious that D21794 may have broken something subtle with unix magic, since I'm seeing some hangs out of deployment scripts wrapping daemon management scripts. I think the issue is probably one of:
May 4 2022
The outline above isn't quite sufficient because when the active resource list is nonempty, we don't actually reach the "new allocation" logic. Broadly, executeAllocator() is kind of wonky and needs some additional restructuring to cover both the D19762 case ("allocate up to the resource limit before reusing resources") and the normal set of cases. The proper logic is something like:
This issue partially reproduces (consistent with the original report, not immediately consistent with my theorizing about a root cause in PHI2177 -- actually, looks like both parts are right, see below): Drydock builds ~1 working copy per minute serially until it reaches a pool size of 5 resources. Then, it begins allocating 2 simultaneous resources.
What options exist for inter-process communication?
Here's how I'm thinking about overengineering this:
May 3 2022
This was resolved as part of T13630. I didn't actually put it in the UI anywhere, but all requests will now originate from 13.56.71.101, and this isn't likely to change given the wind-down of Phacility hosting.
This is somewhat resolved and neither next steps or motivation are clear any longer, so I'm going to call it done until evidence to the contrary arises.
Perhaps a philosophical question here is: do we care about which repositories are checked out in a working copy resource?
Before, instant reclaim after lease destruction:
To create resource pressure, I'm now going to try this -- I guess I don't really need the --count flag, but it does make the terminal juggling slightly easier:
The blueprint thing was on the way toward creating allocation pressure, so D21802 allows you to select a blueprint (or a set of possible blueprints) with --blueprint. You can specify an ID or PHID:
That patch is reasonable, and shouldn't break anything as long as the list you provide is a subset of the possible list.
fill in the details a bit.
- Fix stderr vs stdout mixup.
After D21796:
(one orthogonal bug I found is that bin/drydock lease discards any blueprints provided in an attributes JSON)
(one orthogonal bug I found is that bin/drydock lease discards any blueprints provided in an attributes JSON)
Grab a test lease on the host with:
Harbormaster needs a "Working Copy" blueprint, not just a "Host" blueprint.
Here's a fairly simple way to reproduce this:
May 2 2022
How do modern servers written in C/C++ handle parallelizing requests?
Just for my own notes: