statistics data

Deadline
1

So i have a dilemma,

our IT team had named our render nodes with inconsistent capitalization.
This made me crazy looking at the list of machine names all the time. I had them standardize the naming.

this is with the problem appeared.
Now when i copy our render node stats i have 2 copies of much of the data.
one data set before the name was changed and one after.

for example, i have a render node named rn001 and RN001.
they are the same machine, but the stats before 6/2/2015 are contained in rn001 and the stats after are contained in RN001.

ideally i could concatenate the data so i can preserve my YTD stats, if there is no way to do that an consolidate the list the next best thing would be to permanently delete old and deprecated render nodes, which i have inquired about previously but have yet to figure out how to do in a way that removes all the statistics data as well.

thanks for your help

2

Hello Troy,

I have asked one of our devs to look to see if there is a way to maybe alter the stats data so it more closely matches between the changed names, but it might be hard to do. Hopefully we can figure something out soon.

3

Hey Troy,

This is definitely a bug on the stats-side, since we generally don’t consider casing when identifying Slaves (so “rn001” and “RN001” should always refer to the same Slave). I’ve logged this internally to be fixed in the future (hopefully 7.2).

Unfortunately, I don’t think there’s much we can do in the short term; we don’t have functionality in place to rename specific stats entries, so until we can get a fix in, they will show up as separate entities.

The only way stats entries get deleted is through our Stats Cleanup step in the Housecleaning, which deletes entries older than a configurable threshold. You certainly could temporarily set the cutoff in such a way that would delete all the Slave stats prior to 2015/6/2, but keep in mind this will delete the stats for all the slaves prior to that point in time, not just the ‘obsolete’ ones.

4

no worries, i am excited that there is a potential fix at some point in the future.
we can work with that!

5

Hey Troy,

Just an update that we’re currently working on a 7.1.2 patch release that should be publicly available soon (the first release candidate was released on the beta forums this morning). This case sensitivity issue should be fixed in this patch release.

Cheers,
Ryan

6

oh great!
you guys are fantastic!