3.4 KiB
Satellite-table-related-feature-blocked-due-to-fuse-exceeded_686074726
Problem
The SMAX license report cannot be generated, as reported by Decathlon: https://us2-smax.saas.microfocus.com/saw/Request/318867/general?TENANTID=488503157
The license report no longer track any more usage data.
This was reported on Decathon 1st, other large tenants will have same issue but not report yet.
When login SMAX tenant Agent UI and route to "People" to download the license usage report. You will find the license usage data is not up-to-date.
Environment
EU8 and possible on any big tenants
Cause
There was an old tenant level fuse satelliteMaxIdAllocations control the capacity (max ID) of all satellite tables. The default value of satelliteMaxIdAllocations is 10M. License report is based on lms_metric_ which is a satellite table, and costs about 15000/year. When NH go live every email was tracked in satellite table and the 10M fuse is quickly consumed. When the system running out of IDs, there is no new record can be generated into any satellite table and finally causing the license issues. The large tenant will quickly having this issue as there are too many emails. While usually dev tenant are safe.
The following features will be impacted, complete failure:
- Smax license usage calculation
- The new notification history
- Expense line in Finance
Quick troubleshooting can based on error msg from below log file:
com.hp.maas.platform.exception.service.ServiceException: Cannot create new satellite entities once exceeded allocation threshold
at com.hp.maas.platform.services.satellitemanagement.api.SatelliteExceptionFactory.reachedFuse(SatelliteExceptionFactory.java:31)
at com.hp.maas.platform.services.satellitemanagement.dao.SatelliteDalImpl.getIdGenRange(SatelliteDalImpl.java:436)
at com.hp.maas.platform.services.satellitemanagement.dao.SatelliteDalImpl.buildStringFromRecords(SatelliteDalImpl.java:495)
at com.hp.maas.platform.services.satellitemanagement.dao.SatelliteDalImpl.createEntities(SatelliteDalImpl.java:142)
at com.hp.maas.platform.services.satellitemanagement.impl.SatelliteManagementServiceImpl$1.run(SatelliteManagementServiceImpl.java:66)
at com.hp.maas.platform.services.satellitemanagement.impl.SatelliteManagementServiceImpl$1.run(SatelliteManagementServiceImpl.java:52)
at com.hp.maas.platform.services.satellitemanagement.impl.SatelliteDbRunner.runWithSatelliteDBPool(SatelliteDbRunner.java:19)
at com.hp.maas.platform.services.satellitemanagement.impl.SatelliteManagementServiceImpl.processBulkUpdate(SatelliteManagementServiceImpl.java:52)
Solution
Workaround:
Changing the fuse value to 500M or 1B for the big production tenants on all farms to avoid escalations on the 3 features. Detail value depends on how big the tenant using Satellite table, and when the final solution would applied.
Tenant setting name: satelliteMaxIdAllocations
Payload of 1B (PUT): {"satelliteMaxIdAllocations": "'1000000000'"}
Risk Impact Analysis
1. No binary change
2. No downtime
3. No impact to upgrade
Final solution:
Remove the fuse which is not meaningful/useful.
Risk Impact Analysis
1. Only binary change to ignore the fuse; can be fix in a patch and not necessary through upgrade
2. No downtime
3. No impact to upgrade