larryruili 3d5a6b808c Change loadActiveApplicationsByDomainName to non-transactional ... We can easily end up enlisting too many entity groups (separate DomainApplications) in a TransactionalFlow when loading all applications tracked by the DomainApplicationIndex. This makes the load operation transactionless, to avoid overenlisting. Potential problems: 1. We fail to prevent landrush applications, if a single sunrise application exists. This is likely fine, except for a brief moment in Sunrush when a sunrise application is made immediately prior to a landrush application. The result is we accept an invalid application- which can be mediated manually. 2. We fail to prevent a domain create for a domain with an open application. This is a little more sinister, but also unlikely unless someone submits an application immediately before someone tries to create the same domain (sans application?) 3. We return an invalid DomainCheck response (instead of 'pending allocation'). Not the worst outcome. 4. We reduce the AuctionStatusCommand and GetApplicationIdsCommand to eventual consistency. Since they're internal tools, that's not too big a deal. A better solution: DomainApplications really should just be normalized under a virtualEntityGroup by fullyQualifiedDomainName, or a hash-bucket like EppResources are. The DomainApplication -> DomainBase -> EppResource hierarchy seems to be purely for code reuse, at the cost of Datastore consistency. This would, however, require quite some refactoring, and a custom resave operation across all DomainApplications. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=169395586		2017-10-04 16:16:44 -04:00
..
com/google/testing/builddefs	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
google/registry	Change loadActiveApplicationsByDomainName to non-transactional	2017-10-04 16:16:44 -04:00