kocolosk commented on issue #3939: URL: https://github.com/apache/couchdb/issues/3939#issuecomment-1048773500
Ah, thanks! Then the `ok` response from node B makes more sense, but I can see where we'd still run into the same issue of the `PARSER` waiting around for a receiver that was never spawned in the interactive case as well. I guess the expedient fix here might for the `FABRIC` process to kill off the `PARSER` when it knows that a response has been received from every worker? I agree that this attachment buffering system is overly complex and poorly designed (speaking as one of the designers). It'd be a pretty interesting project to design a greenfield replacement application and then figure out how to integrate that into CouchDB. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
