Skip to content

Conversation

@jacek-lewandowski
Copy link
Contributor

No description provided.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will the version always be inconsistent for a long time ,and we are in this loop for long time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure - is it a statement or question? I think we can skip this sync if paging is not requested; if paging was requested and there happened what you say, we would never be able to return results as paging would always fail due to concurrent schema changes. On the other hand - I don't know under what circumstances that could happen?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

long time ago, in our cluster, with poor machine configuration, we some time saw that the cluster schema may be inconsistent, and it take a long time for them to reach a consistent state. Some times it due to the poor disk hung, where the system table just locate. Some time is other reasons.

So what about logging here when the loop is more than some times like 3 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I don't think this is a case - it is not waiting here for the cluster schema to be consistent - it is only the local thing - when the schema gets transformed locally, the transformation is applied in a synchronized block. A single transformation may include multiple items which are applied one by one immediately updating the snapshot. On the other hand, scheme version is updated once after the whole transformation is completed. So, here we are just waiting for that synchronized block to complete and make sure that no other synchronized transformation has started in the meantime. In other words, waiting to make sure the metadata and version pertains to the same schema.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I see.

@jacek-lewandowski
Copy link
Contributor Author

jacek-lewandowski commented Oct 27, 2023

@jacek-lewandowski
Copy link
Contributor Author

jacek-lewandowski commented Oct 31, 2023

@smiklosovic smiklosovic closed this Dec 1, 2023
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.

3 participants