You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue description: When registration due date arrives auction asks from the registry the latest status of the domains to determine if the domains were registered in time or not. After receiving this information status of the results is updated on the auction side and new task/job is run to set domain not registered status in registry side and send the domains back to auction. between the end of these two jobs there is a period where auction side is updated with not registered information, but registry still accepts new registration applications for the domains. This is what happened number of domains were registered during that time and ended up in the auction simultaneously.
How to avoid this scenario in the future:
option1: add new status "pending" to the auction reservation list in the registry that blocks any registration attempts while it's set. The idea is that auction system will set that status when registration deadline is reached and then continues processing the registration and auction statuses - discover if domains have been registered and if not then update registry auction list with domain not registered status and restarting the auctions. This will make sure that domain statuses are not updated while the auction and registry data exchange is going on. This does not affect auction end times nor waiting for payment states as auction system has info on those and does not need to request any information form registry. There is no need to change the database data structure for this option
option2: add registration due date column to registry auction table so that registry can check if registration request is valid independently from auction system...
will change the reservation list model, will add additional dependencies between registry and auction, but will effectively remove the time constraint and race condition. Value needs to be updated twice -
when auction is over and waiting for payment status is set (invoice issue date+7+30)
when invoice is paid and waiting for registration status is set (invoice payment date+30)
or alternatively leave it blank and set the value only with waiting for registration status.
The text was updated successfully, but these errors were encountered:
Issue description: When registration due date arrives auction asks from the registry the latest status of the domains to determine if the domains were registered in time or not. After receiving this information status of the results is updated on the auction side and new task/job is run to set domain not registered status in registry side and send the domains back to auction. between the end of these two jobs there is a period where auction side is updated with not registered information, but registry still accepts new registration applications for the domains. This is what happened number of domains were registered during that time and ended up in the auction simultaneously.
How to avoid this scenario in the future:
option1: add new status "pending" to the auction reservation list in the registry that blocks any registration attempts while it's set. The idea is that auction system will set that status when registration deadline is reached and then continues processing the registration and auction statuses - discover if domains have been registered and if not then update registry auction list with domain not registered status and restarting the auctions. This will make sure that domain statuses are not updated while the auction and registry data exchange is going on. This does not affect auction end times nor waiting for payment states as auction system has info on those and does not need to request any information form registry. There is no need to change the database data structure for this option
option2: add registration due date column to registry auction table so that registry can check if registration request is valid independently from auction system...
will change the reservation list model, will add additional dependencies between registry and auction, but will effectively remove the time constraint and race condition. Value needs to be updated twice -
or alternatively leave it blank and set the value only with waiting for registration status.
The text was updated successfully, but these errors were encountered: