Hello! Actually, this screen shot does actually contain relevant error message: rebalance thread pool size should be < system thread pool size.
It is enforced and node will not start (even visor's Daemon node). Please fix your cfg to enforce this constraint: https://apacheignite.readme.io/docs/thread-pools Regards, -- Ilya Kasnacheev пт, 6 мар. 2020 г. в 17:37, Николай Кулагин <zzzadruga....@gmail.com>: > Joshi, > > A ticket has been started for this issue. You can track his status here > [1]. > > [1] https://issues.apache.org/jira/browse/IGNITE-12757 > > чт, 5 мар. 2020 г. в 14:48, Kamlesh Joshi <kamlesh.jo...@ril.com>: > >> Hi Team, >> >> >> >> I have updated Ignite cluster to latest version 2.8.0 and update was >> successful. However, I am unable connect to IgniteVisor console. Below is >> the command I used (the same command was used for earlier versions and it >> worked fine). Not sure am I missing something or is there any defect around >> it? Ignite 2.8.0 docs are not available on the site ! >> >> >> >> *$IGNITE_HOME/bin/ignitevisorcmd.sh -cfg="/app/Ignite/visorconfig.xml"* >> >> >> >> >> >> >> >> *Thanks and Regards,* >> >> *Kamlesh Joshi* >> >> >> >> >> "*Confidentiality Warning*: This message and any attachments are >> intended only for the use of the intended recipient(s), are confidential >> and may be privileged. If you are not the intended recipient, you are >> hereby notified that any review, re-transmission, conversion to hard copy, >> copying, circulation or other use of this message and any attachments is >> strictly prohibited. If you are not the intended recipient, please notify >> the sender immediately by return email and delete this message and any >> attachments from your system. >> >> *Virus Warning:* Although the company has taken reasonable precautions >> to ensure no viruses are present in this email. The company cannot accept >> responsibility for any loss or damage arising from the use of this email or >> attachment." >> >