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

Need to first do reset sync and then fast sync instead of the reverse #1529

Open
mahalakshme opened this issue Oct 4, 2024 · 0 comments
Open

Comments

@mahalakshme
Copy link
Contributor

mahalakshme commented Oct 4, 2024

Issue:

I changed catchment of user maha in CK prerelease env from 99 to master. Both 99 and master had fast sync setup. Did fresh sync. It did fast sync for master and then did reset sync and fetched everything freshly. So was in need to create a new user.

this is complex bcoz we dont know what fast sync setup has. so may be we cant solve it.

Need to fix:

Raised by support team - Have setup fast sync - but still taking more time
It was confusing for me as well
Users - When in CK when a user's catchment is changed to 2 from 1, both being big catchments and fast sync setup for both, first fast sync will happen with 1 and then reset sync will happen.

Analysis:

There are two cases when reset sync(without fast sync) can happen:

  • Not a fresh sync and catchment is changed and fast sync not setup for the new catchment
  • Fresh sync and fast sync not setup
  • In other cases, fast sync setup and independent of fresh or non-fresh sync - reset sync should be ignored.

How can we solve this:

  • When catchment uuid fetched by fast sync is same as the current user's catchment then don't do reset sync.
  • Whenever reset sync based on catchment happens, fast sync can be triggered.
@mahalakshme mahalakshme converted this from a draft issue Oct 4, 2024
@mahalakshme mahalakshme moved this from In Analysis to Focus Items in Avni Product Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Focus Items
Development

No branches or pull requests

1 participant