|Anonymous | Login | Signup for a new account||2021-01-17 03:42 PST|
|Main | My View | View Issues | Change Log | Roadmap | Summary | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008851||opensim||[GRID] Robust Server||public||2021-01-09 18:20||2021-01-11 04:27|
|Priority||none||Severity||minor||Reproducibility||have not tried|
|Platform||Operating System||Operating System Version|
|Target Version||Fixed in Version|
|Summary||0008851: Feature request|
|Description||Feature request - a user definable time period, for a Grid User table wipe/refresh, this would allow for stale profile information, to be automatically updated|
|Tags||No tags attached.|
|Git Revision or version number|
|Run Mode||Grid (1 Region per Sim)|
|Not sure i understand the issue this tries to address|
|after chat with dan, seems you issue was not on profiles, but griduserservice|
edited on: 2021-01-10 04:25
Well there are so many good reasons for the avatar not to be properly disconnected from the region ...
and this causes the problem exposed here, the "online" status remain on "False" in the "griduser" database.
This causes problems, for websites that display grid status/avatar onlines etc, for example ...
The result is you get miscalculations, for example avatar online -5.
But it is also a problem for viewers ... the avatar is indicated online but in reality it is offline.
And it's the same with regions elsewhere when they are badly disconnected ...
|The data exists in the databases, so it can be accessed easily through sql so really all you need to do is write some routines to run over the database and make the changes you need. There is no need to make things on robust more complicated.|
|This has been discussed in 0006744. There is no way to determine if an entry is still useful, or which entry is the correct one in case of duplicate uuid's. Better keep all, or wipe all at the risk of loosing some bits.|
That ticket is a bit outdated, it does still happen, but outside of osgrid and one or two other places I think I have not seen it since. Normally this happens if there is something with the setup not fully in sync or robust trips over itself.
GridUser maintains info about online users in case they hypergrid out at which point this data is no longer tracked, hell on earth if we tried to. So it only resets on return or new login. Simply too difficult to reliably and efficiently determine this without adding something on both ends and even then you are adding a lot of traffic to go round if you made the viewer tell the origin grid every x minutes on what their status is, no good.
Cleaning both the GridUser and presence every x hours of stale entries is easily done. On presence you can test for region null keys(although use some delays since region will be nullkey on login). For GridUser simply take all online entries, cache for a couple hours or a day, check again and remove if needed. This can be messy, but I have found not many folks capable of staying awake 24 hours or more and unlike presence it doesn't mess up as much.
This self-checking would make sense to be in robust, but that would mean a lot more for it to do and there is no 100% way to do it without potential issues as well, so you end up trading one issue for another and that's not worth the headache to implement really.
|2021-01-09 18:20||nixnerd||New Issue|
|2021-01-10 03:33||UbitUmarov||Note Added: 0037493|
|2021-01-10 03:41||UbitUmarov||Note Added: 0037494|
|2021-01-10 04:16||djphil||Note Added: 0037496|
|2021-01-10 04:17||djphil||Note Edited: 0037496||View Revisions|
|2021-01-10 04:19||djphil||Note Edited: 0037496||View Revisions|
|2021-01-10 04:25||djphil||Note Edited: 0037496||View Revisions|
|2021-01-10 08:12||tampa||Note Added: 0037499|
|2021-01-11 04:11||JeffKelley||Note Added: 0037501|
|2021-01-11 04:27||tampa||Note Added: 0037502|
|Copyright © 2000 - 2012 MantisBT Group|