Re: Configuration suggestion of Java version at Ignite startup

2019-01-10 Thread Dmitriy Pavlov
Yes, and we can run tests on J9,10,11 but it is controlled by JavaHome build parameter during runAll start. I suggest first to change this parameter as default to newer Java in 2-4 weeks before updating our recommendations. чт, 10 янв. 2019 г. в 15:10, Vyacheslav Daradur : > AFAIK some test-agent

Re: Configuration suggestion of Java version at Ignite startup

2019-01-10 Thread Vyacheslav Daradur
AFAIK some test-agents are configured to use JDK 9/10/11, isn't it? On Thu, Jan 10, 2019 at 2:59 PM Dmitriy Pavlov wrote: > > I feel the first step there should be to switch our tests running on TC to > java > 8. > > After some time having newer java as default we can change suggestions for > use

Re: Configuration suggestion of Java version at Ignite startup

2019-01-10 Thread Dmitriy Pavlov
I feel the first step there should be to switch our tests running on TC to java > 8. After some time having newer java as default we can change suggestions for users. чт, 10 янв. 2019 г. в 14:08, Vyacheslav Daradur : > Igniters, > > As you know, Ignite logs configuration tuning suggestions at no

Configuration suggestion of Java version at Ignite startup

2019-01-10 Thread Vyacheslav Daradur
Igniters, As you know, Ignite logs configuration tuning suggestions at node startup to improve performance. At the moment, it recommends using Java 8 even if later releases are used. Public updates will not be available for business users since January of 2019 if I'm not mistaken. It may be use