Question: Why does Kestrel back out of unfinished transactions when journal is replayed?

twitter-archive / kestrel

simple, distributed message queue system (inactive)

http://twitter.github.io/kestrel

Other

2.77k stars 312 forks source link

Question: Why does Kestrel back out of unfinished transactions when journal is replayed? #18

Closed ebarlas closed 14 years ago

ebarlas commented 14 years ago

It seems like it would be desirable for Kestrel to leave transactions open. Just wondering what led to the decision to back out of unfinished transactions on startup.

Thanks.

robey commented 14 years ago

what would it mean for a transaction to be open after startup, tho? once a client has disconnected, it has no way to close it, so the transaction is aborted. a restarted server seems to be the same state.

ebarlas commented 14 years ago

Ah, right. Jeez, I've been using Kestrel as a library and I forgot about the connection semantics. I'm using an HTTP front end, so I lost sight of that.

ebarlas commented 14 years ago

Closing.