Sync issue between DB and ES

[SathyaJayabal]

Sometimes we face the issue where the trait gets saved successfully in the DB. But the GET traits doesn't return the trait and when the user tries to add the trait again we get an error.

We have it already logged here
topcoder-platform/onboarding-processor#39

Note: The trait shows up in a couple of minutes.

sync._db_es.mov

[lakshmiathreya]

cc @Oanh-and-only-Oanh

[vikasrohit]

@SathyaJayabal @lakshmiathreya it is the exact same situation which I mentioned in topcoder-platform/onboarding-processor#39. And the reason you are seeing the language updated after some time, might be that some other profile update caused the ES to resync.

@rakibansary one possible solution could be as I mentioned somewhere else (don't remember the place), we have to check the error of the POST call and if it says trait already exists, we should make the PUT request with same payload instead of POST. That should solve most of the situations I guess.

[rakibansary]

Hi @SathyaJayabal,

This is ready for QA. Onboarding app, community app setitngs page both now uses v5 member Api. Additionally the onboarding processor has been updated to consistently store data across all clusters when a trait is updated so they are visible in search.

One known issue is when a user first signs up, their first name, last name & country are not saved as basic_info traits. The fix for this is in progress, but should not impact general sync.

[sandhiyakavi]

Verified in Dev Env. Sync issue between DB and ES is resolved.

bandicam.2021-12-14.14-45-46-379.mp4