Hi Ilya, I wonder why do you try to run several Ignite instances in the same JVM in the first place? Is there any value to do so, apart for testing?
Anyway, with current proposal you could try to configure message routing based on a thread name: every thread in Ignite 3 should have name which starts with "%<nodeName>%” prefix. -- Regards, Konstantin Orlov > On 8 Jun 2023, at 18:14, Ilya Korol <llivezk...@gmail.com> wrote: > > Hi Konstantin. Thanks for you work. > > Despite you proposal is more about public API of logging Ignite facility, I > believe that this thread is the best place to highlight some topic about > internal details of IgniteLogger based on my experience with Ignite 2 > > I already tried to initiate a discussion at the end of previous year, > unfortunately there were not so many community members eager to discuss it. > > Here is the link > https://lists.apache.org/thread/xcllwbz12cpb5437hrt5n1xfdfp0wqct > > The feature, that from my perspective, is missing in current implementation > (AI2) and that should be kept in mind when it comes to implement logging IEP, > is ability to separate messages produced by different Ignite instances > running in same JVM, > so at appenders level (no matter of the actual logging implementation) there > is no way to properly route log messages to separate locations based on the > message source node. > > Maybe community will find this feature useful. > > > > On 08.06.2023 17:45, Konstantin Orlov wrote: >> Hi, >> >> Please review "IEP-107 Logging in Ignite 3” proposal >> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-107+Logging+in+Ignite+3 >> >> >> -- >> Regards, >> Konstantin Orlov >> >> >> >> >>
