spawn microproxy to cover for crashy couchdb
Bug #670054 reported by
Chad Miller
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| desktopcouch |
Won't Fix
|
Wishlist
|
Chad Miller | ||
| desktopcouch (Ubuntu) |
Won't Fix
|
Wishlist
|
Chad Miller | ||
Bug Description
couchdb crashes. We'd like to mitigate the pain that causes. Testing for a valid socket state at every operation is painful.
Instead, at the beginning access of couchdb, we should ask the DBus service what port to talk to. It should spawn a simple proxy on an arbitrary port. Any connection incoming to that port will be proxied to the actual couchdb port. When there is no couchdb running or there is a socket error at first access, it should (re-)start couchdb and begin sending the stream to the new port. When a socket error happens in the middle of a stream, it should disconnect the client end of the socket to signal the error.
Related branches
Revision history for this message
| Vincenzo Di Somma (vds) wrote | #1 |
Revision history for this message
| Chad Miller (cmiller) wrote | #2 |
| Changed in desktopcouch: | |
| status: | New → In Progress |
| Changed in desktopcouch (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Chad Miller (cmiller) |
| milestone: | none → natty-alpha-1 |
| Changed in desktopcouch (Ubuntu): | |
| status: | In Progress → Confirmed |
| Changed in desktopcouch: | |
| milestone: | 1.0 → 1.1 |
| Changed in desktopcouch (Ubuntu): | |
| milestone: | natty-alpha-1 → natty-alpha-2 |
| Changed in desktopcouch (Ubuntu): | |
| milestone: | natty-alpha-2 → natty-alpha-3 |
Revision history for this message
| Joshua Hoover (joshuahoover) wrote | #3 |
| Changed in desktopcouch (Ubuntu): | |
| milestone: | natty-alpha-3 → none |
| Changed in desktopcouch (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in desktopcouch: | |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
Great! Any concerns about trying to reuse the same port the couchdb instance was using before crashing?