couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <kxe...@gmail.com>
Subject Re: [DISCUSS] Removing "delayed_commits"
Date Mon, 10 Nov 2014 11:44:55 GMT
+1

P.S. One of proposed use-case of delayed_commits:
https://issues.apache.org/jira/browse/COUCHDB-568
--
,,,^..^,,,


On Mon, Nov 10, 2014 at 2:40 PM, Klaus Trainer <klaus_trainer@posteo.de> wrote:
> Hello everybody.
>
> I'd like to hear your thoughts about removing the `delayed_commits`
> option together with the corresponding code paths.
>
> Note that independent of this discussion (and in contrast to 1.x
> releases), the delayed commits feature will be disabled by default in
> the upcoming 2.0 release.  I'd like to propose that we now (as we're
> already breaking API compatibility with the new major release) go the
> full way and remove that feature entirely.
>
> Speaking for myself: I've never needed that feature, and I'd certainly
> not miss it.  I remember several times where I was in the awkward
> position of having to explain it.  After recommending people to not
> enable delayed commits in production, I'd usually get asked about the
> purpose of that feature.  Then I would answer something awkward like
> "we've implemented and enabled delayed commits by default so that
> CouchDB looks good in certain benchmarks".
>
> Would you miss delayed commits?  Do you think that users would miss it,
> and if so, why?
>
> Thanks,
> Klaus
>

Mime
View raw message