Himanshu, per comment 4, it sounds like this can be closed. Can you confirm and please do so.
A possible fix has been proposed in this related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1535720 That is targeted for the MiqServer, and high confidence that it will fix the leak there. Updates will probably happen there more regularly until we determine if there is a different leak in the MetricsProcessor Worker, and there is a high probability this was a leak across all workers.
The fix above has been backported here: https://bugzilla.redhat.com/show_bug.cgi?id=1536658 We are going to do some testing ourselves to see if this is fixing the issue with the MetricsProcessor as well, and will update with those results.
Update: We are relatively sure that this leak will be resolved with the patch provided in https://bugzilla.redhat.com/show_bug.cgi?id=1535720 (or the respective backported version), so this might already be fixed. That said, we are doing some final long term comparisons with our test environments to confirm that the systems that had the patch applied and displayed no leak, will start leaking once the patch is removed. We are confident this patch fixes the leak with MiqServer, but want to be confident in saying this is the same with the other workers as well, and that there isn't possibly another leak at play here. Next update will be roughly in a week's time.
After testing on a pair of appliances for about a week, we are fairly confident that this has a substantial impact to the memory footprint of all the workers, including the MetricsProcessorWorker, as mentioned here. Please retest with the changes in place, and if the issue persists, feel free to kick the ticket back so we can look into it further.
*** This bug has been marked as a duplicate of bug 1479339 ***