New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with cassandra #63

Closed
tarzanjw opened this Issue Jun 26, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@tarzanjw

tarzanjw commented Jun 26, 2014

I get in error when use waitress with cassandra (https://github.com/datastax/python-driver), it is something about asyncore.

I do not know it's problem of cassandra-driver or waitress, please help me to detect it.

I posted my python script and the log to gist, here it is:

To reproduce errors, access to http://localhost:8080 after run script, the error will then randomly occur.

Thanks a lot

@bertjwregeer

This comment has been minimized.

Show comment
Hide comment
@bertjwregeer

bertjwregeer Jun 26, 2014

Member

@mcdonc and I were discussing this on IRC, we never came to a conclusion, the issue though is that both waitress and that cassandra driver are using asyncore and they are stepping on each others toes.

Member

bertjwregeer commented Jun 26, 2014

@mcdonc and I were discussing this on IRC, we never came to a conclusion, the issue though is that both waitress and that cassandra driver are using asyncore and they are stepping on each others toes.

@tarzanjw

This comment has been minimized.

Show comment
Hide comment
@tarzanjw

tarzanjw Jun 27, 2014

Thanks for reply, I tried to change cassandra to use libev instead of asyncore and everything was fine.

tarzanjw commented Jun 27, 2014

Thanks for reply, I tried to change cassandra to use libev instead of asyncore and everything was fine.

mcdonc added a commit that referenced this issue Jul 14, 2014

- Use a nonglobal asyncore socket map by default to hopefully prevent…
… conflicts

  with apps and libs that use the asyncore global socket map ala
  #63.  You can get the old
  use-global-socket-map behavior back by passing ``asyncore.socket_map`` to the
  ``create_server`` function as the ``map`` argument.

See #63
@mcdonc

This comment has been minimized.

Show comment
Hide comment
@mcdonc

mcdonc Jul 14, 2014

Member

I'm going to close this issue, as @tarzanjw indicates he has found a workaround by using a libev-backed Cassandra lib, and the commit I just made above might allow an asyncore-backed Cassandra lib to run together with waitress too.

Member

mcdonc commented Jul 14, 2014

I'm going to close this issue, as @tarzanjw indicates he has found a workaround by using a libev-backed Cassandra lib, and the commit I just made above might allow an asyncore-backed Cassandra lib to run together with waitress too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment