[
https://issues.apache.org/jira/browse/COUCHDB-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035906#comment-16035906
]
ASF subversion and git services commented on COUCHDB-2594:
----------------------------------------------------------
Commit 75a7682e3db9ac021053af025fce5eb1cd78cb55 in couchdb-setup's branch
refs/heads/master from [~robertkowalski]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-setup.git;h=75a7682 ]
require nodecount on setup
when setting up a node, require the nodecount from the user. when
setting up a cluster, they will probably know it, if not the ui
other interfaces can count it easily for them. this will remove
the warning for a non matching nodecount for the user, and it
is easy to implement in uis and cli clients (e.g. a wizard for
fauxton or cli client like nmo).
once clusterwide setup lands this gets obviously superfluous.
COUCHDB-2598
This closes COUCHDB-2594
> Single node mode: remove warning
> --------------------------------
>
> Key: COUCHDB-2594
> URL: https://issues.apache.org/jira/browse/COUCHDB-2594
> Project: CouchDB
> Issue Type: Task
> Components: Database Core
> Reporter: Robert Kowalski
> Priority: Minor
> Labels: has-pr
> Fix For: 2.0.1
>
>
> we have to remove a warning that is sent as response if the node is not
> joined into a multi-node cluster and has no membership
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)