Eventing port name is wrong #1085
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#1 Note "debugPort" is wrong it will not work the correct name is "eventing_debug_port" #2 The example is wrong it must be terminated by a period for example if we had the following in static_config {eventing_debug_port, 9444} {net_kernel_verbosity, 10} The couchbase server WILL NOT start but if we add a period after the closing brace {eventing_debug_port, 9444}. {net_kernel_verbosity, 10}. The couchbase server starts #3 make the syntax clear e.g. add "(enclosed in braces and terminated by a period)" #4 warn that this will flush all data and restart the server from scratch, e.g. "WARNING: Changing port mapping should be done on the initial node/cluster setup as the required reset and reconfiguration will also purge any data on the node. "
Contributor
|
Thanks for creating this PR @jon-strabala. Can you confirm which releases, if any, that these changes should be backported to? Or are they only applicable to 6.5? |
Contributor
Author
|
Eric,
1) I tested the eventing port name and the "failure case" on a CC 7.0.0 source build.
Since you asked I just did the following:
2) I tested the eventing port name and the "failure case" on a CC 6.5.1 source build.
But since I run debian 9 I can't easily run the 6.0.X or prior releases since they are not built on http://nas.service.couchbase.com/builds/releases
Best
Jon Strabala
…________________________________
From: Eric Schneider <notifications@github.com>
Sent: Wednesday, February 26, 2020 1:51 PM
To: couchbase/docs-server <docs-server@noreply.github.com>
Cc: Jon Strabala <jon.strabala@couchbase.com>; Mention <mention@noreply.github.com>
Subject: Re: [couchbase/docs-server] Eventing port name is wrong (#1085)
Thanks for creating this PR @jon-strabala<https://github.com/jon-strabala>. Can you confirm which releases, if any, that these changes should be backported to? Or are they only applicable to 6.5?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1085?email_source=notifications&email_token=AM4RULFVNUFVVG7XIMKRMQTRE3P7RA5CNFSM4K4OUVN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENCA6KA#issuecomment-591662888>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM4RULA4WZLSRDEG6QVNGUDRE3P7RANCNFSM4K4OUVNQ>.
|
cb-docs-robot
approved these changes
Feb 26, 2020
Contributor
Author
|
Eric,
3) I tested the eventing port name and the "failure case" on Enterprise Edition 6.0.3 build 2895
couchbase-server-enterprise_6.0.3-debian8_amd64.deb
4) I tested the "failure case" on e.g.missing period on
couchbase-server-enterprise_5.1.0-debian8_amd64.deb
- Jon
…________________________________
From: Jon Strabala <jon.strabala@couchbase.com>
Sent: Wednesday, February 26, 2020 2:08 PM
To: couchbase/docs-server <reply@reply.github.com>
Subject: Re: [couchbase/docs-server] Eventing port name is wrong (#1085)
Eric,
1) I tested the eventing port name and the "failure case" on a CC 7.0.0 source build.
Since you asked I just did the following:
2) I tested the eventing port name and the "failure case" on a CC 6.5.1 source build.
But since I run debian 9 I can't easily run the 6.0.X or prior releases since they are not built on http://nas.service.couchbase.com/builds/releases
Best
Jon Strabala
________________________________
From: Eric Schneider <notifications@github.com>
Sent: Wednesday, February 26, 2020 1:51 PM
To: couchbase/docs-server <docs-server@noreply.github.com>
Cc: Jon Strabala <jon.strabala@couchbase.com>; Mention <mention@noreply.github.com>
Subject: Re: [couchbase/docs-server] Eventing port name is wrong (#1085)
Thanks for creating this PR @jon-strabala<https://github.com/jon-strabala>. Can you confirm which releases, if any, that these changes should be backported to? Or are they only applicable to 6.5?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1085?email_source=notifications&email_token=AM4RULFVNUFVVG7XIMKRMQTRE3P7RA5CNFSM4K4OUVN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENCA6KA#issuecomment-591662888>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM4RULA4WZLSRDEG6QVNGUDRE3P7RANCNFSM4K4OUVNQ>.
|
jon-strabala
added a commit
that referenced
this pull request
Feb 27, 2020
1. Add working directions to change the debug port 2. Also follows #1085 3. Also reference https://docs.couchbase.com/server/6.5/install/install-ports.html#map-custom-ports (which is fixed in above pull)
amarantha-k
pushed a commit
that referenced
this pull request
Mar 3, 2020
1. Add working directions to change the debug port 2. Also follows #1085 3. Also reference https://docs.couchbase.com/server/6.5/install/install-ports.html#map-custom-ports (which is fixed in above pull)
amarantha-k
approved these changes
Mar 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#1 Note "debugPort" is wrong it will not work the correct name is "eventing_debug_port"
#2 The example is wrong it must be terminated by a period for example if we had the following in static_config
{eventing_debug_port, 9444}
{net_kernel_verbosity, 10}
The couchbase server WILL NOT start but if we add a period after the closing brace
{eventing_debug_port, 9444}.
{net_kernel_verbosity, 10}.
The couchbase server starts
#3 make the syntax clear e.g. add "(enclosed in braces and terminated by a period)"
#4 warn that this will flush all data and restart the server from scratch, e.g. "WARNING: Changing port mapping should be done on the initial node/cluster setup as the required reset and reconfiguration will also purge any data on the node. "