openLocalStateFrom seems to have max limit on file count about acid-state

[lemmih]

You're not closing any of the databases so maybe you're running out of file descriptors. Try changing the ulimit and run it again.

On Wednesday, June 4, 2014 at 1:06 PM, smurphy8 wrote:

https://github.com/smurphy8/broken-acid-test
I made a test that just makes a bunch of counters and breaks acid-state. with a resource busy .
since the counters are just being opened in sequentially numbered directories it doesn't seem like there should be a problem.

—
Reply to this email directly or view it on GitHub (#37).

[smurphy8]

I have ulimit set to 10k soft and 100k hard. It is breaking at 500 open timers.

[smurphy8]

Here is the output from the program after I added in a milisecond delay between state opens.

08:59:52-scott~/programs/reference/broken-acid-state-test (master)$ ./dist/build/acidStress/acidStress
"stressing system"
acidStress: <file descriptor: 1026>: hClose: invalid argument (Invalid argument)

Here are my ulimits settings...

08:59:57-scott~/programs/reference/broken-acid-state-test (master)$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 127028
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 10000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 127028
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited