eye timed out without responding...

[dmerrick]

Hello,

We use eye to manage a large set of resque processes... currently around 100 per server.

Unfortunately, running eye info occasionally times out, due to the low default client timeout set by eye (5 seconds).

We'd like to be able to increase that timeout easily, but the only way we could is by monkey-patching Eye::Client#attempt_command (and I don't think that is working anyway).

Is there a better way to go about this? If not, could we add an easy-to-configure timeout for configurations with many subprocesses?

[kostya]

I very rare saw client timeout, for server with 134 processes, eye info 0.381s.
5s actually is a pretty much. May be you have very big LA for the server, or may be using some custom checks (which mistakenly not using defer, and block process actors). Also you can enable debug logger to see time which server spend to prepare info command.
I think we can add timeout by env variable, like this: EYE_CLIENT_TIMEOUT=10 eye i

[dmerrick]

What does LA mean?

We don't have custom checks, but we have 100 processes, each with daemonize true and they each have a child. So it's managing 200 pids in total.

I'd like to be able to run eye info (or even eye oinfo) across ~50 servers at the same time and parse their output, but the timeout issue makes it unreliable. The EYE_CLIENT_TIMEOUT env variable would be enough for me!

[kostya]

LA is server load average.
Not need to parse, you can output json, eye i -j.

[dmerrick]

Ah, yes, we have a very high LA. That being said, we don't mind waiting for output from eye.

That's a great trick about the JSON output, thanks!

[dmerrick]

Thank you!