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

Adding limitation in glusterfind. #678

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

schaffung
Copy link
Member

Currently the glusterfind operation
is disrupted if even one node is down
during the pre. This is due to the fact
that changelogs are required to be
captured from the specific bricks and then
aggregated.

Fixes: #677
Signed-off-by: srijan-sivakumar [email protected]

Currently the glusterfind operation
is disrupted if even one node is down
during the pre. This is due to the fact
that changelogs are required to be
captured from the specific bricks and then
aggregated.

Fixes: gluster#677
Signed-off-by: srijan-sivakumar <[email protected]>
@schaffung schaffung self-assigned this Apr 7, 2021
@schaffung
Copy link
Member Author

@aravindavk can you please review this. TIA.

@aravindavk
Copy link
Member

This looks like a bug in glusterfind. By default it should return partial results unless --disable-partial is specified.
https://github.com/gluster/glusterfs/blob/devel/tools/glusterfind/src/main.py#L365

@schaffung
Copy link
Member Author

@aravindavk , it fails when the flag isn't used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding limitation in glusterfind
2 participants