This behavior has been resolved and deployed to the production environment as of 10/30/23.
Description
The user_id and real_user_id columns point to the canvas.users table. The input format is globalised, and converted into local format, to make the joins more convenient (id % 10000000000000).
The problem is that converted IDs come from different shards, so the information in which shard that ID belongs to is lost.
Expected Behavior
User and real user IDs in the web logs should only be localised if a join can be made with the users table of the given account. Localised IDs should always have a counterpart in the users table. IDs in the web logs should never refer to the wrong user.
Workaround
No workaround exists at this time.
Steps to Reproduce
-
Login with a user that is not present in the users table of the given account.
-
You will see localised IDs showing up in the logs that may incorrectly refer to an already existing user in the users table, or a non-existent user. Users that have no counterpart in the users table are expected to show up as globalised users.
Additional Info
DAP-1670
Known issues indicate notable behaviors that has been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.
