gevent monkeypatching breaks celery

[jbittel]

gevent monkeypatching breaks celery

[jbittel]

Interesting...I don't currently run these two together, so I've not encountered this before. Did you try running celery with the "-P gevent" option? Is that what you mean by switching to threaded workers?

On the plus side, gevent isn't required for django-mama-cas operation, but it can certainly make SLO requests happen faster.

[Mihara]

Threaded workers is -P thread. -P gevent just crashes.

Django-rq exhibits a similar problem, which also persists on gevent 1.1rc5 when I use memcached for session storage, which is why I caught this much later.

The problem isn't that gevent is required or not required, it's that if it is required by anything else, django-mama-cas will use it, and monkeypatch it in, (whether that anything else monkeypatches it in or not) with pretty unpredictable results...

I'm going to investigate what happens if I monkeypatch everything globally all the way up in gunicorn, which will ensure, at least, that everything is monkeypatched early, but I don't really have high hopes for this. I'd have much better hopes for https://github.com/i-trofimtschuk/frequests but django-mama-cas isn't structured to take advantage of that easily.

[jbittel]

Did you have any success monkeypatching earlier in the process?

The simplest idea to sidestep this would be to add a "don't use gevent" setting to forcibly ignore it even if it's present because of some other requirement.

[Mihara]

Haven't had the opportunity to do that yet, and probably won't for a week more. :(

A setting to disable gevent even if present would be a workable stopgap measure, though I think that actually using gevent without monkeypatching would be the preferable solution.