Additional data purging needed; e.g. RHQ_CONFIG_UPDATE
Jay Shaughnessy
jshaughn at redhat.com
Tue Sep 30 17:26:59 UTC 2014
It is definitely the case that we don't successfully eliminate all
Config props. There are certainly orphans. It has to do with our
recursive config structure, which is an albatross we haven't been able
to shed.
On 9/29/2014 5:11 PM, Thomas Segismont wrote:
> Le 29/09/2014 22:22, Elias Ross a écrit :
>> I have 800,000+ rows in RHQ_CONFIG and RHQ_CONFIG_PROPERTY has
>> 87,000,000+ rows, and this is just my lab system. My suspicion is data
>> is not being deleted here there either.
>>
>> As RHQ_RESOURCE is 150K rows, and none of the other tables come close
>> to that many rows, there's quite a lot of orphaned configurations I
>> suspect.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1147669
>
> I believe this is a consequence of RHQ_CONFIG_UPDATE not being purged.
> Each config update is associated with a configuration.
>
> Resource configuration updates may come from:
> * users: UI, CLI
> * agent: config check job (if the live configuration is different than
> the original)
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
More information about the rhq-devel
mailing list