Skip to content
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 ports used in HA docs #922

Closed
kgolubic opened this issue Jul 16, 2024 · 1 comment · Fixed by #1037
Closed

Update ports used in HA docs #922

kgolubic opened this issue Jul 16, 2024 · 1 comment · Fixed by #1037
Assignees
Labels
priority: high (error) A mistake in the documentation, or information that is crucial for a correct flow

Comments

@kgolubic
Copy link
Contributor

From internal Slack channel:

One port to rule them all, but should be consistent in docs.

There are configuration flags on page for High availability, but when we describing Env flags
the config is not the same as it is used in docker parameters in previous paragraph,
and that is confusing

Data and Coordinator instances paragraphs

export MEMGRAPH_BOLT_PORT=7692

There is 7692 port specified, but should be 7687 (to be consistent on this page.
https://memgraph.com/docs/clustering/high-availability

@kgolubic kgolubic added the priority: low (improvements) An idea how the representation of knowledge on a certain page could be improved label Jul 16, 2024
@katarinasupe katarinasupe added priority: high (error) A mistake in the documentation, or information that is crucial for a correct flow and removed priority: low (improvements) An idea how the representation of knowledge on a certain page could be improved labels Nov 4, 2024
@katarinasupe
Copy link
Contributor

@as51340, next time you update HA docs, can you take a look at this and make sure all ports used on the page are correct? I don't want to get into this rabbit hole now, and I think it will be easier if you update it on the fly.

@as51340 as51340 linked a pull request Nov 14, 2024 that will close this issue
31 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high (error) A mistake in the documentation, or information that is crucial for a correct flow
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants