Merging of collector cache files from two different collectors
I am upgrading one of our dynaTrace instances from 5.5 to 5.6 tomorrow. During the migration, I am migrating traffic on two collectors down to a single collector. Is it possible to take the resulting collector cache file (from dtmigration.jar) from each of the two collectors and import both of files (one at a time) to the new single collector?
Use Case: on dynaTrace 5.5, i have two collectors in same site (Dallas A collector & Dallas B collector). Due to very light traffic, I don't need both collectors and will have plenty of headroom on a single collector, Dallas C collector. Can I take resulting dtmigration.jar collector cache file from both Dallas A and Dallas B and import them one at a time on Dallas C?
Thanks,
Rob Herring
Hi Rob,
nope, you cannot consolidate class caches with such a procedure. Guess the info in the class cache files would need to be consolidated, BUT...
- naturally the single Collector will draw the class info from the new Agents, which, also naturally will take some time. (depending...)
- in the next dynaTrace version the Collectors will share meta-data which will make your wish come true and then some...
More info on that in a couple of weeks.
Cheers
G.
Guenter,
If using the dtMigration.jar is not the way to do it, is there any other way to do this?
Hi Ali,
you would need some utility to consolidate the content of the classCache files from the Collectors into one, but that wouldn´t pay, because the then single Collector will discover the classes from the new Agents automatically and cache it too.
OTOH as hinted above and without spilling all the beans <g>: If you want to connect Agents to a different Collector on the fly it needs to know about the classes instantly.
The dTMigration tool only offers a relatively convenient way to migrate settings and certain data (here: class caches) 1 : 1, i.e. it copies the classCache file, but doesn´t look into the file.
Hope this helps
G.
Hi there
I think the problem is not the collectors,but the agents. You have to change their config to the single collector instance and restart the agent/application anyway. So after they restarted you can get rid of the collector at any time.
Anton
Anton,
This customer is using a load balancer in front of the collectors. Given this, typically they don't have to restart the agents when they upgrade the collectors as the LB would automatically point the agents to the new (upgraded) collectors.
