Conversation
wohali
force-pushed
the
2.3.x
branch
2 times, most recently
from
3307c2c to
c429e49
Compare
|
Looks like it will be a good release! I like narwhal. |
nickva
left a comment
nickva
left a comment
There was a problem hiding this comment.
Nice work! Thank. Also excited for new features.
Hopefully we can get the rest of the ticket in soon.
|
Want to wait to merge until @janl has had a chance to review, but not sure if he has time. Will merge tomorrow either way. |
|
|
||
| .. rst-class:: open | ||
|
|
||
| * :ghissue:`1602`: To improve security, there has been a major change in the |
There was a problem hiding this comment.
I think this should be "there have been major changes" ... as it sounds like a list of many changes, not a single change that affects all three (query servers, SSL support, and HTTP global handlers)? Or maybe it was a single change...?
| of manual config or the cluster setup wizard to bootstrap a cluster. The progress of | ||
| the initial seeding of new nodes is exposed at the ``GET /_up`` endpoint. | ||
| * Replication supports ipv6-only peers after updating ibrowse dependency. | ||
| * :ghissue:`1543`: A CouchDB node can now be restarted via the ``/_node/$node/_restart`` |
There was a problem hiding this comment.
This is mentioned above (lines 101-103). Should these two be merged into a single bullet point?
There was a problem hiding this comment.
I can remove this one, the one farther up probably covers it
| * :ghissue:`1423`: Mango selector matching now occurs at the shard level, reducing the | ||
| network traffic within a cluster for a mango query. | ||
| * :ghissue:`1423`: Long running operations at the node level could exceed the inter-node | ||
| timeout, leading to a fabric timeout error in the logfile and a cancellation of the |
There was a problem hiding this comment.
What is a "fabric timeout error"? Perhaps some internal library/daemon/something? Is a less technical term possible, for those not intimately familiar with the internals of CouchDB?
There was a problem hiding this comment.
It's an internal library, there's no easier way to explain this. I left "fabric timeout" in there because that exact phrase shows up in the couch logfile if it happens.
| installations using the ``require_valid_user = true`` setting. | ||
| * :ghissue:`1571`: Under very heavy load, it was possible that `rexi_server` could | ||
| die in such a way that it's never restarted, leaving a cluster without the ability | ||
| to issue RPC calls - effectively rendering the cluster useless. |
There was a problem hiding this comment.
| to issue RPC calls - effectively rendering the cluster useless. | |
| to issue RPC calls, effectively rendering the cluster useless. |
There was a problem hiding this comment.
I prefer the dash here. It calls out a subclause that stands out, which it should in this case.
|
@janl I'd rather it stand on its own, since this PR only touches the |
|
@wohali that's what I meant, my question was whether you're up for taking that over from me. Sorry if I was unclear. |
5 participants
Overview
Time to add the 2.3.x release notes.
Testing recommendations
Read them and make comments!
Checklist
make checkpasses with no errors