Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Roxie ping log events should be reevaluated

Description

“PING reply, garbled result activityId=ROXIE_PING…” was identified as a high frequency log entry on a low traffic environment. Roxie should evaluate the cost-effectiveness of this and other similar/related log entries and either conditionally report based on conditions, condense the log entry size, suppress, or re-categorize

 

fyi

Conclusion

None

Attachments

3

Activity

Rodrigo Pastrana 
March 7, 2025 at 6:14 PM

Log cost distribution on idle system seems to have shifted away from roxie toward ESP:

Gavin Halliday 
March 6, 2025 at 10:10 AM

Thanks Rodrigo. See linked issue, where Richard has a PR to remove it because it provides no benefit.

Separately I am curious why it is 9.10.0 rather than the current point release

Rodrigo Pastrana 
March 5, 2025 at 8:03 PM

Ok, community_9.10.0-1 is now deployed. After an hour of sitting idle, this is the billed log size distribution

I emphasize this is under idle load because the cost might be negligible under normal load.

Rodrigo Pastrana 
March 5, 2025 at 2:58 PM

It’s a private Terraform based deployment, I’ll update to a recent HPCC version and update the billable log reports

Richard Chapman 
March 5, 2025 at 11:16 AM

Do we know what build this was in?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Created February 28, 2025 at 5:07 PM
Updated April 29, 2025 at 9:02 AM
Resolved March 21, 2025 at 3:52 PM