|Anonymous | Login | Signup for a new account||2018-11-18 03:01 PST|
|Main | My View | View Issues | Change Log | Roadmap | Summary | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008314||opensim||[GRID] Robust Server||public||2018-04-14 05:58||2018-08-14 13:50|
|Product Version||master (dev code)|
|Target Version||Fixed in Version|
|Summary||0008314: Map tile generation from robust|
|Description||At the moment when simulators are taken from the grid the maptiles of the regions stay behind. The structure used for the maptiles makes it difficult to manually clear just the tiles of the regions. The best approach is to remove all maptiles and re-generate the maptiles of all connected regions.|
The problem with that approach is that if the simulators are operated by third parties the only way to re-generate maptiles is to instruct the operators of those simulators to issue the "generate map" command or restart their simulators.
On large open grids this can take time and results in a reluctance to issue such maptile-clearances.
It would thus be a good to have a way to issue the maptile generation command from robust to be done by all currently connected simulators after a clearance of the maptile files.
Obviously the simulators will need a configuration to either delay this generation command or disable it completely should it be issued by robust rather than locally.
The alternative is to revisit maptile generation to cache the maptiles of all simulators and re-generate the larger, combined, maptiles scales based on the cached tiles and regions table once a de-registration of a simulator is received. This would obviously add load to robust every time a simulator is disconnected. It would also require robust to have logic to combine the maptiles to the regions via the grid coordinates since var-regions have more than one maptile.
|Tags||No tags attached.|
|Git Revision or version number|
|Run Mode||Grid (1 Region per Sim) , Grid (Multiple Regions per Sim)|
this is a bit related to 8315, except that map is a diferent part of grid code that knows nothing about other parts ( also a is a issue on 8315 since diferent parts maybe involved in current robust architecture )
adicionally map is a bit complex, clearing it takes several image operations and full awareness of regions state on a large map section
@UbitUmarov However, we can always come up with a region module that receives the request to generate a new Maptile for a region.
The question is: Why would someone add that module to their region, security wise.
|They can always disable it using a config line I would think, but I see a great benefit to reduce clutter on the map and save some bandwidth not loading orphaned maptiles|
Sheera Khan (reporter)
|Maybe a (configurable) cleaning by the ROBUST server could help? Any region not seen in the last x days is removed from the grid and the resp. maptile is cleared. The grid could state the timeframe in the Terms of Usage.|
|2018-04-14 05:58||tampa||New Issue|
|2018-04-14 10:31||UbitUmarov||Note Added: 0032641|
|2018-07-04 05:02||Fly-Man-||Note Added: 0032719|
|2018-07-04 07:52||tampa||Note Added: 0032724|
|2018-08-14 13:50||Sheera Khan||Note Added: 0032860|
|Copyright © 2000 - 2012 MantisBT Group|