Hello! I was working on https://issues.apache.org/jira/browse/IGNITE-8935 to avoid default toString() implementations in classes reachable from IgniteConfiguration, which we print on start-up.
I have discovered that by default we avoid printing arrays and collections. We only print those when marked with @GridToStringInclude. This to avoid serializing endless auto-generated lists I suppose. And I was thinking of going through IgniteConfiguration and friends, marking some user-specified collections @GridToStringInclude so that they show up in toString(). The most notorious one will be IgniteConfiguration.cacheConfigurations. What's your take on this one? On one hand, cache configurations are of tremendous significance to anybody debugging Ignite, or troubleshooting user cases on e.g. userlist. On other hand, some people have configurations with thousands of caches and might be not completely happy with several megabytes of log within a single line. Should I mark caches configurations (and also service configurations, and others) with @GridToStringInclude or not? I think that the only place where it gets printed is once on the start when IGNITE_QUIET is false. I will defer doing that until aforementioned ticket is merged, so please take a look at it if you're interested. Regards, -- Ilya Kasnacheev
