Andrey Smirnov
Andrey Smirnov
@btkostner @janisppc I'll take a look tomorrow
Currently aptly doesn't cleanup empty directories in pool at all, as I thought they would be created anyway if you download another mirror. I can add this feature, it should...
@avongluck-r1soft I was trying to figure out the problem here... so you are adding packages via CLI aptly while API aptly is running? Is it related to API aptly?
Also this is inefficient way to add packages (very slow), aptly can do much better job by importing more packages at once, it can do iteration on its own like...
So aptly should have fd leak somewhere. Thanks I'll keep looking.
@jalmansor just trying to understand what is going on there. as aptly via `xargs` is a process each time it runs, it should be something using too many fds for...
on a side note, I don't think having LevelDB on NFS is really good scenario (not sure about locking and consistency). I'm thinking about what is triggering this open file...
I tried to reproduce this by creating and dropping 2000 snapshots, but number of files in the db directory stays stable like it should (testing with `master` version though)
Created 10GB worth of database, 3.5k files, ulimit set to 384, still no failures
``` 22:36:08.970318 version@stat F·[7 56 395 3025] S·10GiB[1KiB 98MiB 999MiB 9GiB] Sc·[1.75 0.98 1.00 0.95] ```