[eFEAT] Data about new league

[akasolace]

See lot of users using an old tool that predict league for next season based on ranking. Maybe we could have this somehow in HO and/or maybe simply in a static webpage

@tychobrailleur I keep here for reference a list of implemented endpoint:

[GET]

• .../league/supported => returns list of all supported leagues

• .../league/{leagueID}/status => returns status of given leagueID

• .../league/{leagueID}/next-block?accept-job={true/false} => returns the next batch to be treated, if accept-job is set to false, the block is not set to in-progress on the server

• .../league/:leagueID/team/:teamID/pd-status => returns a tuple (pmStatus, [oppTeamIDs])

[POST]

• /league/:leagueID/block/:blockID/push/ => push one block to server via json

w/ json like {"username": "john Doe", "data": [{"teamId": 73868, "Score": 970050050000000}, {"teamId": 280009, "Score": 960050050000000}, .....

[tychobrailleur]

There seems to be various timeouts in the logs:

 [Error]   HttpDataSubmitter: Timestamp: 1584957999587
 [Error]   HttpDataSubmitter: Error submitting data to HO Server: {"HTTP Status Code": 520, "Msg": "Request could not be processed", "error_desc": "'Another transaction has changed this data; aborting'", "json": {"leagueId": 5, "season": 74, "username": "capitaineFro", "data": [{"teamId": 1750670, "Score": 571852953300000}, . . .
 [Info]    LeaguePromotionHandler: Status of league: 5 : {"status_code": 1, "status_desc": "NOT_AVAILABLE", "nbBlocks": 14, "nbBlocksReady": 3, "nbBlocksInProgress": 0}
 [Info]    HttpDataSubmitter: Lock block for league 5...
 [Error]   HttpDataSubmitter: Read timed out

I am not too sure how come it looks like some of the blocks are being processed in parallel in your logs: they should be processed sequentially, to avoid putting too much load on both HT and HO servers.

I am going to run tests using league 5 rather than 21 to see if I can reproduce.

[tychobrailleur]

I am seeing similar issues as I am testing this this evening, pushes of blocks seems to timeout:

Not sure what is going on on the server, but there seems to be an issue there.

However, this situation also needs to be handled on the client side, and I see two options here:

• Either we abandon that block for now and carry on, in which case the block will be released within 30 min (or we could have another operation that the client could call to “release” the block, but if the problem is on the server, that won't make any difference);
• Or we retry until we get success — we could possibly adopt a exponential backoff strategy where we retry after an increasingly longer delay, until at some point we'd revert back to option 1.

I am tempted to go with option 2 for now (exponential backoff), and stop after 4 or 5 attempts. Thoughts?

[akasolace]

closed by 42687e3 and d014420