-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update deploy-bare-metal.md #12432
Update deploy-bare-metal.md #12432
Conversation
no details for NAT. It is useful for distributed cluster.
@diegobelotti:Thanks for your contribution. For this PR, do we need to update docs? |
@diegobelotti:Thanks for providing doc info! |
@Demogorgon314 can you help review this PR from a technical perspective? Thanks |
site2/docs/deploy-bare-metal.md
Outdated
> If you only have one machine on which to deploy Pulsar, you only need to add one server entry in the configuration file. | ||
|
||
> If your machines are behind NAT use 0.0.0.0 as server entry for the local address. | ||
```example for configuration on server #3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
```example for configuration on server #3 | |
example for configuration on server.3 | |
```properties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, this is better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM just left a comment. PTAL.
If the node use external IP in configuration for itself, behind NAT, zookeper service won't start because it tries to put a listener on an external ip that the linux bow doesn't own. Using 0.0.0.0 start a listener on ALL that NAT network traffic can reach. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@diegobelotti any progress? Thanks |
Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com>
Sorry I'm a newbie on github. There is anything else I should do? |
@diegobelotti can you incorporate our comments? Thanks |
AS requested
Done. Is this what you mean? |
@diegobelotti exactly. We can merge this PR after it passes tests. |
* up/master: Update deploy-bare-metal.md (apache#12432) [Broker] Fix producer getting incorrectly removed from topic's producers map (apache#12846) Add error log when new jetty client (apache#12840) JavaInstanceTest should be AssertEquals (apache#12836) [Transaction] Fix transaction flaky test testMaxReadPositionForNormalPublish (apache#12681) The problem of two exception handling (apache#12744) Fix TopicPoliciesCacheNotInitException issue. (apache#12773) Added local filesystem backend for package manager (apache#12708) [Java Client] Make userProvidedProducerName final (apache#12849) optimize indention in ServerCnx#handleProducer (apache#12854)
* up/master: [Issue 12757][broker] add broker config isAllowAutoUpdateSchema (apache#12786) Update deploy-bare-metal.md (apache#12432) [Broker] Fix producer getting incorrectly removed from topic's producers map (apache#12846) Add error log when new jetty client (apache#12840) JavaInstanceTest should be AssertEquals (apache#12836) [Transaction] Fix transaction flaky test testMaxReadPositionForNormalPublish (apache#12681) The problem of two exception handling (apache#12744) Fix TopicPoliciesCacheNotInitException issue. (apache#12773) Added local filesystem backend for package manager (apache#12708)
* Update deploy-bare-metal.md no details for NAT. It is useful for distributed cluster. * Update site2/docs/deploy-bare-metal.md Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com> * Update deploy-bare-metal.md AS requested Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com>
* Update deploy-bare-metal.md no details for NAT. It is useful for distributed cluster. * Update site2/docs/deploy-bare-metal.md Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com> * Update deploy-bare-metal.md AS requested Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com>
* Update deploy-bare-metal.md no details for NAT. It is useful for distributed cluster. * Update site2/docs/deploy-bare-metal.md Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com> * Update deploy-bare-metal.md AS requested Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com>
no details for NAT. It is useful for distributed cluster.
(If this PR fixes a github issue, please add
Fixes #<xyz>
.)Fixes #
(or if this PR is one task of a github issue, please add
Master Issue: #<xyz>
to link to the master issue.)Master Issue: #
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
If
yes
was chosen, please highlight the changesDocumentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?
doc-required
(If you need help on updating docs, create a doc issue)
no-need-doc
(Please explain why)
doc
(If this PR contains doc changes)