4.0 is still in development today.
If you tweak compaction settings and have very large shards, do take care
to leave some disk space headroom to allow the compaction process to take
place. Basically don't run your disks at 90% in production without
experience there. ;)
Kyle
On Thu, Aug 19, 2021
Hi Bob,
Ok thanks, interesting. Can you tell me when 4.0 is planned to be released
please?
Thanks
Paul
On Thu, 19 Aug 2021 at 15:19, Robert Newson wrote:
> Hi Paul,
>
>
> I think that’s reasonable though do note that compaction is also for
> performance, even if you never update or delete a do
Hi Paul,
I think that’s reasonable though do note that compaction is also for
performance, even if you never update or delete a document, as couchdb defers
rebalancing the b+tree disk structures until then (i.e, couchdb isn’t adhering
to the b+tree algorithm from literature).
Left uncompacted
Hi B (?? ;-) )
I have a log database that could encounter high frequency updates and
deletes. It's not required to be read by multiple users, but will be
updated by all users. So rather than compacting it, which at certain
frequencies of updates could lead to possible race conditions (thinking of
Hi Paul,
We welcome feedback on why the automatic compaction system (in its default
configuration or custom) is not appropriate for you.
B.
> On 19 Aug 2021, at 05:29, Paul Milner wrote:
>
> Hi Adam
>
> Thanks for the feedback. I was actually struggling with which options to set
> per chann
Hi Adam
Thanks for the feedback. I was actually struggling with which options to set
per channel and what to set them to. Anyway after more thought, I’ve decided on
a manual approach as I need it to be more custom than automatic.
But thanks again
I appreciate it.
Best regards
Paul
Sent fro
Hi Paul, sorry to hear you’re finding it a challenge to configure. The default
configuration described in the documentation does give you an example of how
things are set up:
https://docs.couchdb.org/en/3.1.1/maintenance/compaction.html#channel-configuration
Cross-referenced from that section y
Hello
I'm looking at the maintenance of my databases and how I could implement
tools to do that. Smoosh seems to be the main option, but I'm struggling to
set it up as the documentation seems a bit limited.
I have only really found this:
5.1. Compaction — Apache CouchDB® 3.1 Documentation