Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008439opensim[REGION] OpenSim Corepublic2019-01-01 07:582020-05-10 03:03
Assigned To 
PlatformPCOSWindowsOS Version10
Product Versionmaster (dev code) 
Target Versionmaster (dev code)Fixed in Version 
Summary0008439: Region maptiles - can previous tiles be removed from database as they are replaced by later versions
DescriptionRegion maptiles are stored in the opensim.assets data table each time they are produced. But, as far as I understand, previous copies will never be used again. A good time to tidy the data base would seem to be at exactly the time that a new tile is stored, with older versions for that region UUID being deleted at that time.

Note that at present I occasionally do the following mysql console command while the grid is stopped and sometimes thousands of these are deleted... even on a simple grid.

DELETE FROM opensim.assets WHERE name LIKE "terrainImage_%";
TagsNo tags attached.
Git Revision or version
Run Mode Grid (Multiple Regions per Sim)
Physics EngineBulletSim
Script Engine
Environment.NET / Windows64
Mono VersionNone
Attached Files

- Relationships

-  Notes
tampa (reporter)
2019-02-05 13:37

Actually a very good question. The map tiles seem to be entered into the database as new asset even if their hash is identical. I believe they are in there for robust to be able to serve them directly, but why it creates new entries each time... strange.

I have fields for the creation date in my tables, perhaps a query to clear all but the newest tile would make more sense, then again ideally the entry in the database would be updated instead of new ones being created.
UbitUmarov (administrator)
2019-02-05 14:58
edited on: 2019-02-05 14:59

commands to delete old terrain image and parcel image are actually issued on map generation.
but they are currently ignored unless you set AllowRemoteDelete = true on robust.ini.
AllowRemoteDeleteAllTypes should stay false

tampa (reporter)
2019-02-05 15:10

Doesn't AllowRemoteDelete also enable deletion of other assets though or just the maptiles?

Why do we still store them that way if they are stored in maptiles folder, just for v1 viewers? Should those still be supported at this point?

I just issued a delete on all these entries I have on my assets table, so far nothing has caught fire, you sure these are actively used still?
UbitUmarov (administrator)
2019-02-05 15:12

AllowRemoteDeleteAllTypes should stay false <--- or all types can be deleted
tampa (reporter)
2019-02-05 15:20

What was the reasoning for setting the default to false?
UbitUmarov (administrator)
2019-02-05 15:20

reason lost in time..
tampa (reporter)
2019-02-05 15:28

So then why not change this and prevent blowing up asset tables with useless older versions of maptiles that are never even going to be used even if they happen to be requested by a v1 viewer, because I suppose that also only fetches the most current version?
aiaustin (developer)
2019-02-06 02:06

Thanks for pointing out this Robust[.HG].ini setting which I did not know about. I changed it to AllowRemoteDelete = true on the Openvue and Ailand grid.

Would it be worth setting this parameter to true by default now as these data base entries do build up.
paela argus (reporter)
2019-02-06 07:56

because if you use fsassets is not needed AllowRemoteDelete = true
use old db think for assets at this years why ?
Ferd Frederix (reporter)
2020-05-09 22:01

I had 7657 maptiles. I set AllowRemoteDelete = true in Robust.HG.ini. After clearing maptiles and restarting and making the highest version tiles, I still had 7654 maptiles in robust after all maps were regenned. AllowRemoteDelete = true had no effect.

mysql> select count(*) FROM robust.assets WHERE name LIKE "terrainImage_%";
| count(*) |
| 7657 |
1 row in set (25.36 sec)
Ferd Frederix (reporter)
2020-05-09 22:03

Also very time consuming:

mysql> delete FROM robust.assets WHERE name LIKE "terrainImage_%";
Query OK, 7657 rows affected (23 min 35.96 sec)
aiaustin (developer)
2020-05-10 03:03
edited on: 2020-05-10 04:16

Fred, I just checked my Openvue and AiLand grids and the following SQL gives exactly the number of tiles I would expect, one per region, so the deletes are working correctly in my dev master setup and have been for some time.

SELECT * FROM opensim.assets WHERE name LIKE "terrainImage_%";

One difference I can see may be relevant. I run with a single data base "opensim" for each grid. Each grid does have several servers for the add on regions, so that is not a factor. Could it be that robust.assets old map tiles are not being cleared out and that the clear out only works if its in the sane database as used for the region?

- Issue History
Date Modified Username Field Change
2019-01-01 07:58 aiaustin New Issue
2019-01-01 07:59 aiaustin Description Updated View Revisions
2019-01-01 10:51 aiaustin Description Updated View Revisions
2019-02-05 13:37 tampa Note Added: 0034325
2019-02-05 14:58 UbitUmarov Note Added: 0034326
2019-02-05 14:59 UbitUmarov Note Edited: 0034326 View Revisions
2019-02-05 15:10 tampa Note Added: 0034327
2019-02-05 15:12 UbitUmarov Note Added: 0034328
2019-02-05 15:20 tampa Note Added: 0034330
2019-02-05 15:20 UbitUmarov Note Added: 0034331
2019-02-05 15:28 tampa Note Added: 0034332
2019-02-06 02:06 aiaustin Note Added: 0034334
2019-02-06 07:56 paela argus Note Added: 0034337
2020-05-09 22:01 Ferd Frederix Note Added: 0036457
2020-05-09 22:03 Ferd Frederix Note Added: 0036458
2020-05-10 03:03 aiaustin Note Added: 0036465
2020-05-10 04:15 aiaustin Note Edited: 0036465 View Revisions
2020-05-10 04:16 aiaustin Note Edited: 0036465 View Revisions

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker