Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[DOC] Recommendation on setting ptrack.map_size updated with ptrack d... #332

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

Merged
gsmolk merged 1 commit into master from doc
Feb 19, 2021

Conversation

Copy link
Contributor

@indrups indrups commented Feb 19, 2021

...ocumentation

Copy link
Contributor

gsmolk commented Feb 19, 2021

but it is not recommended to set this parameter to a value higher than 1024.

@alubennikova, so it is possible, but just not recommended?
Will the higher value actually work or it will be just forced down to 1024 ?

Copy link
Contributor Author

indrups commented Feb 19, 2021 via email

It will not be forced down. Previously it was forced down to 0, but this was a bug that is fixed. ptrack documentation now says: It is not recommended to set this parameter to a value higher than 1024. Even for <productname>&project;</productname> clusters with <replaceable>N</replaceable>&gt;1 <literal>TB</literal>, it makes sense to use a higher value only if the efficiency and sizes of backups are more critical than the potential overhead of maintaining a large PTRACK map.
...
On 19.02.2021 17:47, gsmol wrote: but it is not recommended to set this parameter to a value higher than 1024. @alubennikova <https://github.com/alubennikova>, so it is possible, but just not recommended? Will the higher value actually work or it will be just forced down to 1024 ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#332 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP763AFSHNOKMYHNVV27H5DS7Z2X5ANCNFSM4X4MANFA>.

Copy link
Contributor

gsmolk commented Feb 19, 2021

Thank you for a clarification.

@gsmolk gsmolk merged commit b1dec24 into master Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /