Account, region and inventory caches
Internal lifetimes, stale results and differences between caches and authoritative services.
Simulator user-account caches
Simulator UserAccountCache.cs stores entries by UUID and name. Code uses one hour for some ordinary accounts, 48 hours for foreign visitors and ten minutes for negative lookups. These are component-specific values, not universal account database settings.
Hypergrid service account cache differs
OpenSim/Services/HypergridService/UserAccountCache.cs is another component, with approximately five-minute expiration. Do not confuse it with the simulator UserAccountCache: their purpose and invalidation methods differ.
New or renamed accounts
Recently created, renamed or foreign-resolved accounts may briefly be represented by an old cache entry. Check that the authoritative UserAccount service returns current data. Recreating database accounts to 'fix a cache' is a mistake.
Grid region information cache
RegionInfoCache stores lookup information by UUID, name and location. Typical temporary entries expire after about 120 seconds in reviewed code. A changed region or address may remain briefly visible to some processes without GridStore itself being wrong.
Simulator inventory cache
InventoryCache temporarily holds root folders, folder types and some inventory data with about one-minute expiration. This memory cache is distinct from InventoryStore and from the inventory cache on a Firestorm client.
Are console commands available?
The reviewed components expose invalidation methods for application code, but a C# Clear or Invalidate method does not automatically register a console command. No universal account cache clear or inventory cache clear command is established here. Check the actual running module console rather than inventing commands.
Connection with Hypergrid friendships
An account cache may temporarily display stale information but it does not change friendship relationships in each grid's FriendsStore. Migrating foreign friends remains a cross-grid trust problem, not simply an account cache to clear.
Managing this cache: practical steps
Managing account and region caches
Source defines TTLs and internal invalidation, not a universal console command. For a renamed user or misidentified foreign visitor: verify the authoritative UserAccount service, record UUID and time, check logs, then allow component TTL. For a moved region: check GridStore registration before blaming RegionInfoCache. Do not edit SQL tables to fix temporarily cached values.
Restart: last resort, not a cache command
Restarting a simulator resets its local in-memory caches but also interrupts regions and residents and does not necessarily clear disk caches. Restarting ROBUST can impact the whole grid; do not describe it as a UserAccountCache clear command. Selective memory invalidation needs explicit support from the module.
User cache: commands verified in 0.9.3.1 source
Verified command: reset user cache
In the simulator console, when UserManagementModule is active, reset user cache clears m_userCacheByID, the module's user/identity mapping cache. The show name <uuid> and show names commands inspect currently known mappings. This does not clear every other UserAccountCache in the simulator or ROBUST services.
Practical procedure
If a UUID shows an outdated name or foreign identity: run show name <uuid>, verify authoritative home-service data, then reset user cache and check again. Entries may be rebuilt on later lookups; this does not change SQL accounts, home UUIs or FriendsStore relationships.
Simulator console, UserManagement module active. reset user cache does not clear all other account caches.
show name <uuid> show names reset user cache
Source: UserManagementModule.cs, lines 1300-1327 — https://github.com/Vlad-BloodMoon/opensim/blob/master/OpenSim/Region/CoreModules/Framework/UserManagement/UserManagementModule.cs