Hello! The configuration is usually already present in some other file (in XML or Java form). People who report problems or userlist often fail to provide such file, and they will also definitely forget to provide that other separate file with printed configuation. Log file is our best shot since it's what usually gets reported.
Regards, -- Ilya Kasnacheev 2018-07-07 0:23 GMT+03:00 Dmitriy Setrakyan <[email protected]>: > Can we print out the configuration to a separate file? Moreover, I think we > should also print out the configuration differences between nodes, whenever > new nodes join topology. > > D. > > On Fri, Jul 6, 2018 at 6:51 AM, Ilya Kasnacheev <[email protected] > > > wrote: > > > 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 > > >
