Hi,
I failed to connect ignitevisorcmd.sh to my grid. The result of open is: +-------------------------------------+ | Status | Disconnected | | Ignite instance name | <n/a> | | Config path | <n/a> | | Uptime | <n/a> | +-------------------------------------+ visor> even if I choose the right conf, and I repeat open many times. The grid is running, and I can perform queries normally. There is no exception, nor indication in the logs. I used –v in both ignite.sh and ignitevisorcmd.sh. I appreciate your help. Best Regards, Ali Hassan Senior Scala SE Senior BigData SE |
Hello, Ali.
Looks like this is known issue and it was fixed by [1] Nikolay, can you confirm it? [1] https://github.com/apache/ignite/commit/d0bae90bce33dbed8b9f3cd52663ce5efa545d97 > 28 марта 2020 г., в 12:30, ali hassan <[hidden email]> написал(а): > > Hi, > I failed to connect ignitevisorcmd.sh to my grid. The result of open is: > > +-------------------------------------+ > > | Status | Disconnected | > > | Ignite instance name | <n/a> | > > | Config path | <n/a> | > > | Uptime | <n/a> | > > +-------------------------------------+ > > visor> > > > > even if I choose the right conf, and I repeat open many times. > > > > The grid is running, and I can perform queries normally. > > There is no exception, nor indication in the logs. > > I used –v in both ignite.sh and ignitevisorcmd.sh. > > > > I appreciate your help. > > > > Best Regards, > > Ali Hassan > > Senior Scala SE > > Senior BigData SE |
Ali, yes, this problem has been fixed.
пн, 30 мар. 2020 г. в 11:44, Nikolay Izhikov <[hidden email]>: > Hello, Ali. > > Looks like this is known issue and it was fixed by [1] > > Nikolay, can you confirm it? > > [1] > https://github.com/apache/ignite/commit/d0bae90bce33dbed8b9f3cd52663ce5efa545d97 > > > 28 марта 2020 г., в 12:30, ali hassan <[hidden email]> написал(а): > > > > Hi, > > I failed to connect ignitevisorcmd.sh to my grid. The result of open is: > > > > +-------------------------------------+ > > > > | Status | Disconnected | > > > > | Ignite instance name | <n/a> | > > > > | Config path | <n/a> | > > > > | Uptime | <n/a> | > > > > +-------------------------------------+ > > > > visor> > > > > > > > > even if I choose the right conf, and I repeat open many times. > > > > > > > > The grid is running, and I can perform queries normally. > > > > There is no exception, nor indication in the logs. > > > > I used –v in both ignite.sh and ignitevisorcmd.sh. > > > > > > > > I appreciate your help. > > > > > > > > Best Regards, > > > > Ali Hassan > > > > Senior Scala SE > > > > Senior BigData SE > > |
Hello, Ali.
This fix would be available in 2.8.1. > 30 марта 2020 г., в 21:09, Nikolai Kulagin <[hidden email]> написал(а): > > Ali, yes, this problem has been fixed. > > пн, 30 мар. 2020 г. в 11:44, Nikolay Izhikov <[hidden email]>: > >> Hello, Ali. >> >> Looks like this is known issue and it was fixed by [1] >> >> Nikolay, can you confirm it? >> >> [1] >> https://github.com/apache/ignite/commit/d0bae90bce33dbed8b9f3cd52663ce5efa545d97 >> >>> 28 марта 2020 г., в 12:30, ali hassan <[hidden email]> написал(а): >>> >>> Hi, >>> I failed to connect ignitevisorcmd.sh to my grid. The result of open is: >>> >>> +-------------------------------------+ >>> >>> | Status | Disconnected | >>> >>> | Ignite instance name | <n/a> | >>> >>> | Config path | <n/a> | >>> >>> | Uptime | <n/a> | >>> >>> +-------------------------------------+ >>> >>> visor> >>> >>> >>> >>> even if I choose the right conf, and I repeat open many times. >>> >>> >>> >>> The grid is running, and I can perform queries normally. >>> >>> There is no exception, nor indication in the logs. >>> >>> I used –v in both ignite.sh and ignitevisorcmd.sh. >>> >>> >>> >>> I appreciate your help. >>> >>> >>> >>> Best Regards, >>> >>> Ali Hassan >>> >>> Senior Scala SE >>> >>> Senior BigData SE >> >> |
Free forum by Nabble | Edit this page |