You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Charlin S <ch...@hotelhub.com> on 2024/04/10 12:01:01 UTC
ignitevisorcmd tool - alternate option
Hi All,
Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and
found that
ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is the
alternative way for checking grids statistics and cache details without
ignitevisorcmd tool.
Thanks & Regards,
Charlin
Re: ignitevisorcmd tool - alternate option
Posted by Николай Ижиков <ni...@apache.org>.
Hello.
You can configure sql view metric exporter to export all metrics in form of SQL view and query view via control.sh
https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#sql-view
> 24 апр. 2024 г., в 09:43, Charlin S <Ch...@hotelhub.com> написал(а):
>
> Hi,
> Thank you all.
> metric works for me to find cache count. could you please let me know if any option for getting all caches with count in single window or tabular format
>
> Thanks & Regards,
> Charlin
>
>
> On Mon, 22 Apr 2024 at 14:59, Stephen Darlington <sd...@apache.org> wrote:
> bin/control.sh --metric cache.SQL_PUBLIC_IGNITE
>
> On Mon, 22 Apr 2024 at 10:06, Charlin S <ch...@hotelhub.com> wrote:
> Hi All,
> ./control.sh —system-view CACHES also not having cache records count.
> How to get cache count like visorcommand
>
> Thanks & Regards,
> Charlin
>
>
> On Mon, 15 Apr 2024 at 22:21, Николай Ижиков <ni...@apache.org> wrote:
> > Thanks for your email, able to get a list of caches like list . but the result format is not easy to understand.<image.png
>
> System view command outputs table rows with the single line.
> You can adjust formatting with the following:
>
> ./control.sh —system-view CACHES > output.txt
>
> Then view output.txt with the any editor, disable wrap lines option.
>
>
>
> > 15 апр. 2024 г., в 19:25, Stephen Darlington <sd...@apache.org> написал(а):
> >
> > What tool are you using?
> >
> > If you're using sqlline, you could do "!set output vertical" or only select the columns you're interested in.
> >
> > On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com> wrote:
> > Hello Nizhikov,
> > Thanks for your email, able to get a list of caches like list . but the result format is not easy to understand.<image.png>
> >
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> > On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org> wrote:
> > Hello, Charlin
> >
> > Looks like system view CACHES can help you.
> > https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
> >
> >
> > > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com> написал(а):
> > >
> > > Hi All,
> > > Thank you for your email.
> > > Still I am missing cache -scan result details like below (in visorcmd).
> > > <image.png>
> > > Is it possible to get results using --cache scan list . ?
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> > >
> > >
> > > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org> wrote:
> > > Hello, Charlin
> > >
> > > Please, take a look at system views:
> > >
> > > NODES, BASELINE_NODES.
> > >
> > > You can query them by control.sh -
> > >
> > > https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> > >
> > > control.sh --system-view nodes
> > >
> > >
> > > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com> написал(а):
> > > >
> > > > Hi Pavel,
> > > > Thank you for your email. --baseline argument not showing client node list, actually 1 server and 1 client node should shown
> > > >
> > > > <image.png>
> > > >
> > > > Thanks & Regards,
> > > > Charlin
> > > >
> > > >
> > > >
> > > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org> wrote:
> > > > control.sh is the replacement:
> > > > https://ignite.apache.org/docs/latest/tools/control-script
> > > >
> > > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com> wrote:
> > > > Hi Charlin,
> > > >
> > > > I am working as a Principal Architect at GridGain.
> > > > Let me know if you would like to have a call to discuss your project and needs, so I can figure out how to help you.
> > > >
> > > > Regards,
> > > > Rajiv Shah
> > > >
> > > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
> > > > Hi All,
> > > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and found that
> > > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is the alternative way for checking grids statistics and cache details without ignitevisorcmd tool.
> > > >
> > > > Thanks & Regards,
> > > > Charlin
> > > >
> > >
> >
>
Re: ignitevisorcmd tool - alternate option
Posted by Charlin S <ch...@hotelhub.com>.
Hi,
Thank you all.
metric works for me to find cache count. could you please let me know if
any option for getting all caches with count in single window or
tabular format
Thanks & Regards,
Charlin
On Mon, 22 Apr 2024 at 14:59, Stephen Darlington <sd...@apache.org>
wrote:
> bin/control.sh --metric cache.SQL_PUBLIC_IGNITE
>
> On Mon, 22 Apr 2024 at 10:06, Charlin S <ch...@hotelhub.com> wrote:
>
>> Hi All,
>> ./control.sh —system-view CACHES also not having cache records count.
>> How to get cache count like visorcommand
>>
>> Thanks & Regards,
>> Charlin
>>
>>
>> On Mon, 15 Apr 2024 at 22:21, Николай Ижиков <ni...@apache.org> wrote:
>>
>>> > Thanks for your email, able to get a list of caches like list . but
>>> the result format is not easy to understand.<image.png
>>>
>>> System view command outputs table rows with the single line.
>>> You can adjust formatting with the following:
>>>
>>> ./control.sh —system-view CACHES > output.txt
>>>
>>> Then view output.txt with the any editor, disable wrap lines option.
>>>
>>>
>>>
>>> > 15 апр. 2024 г., в 19:25, Stephen Darlington <sd...@apache.org>
>>> написал(а):
>>> >
>>> > What tool are you using?
>>> >
>>> > If you're using sqlline, you could do "!set output vertical" or only
>>> select the columns you're interested in.
>>> >
>>> > On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com>
>>> wrote:
>>> > Hello Nizhikov,
>>> > Thanks for your email, able to get a list of caches like list . but
>>> the result format is not easy to understand.<image.png>
>>> >
>>> >
>>> > Thanks & Regards,
>>> > Charlin
>>> >
>>> >
>>> > On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org>
>>> wrote:
>>> > Hello, Charlin
>>> >
>>> > Looks like system view CACHES can help you.
>>> >
>>> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
>>> >
>>> >
>>> > > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com>
>>> написал(а):
>>> > >
>>> > > Hi All,
>>> > > Thank you for your email.
>>> > > Still I am missing cache -scan result details like below (in
>>> visorcmd).
>>> > > <image.png>
>>> > > Is it possible to get results using --cache scan list . ?
>>> > >
>>> > > Thanks & Regards,
>>> > > Charlin
>>> > >
>>> > >
>>> > >
>>> > > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org>
>>> wrote:
>>> > > Hello, Charlin
>>> > >
>>> > > Please, take a look at system views:
>>> > >
>>> > > NODES, BASELINE_NODES.
>>> > >
>>> > > You can query them by control.sh -
>>> > >
>>> > >
>>> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
>>> > >
>>> > > control.sh --system-view nodes
>>> > >
>>> > >
>>> > > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com>
>>> написал(а):
>>> > > >
>>> > > > Hi Pavel,
>>> > > > Thank you for your email. --baseline argument not showing client
>>> node list, actually 1 server and 1 client node should shown
>>> > > >
>>> > > > <image.png>
>>> > > >
>>> > > > Thanks & Regards,
>>> > > > Charlin
>>> > > >
>>> > > >
>>> > > >
>>> > > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
>>> wrote:
>>> > > > control.sh is the replacement:
>>> > > > https://ignite.apache.org/docs/latest/tools/control-script
>>> > > >
>>> > > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <
>>> rajiv.shah@gridgain.com> wrote:
>>> > > > Hi Charlin,
>>> > > >
>>> > > > I am working as a Principal Architect at GridGain.
>>> > > > Let me know if you would like to have a call to discuss your
>>> project and needs, so I can figure out how to help you.
>>> > > >
>>> > > > Regards,
>>> > > > Rajiv Shah
>>> > > >
>>> > > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
>>> wrote:
>>> > > > Hi All,
>>> > > > Currently I am using Ignite 2.10 and planning to upgrade Ignite
>>> 2.16 and found that
>>> > > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards.
>>> What is the alternative way for checking grids statistics and cache details
>>> without ignitevisorcmd tool.
>>> > > >
>>> > > > Thanks & Regards,
>>> > > > Charlin
>>> > > >
>>> > >
>>> >
>>>
>>>
Re: ignitevisorcmd tool - alternate option
Posted by Stephen Darlington <sd...@apache.org>.
bin/control.sh --metric cache.SQL_PUBLIC_IGNITE
On Mon, 22 Apr 2024 at 10:06, Charlin S <ch...@hotelhub.com> wrote:
> Hi All,
> ./control.sh —system-view CACHES also not having cache records count.
> How to get cache count like visorcommand
>
> Thanks & Regards,
> Charlin
>
>
> On Mon, 15 Apr 2024 at 22:21, Николай Ижиков <ni...@apache.org> wrote:
>
>> > Thanks for your email, able to get a list of caches like list . but the
>> result format is not easy to understand.<image.png
>>
>> System view command outputs table rows with the single line.
>> You can adjust formatting with the following:
>>
>> ./control.sh —system-view CACHES > output.txt
>>
>> Then view output.txt with the any editor, disable wrap lines option.
>>
>>
>>
>> > 15 апр. 2024 г., в 19:25, Stephen Darlington <sd...@apache.org>
>> написал(а):
>> >
>> > What tool are you using?
>> >
>> > If you're using sqlline, you could do "!set output vertical" or only
>> select the columns you're interested in.
>> >
>> > On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com> wrote:
>> > Hello Nizhikov,
>> > Thanks for your email, able to get a list of caches like list . but the
>> result format is not easy to understand.<image.png>
>> >
>> >
>> > Thanks & Regards,
>> > Charlin
>> >
>> >
>> > On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org>
>> wrote:
>> > Hello, Charlin
>> >
>> > Looks like system view CACHES can help you.
>> >
>> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
>> >
>> >
>> > > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com>
>> написал(а):
>> > >
>> > > Hi All,
>> > > Thank you for your email.
>> > > Still I am missing cache -scan result details like below (in
>> visorcmd).
>> > > <image.png>
>> > > Is it possible to get results using --cache scan list . ?
>> > >
>> > > Thanks & Regards,
>> > > Charlin
>> > >
>> > >
>> > >
>> > > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org>
>> wrote:
>> > > Hello, Charlin
>> > >
>> > > Please, take a look at system views:
>> > >
>> > > NODES, BASELINE_NODES.
>> > >
>> > > You can query them by control.sh -
>> > >
>> > >
>> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
>> > >
>> > > control.sh --system-view nodes
>> > >
>> > >
>> > > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com>
>> написал(а):
>> > > >
>> > > > Hi Pavel,
>> > > > Thank you for your email. --baseline argument not showing client
>> node list, actually 1 server and 1 client node should shown
>> > > >
>> > > > <image.png>
>> > > >
>> > > > Thanks & Regards,
>> > > > Charlin
>> > > >
>> > > >
>> > > >
>> > > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
>> wrote:
>> > > > control.sh is the replacement:
>> > > > https://ignite.apache.org/docs/latest/tools/control-script
>> > > >
>> > > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
>> wrote:
>> > > > Hi Charlin,
>> > > >
>> > > > I am working as a Principal Architect at GridGain.
>> > > > Let me know if you would like to have a call to discuss your
>> project and needs, so I can figure out how to help you.
>> > > >
>> > > > Regards,
>> > > > Rajiv Shah
>> > > >
>> > > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
>> wrote:
>> > > > Hi All,
>> > > > Currently I am using Ignite 2.10 and planning to upgrade Ignite
>> 2.16 and found that
>> > > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards.
>> What is the alternative way for checking grids statistics and cache details
>> without ignitevisorcmd tool.
>> > > >
>> > > > Thanks & Regards,
>> > > > Charlin
>> > > >
>> > >
>> >
>>
>>
Re: ignitevisorcmd tool - alternate option
Posted by Charlin S <ch...@hotelhub.com>.
Hi All,
./control.sh —system-view CACHES also not having cache records count.
How to get cache count like visorcommand
Thanks & Regards,
Charlin
On Mon, 15 Apr 2024 at 22:21, Николай Ижиков <ni...@apache.org> wrote:
> > Thanks for your email, able to get a list of caches like list . but the
> result format is not easy to understand.<image.png
>
> System view command outputs table rows with the single line.
> You can adjust formatting with the following:
>
> ./control.sh —system-view CACHES > output.txt
>
> Then view output.txt with the any editor, disable wrap lines option.
>
>
>
> > 15 апр. 2024 г., в 19:25, Stephen Darlington <sd...@apache.org>
> написал(а):
> >
> > What tool are you using?
> >
> > If you're using sqlline, you could do "!set output vertical" or only
> select the columns you're interested in.
> >
> > On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com> wrote:
> > Hello Nizhikov,
> > Thanks for your email, able to get a list of caches like list . but the
> result format is not easy to understand.<image.png>
> >
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> > On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org>
> wrote:
> > Hello, Charlin
> >
> > Looks like system view CACHES can help you.
> >
> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
> >
> >
> > > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com>
> написал(а):
> > >
> > > Hi All,
> > > Thank you for your email.
> > > Still I am missing cache -scan result details like below (in
> visorcmd).
> > > <image.png>
> > > Is it possible to get results using --cache scan list . ?
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> > >
> > >
> > > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org>
> wrote:
> > > Hello, Charlin
> > >
> > > Please, take a look at system views:
> > >
> > > NODES, BASELINE_NODES.
> > >
> > > You can query them by control.sh -
> > >
> > >
> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> > >
> > > control.sh --system-view nodes
> > >
> > >
> > > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com>
> написал(а):
> > > >
> > > > Hi Pavel,
> > > > Thank you for your email. --baseline argument not showing client
> node list, actually 1 server and 1 client node should shown
> > > >
> > > > <image.png>
> > > >
> > > > Thanks & Regards,
> > > > Charlin
> > > >
> > > >
> > > >
> > > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
> wrote:
> > > > control.sh is the replacement:
> > > > https://ignite.apache.org/docs/latest/tools/control-script
> > > >
> > > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
> wrote:
> > > > Hi Charlin,
> > > >
> > > > I am working as a Principal Architect at GridGain.
> > > > Let me know if you would like to have a call to discuss your project
> and needs, so I can figure out how to help you.
> > > >
> > > > Regards,
> > > > Rajiv Shah
> > > >
> > > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
> wrote:
> > > > Hi All,
> > > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16
> and found that
> > > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What
> is the alternative way for checking grids statistics and cache details
> without ignitevisorcmd tool.
> > > >
> > > > Thanks & Regards,
> > > > Charlin
> > > >
> > >
> >
>
>
Re: ignitevisorcmd tool - alternate option
Posted by Charlin S <ch...@hotelhub.com>.
Hi,
Thanks for your email,
/control.sh —system-view CACHES > output.txt works for now, I have not
started using sqlline.
Thanks & Regards,
Charlin
On Mon, 15 Apr 2024 at 22:21, Николай Ижиков <ni...@apache.org> wrote:
> > Thanks for your email, able to get a list of caches like list . but the
> result format is not easy to understand.<image.png
>
> System view command outputs table rows with the single line.
> You can adjust formatting with the following:
>
> ./control.sh —system-view CACHES > output.txt
>
> Then view output.txt with the any editor, disable wrap lines option.
>
>
>
> > 15 апр. 2024 г., в 19:25, Stephen Darlington <sd...@apache.org>
> написал(а):
> >
> > What tool are you using?
> >
> > If you're using sqlline, you could do "!set output vertical" or only
> select the columns you're interested in.
> >
> > On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com> wrote:
> > Hello Nizhikov,
> > Thanks for your email, able to get a list of caches like list . but the
> result format is not easy to understand.<image.png>
> >
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> > On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org>
> wrote:
> > Hello, Charlin
> >
> > Looks like system view CACHES can help you.
> >
> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
> >
> >
> > > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com>
> написал(а):
> > >
> > > Hi All,
> > > Thank you for your email.
> > > Still I am missing cache -scan result details like below (in
> visorcmd).
> > > <image.png>
> > > Is it possible to get results using --cache scan list . ?
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> > >
> > >
> > > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org>
> wrote:
> > > Hello, Charlin
> > >
> > > Please, take a look at system views:
> > >
> > > NODES, BASELINE_NODES.
> > >
> > > You can query them by control.sh -
> > >
> > >
> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> > >
> > > control.sh --system-view nodes
> > >
> > >
> > > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com>
> написал(а):
> > > >
> > > > Hi Pavel,
> > > > Thank you for your email. --baseline argument not showing client
> node list, actually 1 server and 1 client node should shown
> > > >
> > > > <image.png>
> > > >
> > > > Thanks & Regards,
> > > > Charlin
> > > >
> > > >
> > > >
> > > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
> wrote:
> > > > control.sh is the replacement:
> > > > https://ignite.apache.org/docs/latest/tools/control-script
> > > >
> > > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
> wrote:
> > > > Hi Charlin,
> > > >
> > > > I am working as a Principal Architect at GridGain.
> > > > Let me know if you would like to have a call to discuss your project
> and needs, so I can figure out how to help you.
> > > >
> > > > Regards,
> > > > Rajiv Shah
> > > >
> > > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
> wrote:
> > > > Hi All,
> > > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16
> and found that
> > > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What
> is the alternative way for checking grids statistics and cache details
> without ignitevisorcmd tool.
> > > >
> > > > Thanks & Regards,
> > > > Charlin
> > > >
> > >
> >
>
>
Re: ignitevisorcmd tool - alternate option
Posted by Николай Ижиков <ni...@apache.org>.
> Thanks for your email, able to get a list of caches like list . but the result format is not easy to understand.<image.png
System view command outputs table rows with the single line.
You can adjust formatting with the following:
./control.sh —system-view CACHES > output.txt
Then view output.txt with the any editor, disable wrap lines option.
> 15 апр. 2024 г., в 19:25, Stephen Darlington <sd...@apache.org> написал(а):
>
> What tool are you using?
>
> If you're using sqlline, you could do "!set output vertical" or only select the columns you're interested in.
>
> On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com> wrote:
> Hello Nizhikov,
> Thanks for your email, able to get a list of caches like list . but the result format is not easy to understand.<image.png>
>
>
> Thanks & Regards,
> Charlin
>
>
> On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org> wrote:
> Hello, Charlin
>
> Looks like system view CACHES can help you.
> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
>
>
> > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com> написал(а):
> >
> > Hi All,
> > Thank you for your email.
> > Still I am missing cache -scan result details like below (in visorcmd).
> > <image.png>
> > Is it possible to get results using --cache scan list . ?
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> >
> > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org> wrote:
> > Hello, Charlin
> >
> > Please, take a look at system views:
> >
> > NODES, BASELINE_NODES.
> >
> > You can query them by control.sh -
> >
> > https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> >
> > control.sh --system-view nodes
> >
> >
> > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com> написал(а):
> > >
> > > Hi Pavel,
> > > Thank you for your email. --baseline argument not showing client node list, actually 1 server and 1 client node should shown
> > >
> > > <image.png>
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> > >
> > >
> > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org> wrote:
> > > control.sh is the replacement:
> > > https://ignite.apache.org/docs/latest/tools/control-script
> > >
> > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com> wrote:
> > > Hi Charlin,
> > >
> > > I am working as a Principal Architect at GridGain.
> > > Let me know if you would like to have a call to discuss your project and needs, so I can figure out how to help you.
> > >
> > > Regards,
> > > Rajiv Shah
> > >
> > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
> > > Hi All,
> > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and found that
> > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is the alternative way for checking grids statistics and cache details without ignitevisorcmd tool.
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> >
>
Re: ignitevisorcmd tool - alternate option
Posted by Stephen Darlington <sd...@apache.org>.
What tool are you using?
If you're using sqlline, you could do "!set output vertical" or only select
the columns you're interested in.
On Mon, 15 Apr 2024 at 17:09, Charlin S <ch...@hotelhub.com> wrote:
> Hello Nizhikov,
> Thanks for your email, able to get a list of caches like list . but the
> result format is not easy to understand.
> [image: image.png]
>
> Thanks & Regards,
> Charlin
>
>
> On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org> wrote:
>
>> Hello, Charlin
>>
>> Looks like system view CACHES can help you.
>>
>> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
>>
>>
>> > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com>
>> написал(а):
>> >
>> > Hi All,
>> > Thank you for your email.
>> > Still I am missing cache -scan result details like below (in visorcmd).
>> > <image.png>
>> > Is it possible to get results using --cache scan list . ?
>> >
>> > Thanks & Regards,
>> > Charlin
>> >
>> >
>> >
>> > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org>
>> wrote:
>> > Hello, Charlin
>> >
>> > Please, take a look at system views:
>> >
>> > NODES, BASELINE_NODES.
>> >
>> > You can query them by control.sh -
>> >
>> >
>> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
>> >
>> > control.sh --system-view nodes
>> >
>> >
>> > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com>
>> написал(а):
>> > >
>> > > Hi Pavel,
>> > > Thank you for your email. --baseline argument not showing client node
>> list, actually 1 server and 1 client node should shown
>> > >
>> > > <image.png>
>> > >
>> > > Thanks & Regards,
>> > > Charlin
>> > >
>> > >
>> > >
>> > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
>> wrote:
>> > > control.sh is the replacement:
>> > > https://ignite.apache.org/docs/latest/tools/control-script
>> > >
>> > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
>> wrote:
>> > > Hi Charlin,
>> > >
>> > > I am working as a Principal Architect at GridGain.
>> > > Let me know if you would like to have a call to discuss your project
>> and needs, so I can figure out how to help you.
>> > >
>> > > Regards,
>> > > Rajiv Shah
>> > >
>> > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
>> wrote:
>> > > Hi All,
>> > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16
>> and found that
>> > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What
>> is the alternative way for checking grids statistics and cache details
>> without ignitevisorcmd tool.
>> > >
>> > > Thanks & Regards,
>> > > Charlin
>> > >
>> >
>>
>>
Re: ignitevisorcmd tool - alternate option
Posted by Charlin S <ch...@hotelhub.com>.
Hello Nizhikov,
Thanks for your email, able to get a list of caches like list . but the
result format is not easy to understand.
[image: image.png]
Thanks & Regards,
Charlin
On Mon, 15 Apr 2024 at 19:39, Николай Ижиков <ni...@apache.org> wrote:
> Hello, Charlin
>
> Looks like system view CACHES can help you.
>
> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
>
>
> > 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com> написал(а):
> >
> > Hi All,
> > Thank you for your email.
> > Still I am missing cache -scan result details like below (in visorcmd).
> > <image.png>
> > Is it possible to get results using --cache scan list . ?
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> >
> > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org>
> wrote:
> > Hello, Charlin
> >
> > Please, take a look at system views:
> >
> > NODES, BASELINE_NODES.
> >
> > You can query them by control.sh -
> >
> >
> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> >
> > control.sh --system-view nodes
> >
> >
> > > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com>
> написал(а):
> > >
> > > Hi Pavel,
> > > Thank you for your email. --baseline argument not showing client node
> list, actually 1 server and 1 client node should shown
> > >
> > > <image.png>
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> > >
> > >
> > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
> wrote:
> > > control.sh is the replacement:
> > > https://ignite.apache.org/docs/latest/tools/control-script
> > >
> > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
> wrote:
> > > Hi Charlin,
> > >
> > > I am working as a Principal Architect at GridGain.
> > > Let me know if you would like to have a call to discuss your project
> and needs, so I can figure out how to help you.
> > >
> > > Regards,
> > > Rajiv Shah
> > >
> > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
> wrote:
> > > Hi All,
> > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16
> and found that
> > > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What
> is the alternative way for checking grids statistics and cache details
> without ignitevisorcmd tool.
> > >
> > > Thanks & Regards,
> > > Charlin
> > >
> >
>
>
Re: ignitevisorcmd tool - alternate option
Posted by Николай Ижиков <ni...@apache.org>.
Hello, Charlin
Looks like system view CACHES can help you.
https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
> 15 апр. 2024 г., в 09:30, Charlin S <ch...@hotelhub.com> написал(а):
>
> Hi All,
> Thank you for your email.
> Still I am missing cache -scan result details like below (in visorcmd).
> <image.png>
> Is it possible to get results using --cache scan list . ?
>
> Thanks & Regards,
> Charlin
>
>
>
> On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org> wrote:
> Hello, Charlin
>
> Please, take a look at system views:
>
> NODES, BASELINE_NODES.
>
> You can query them by control.sh -
>
> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
>
> control.sh --system-view nodes
>
>
> > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com> написал(а):
> >
> > Hi Pavel,
> > Thank you for your email. --baseline argument not showing client node list, actually 1 server and 1 client node should shown
> >
> > <image.png>
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> >
> > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org> wrote:
> > control.sh is the replacement:
> > https://ignite.apache.org/docs/latest/tools/control-script
> >
> > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com> wrote:
> > Hi Charlin,
> >
> > I am working as a Principal Architect at GridGain.
> > Let me know if you would like to have a call to discuss your project and needs, so I can figure out how to help you.
> >
> > Regards,
> > Rajiv Shah
> >
> > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
> > Hi All,
> > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and found that
> > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is the alternative way for checking grids statistics and cache details without ignitevisorcmd tool.
> >
> > Thanks & Regards,
> > Charlin
> >
>
Re: ignitevisorcmd tool - alternate option
Posted by Charlin S <ch...@hotelhub.com>.
Hi All,
Thank you for your email.
Still I am missing cache -scan result details like below (in visorcmd).
[image: image.png]
* Is it possible to get results using ** --cache scan list . ** ?*
Thanks & Regards,
Charlin
On Fri, 12 Apr 2024 at 18:46, Николай Ижиков <ni...@apache.org> wrote:
> Hello, Charlin
>
> Please, take a look at system views:
>
> NODES, BASELINE_NODES.
>
> You can query them by control.sh -
>
>
> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
>
> control.sh --system-view nodes
>
>
> > 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com> написал(а):
> >
> > Hi Pavel,
> > Thank you for your email. --baseline argument not showing client node
> list, actually 1 server and 1 client node should shown
> >
> > <image.png>
> >
> > Thanks & Regards,
> > Charlin
> >
> >
> >
> > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org>
> wrote:
> > control.sh is the replacement:
> > https://ignite.apache.org/docs/latest/tools/control-script
> >
> > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
> wrote:
> > Hi Charlin,
> >
> > I am working as a Principal Architect at GridGain.
> > Let me know if you would like to have a call to discuss your project and
> needs, so I can figure out how to help you.
> >
> > Regards,
> > Rajiv Shah
> >
> > On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com>
> wrote:
> > Hi All,
> > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and
> found that
> > ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is
> the alternative way for checking grids statistics and cache details without
> ignitevisorcmd tool.
> >
> > Thanks & Regards,
> > Charlin
> >
>
>
Re: ignitevisorcmd tool - alternate option
Posted by Николай Ижиков <ni...@apache.org>.
Hello, Charlin
Please, take a look at system views:
NODES, BASELINE_NODES.
You can query them by control.sh -
https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
control.sh --system-view nodes
> 12 апр. 2024 г., в 15:38, Charlin S <ch...@hotelhub.com> написал(а):
>
> Hi Pavel,
> Thank you for your email. --baseline argument not showing client node list, actually 1 server and 1 client node should shown
>
> <image.png>
>
> Thanks & Regards,
> Charlin
>
>
>
> On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org> wrote:
> control.sh is the replacement:
> https://ignite.apache.org/docs/latest/tools/control-script
>
> On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com> wrote:
> Hi Charlin,
>
> I am working as a Principal Architect at GridGain.
> Let me know if you would like to have a call to discuss your project and needs, so I can figure out how to help you.
>
> Regards,
> Rajiv Shah
>
> On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
> Hi All,
> Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and found that
> ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is the alternative way for checking grids statistics and cache details without ignitevisorcmd tool.
>
> Thanks & Regards,
> Charlin
>
Re: ignitevisorcmd tool - alternate option
Posted by Charlin S <ch...@hotelhub.com>.
Hi Pavel,
Thank you for your email. --baseline argument not showing client node list,
actually 1 server and 1 client node should shown
[image: image.png]
Thanks & Regards,
Charlin
On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn <pt...@apache.org> wrote:
> control.sh is the replacement:
> https://ignite.apache.org/docs/latest/tools/control-script
>
> On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com>
> wrote:
>
>> Hi Charlin,
>>
>> I am working as a Principal Architect at GridGain.
>> Let me know if you would like to have a call to discuss your project and
>> needs, so I can figure out how to help you.
>>
>> Regards,
>> Rajiv Shah
>>
>> On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
>>
>>> Hi All,
>>> Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and
>>> found that
>>> ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is
>>> the alternative way for checking grids statistics and cache details without
>>> ignitevisorcmd tool.
>>>
>>> Thanks & Regards,
>>> Charlin
>>>
>>>
Re: ignitevisorcmd tool - alternate option
Posted by Pavel Tupitsyn <pt...@apache.org>.
control.sh is the replacement:
https://ignite.apache.org/docs/latest/tools/control-script
On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah <ra...@gridgain.com> wrote:
> Hi Charlin,
>
> I am working as a Principal Architect at GridGain.
> Let me know if you would like to have a call to discuss your project and
> needs, so I can figure out how to help you.
>
> Regards,
> Rajiv Shah
>
> On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
>
>> Hi All,
>> Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and
>> found that
>> ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is
>> the alternative way for checking grids statistics and cache details without
>> ignitevisorcmd tool.
>>
>> Thanks & Regards,
>> Charlin
>>
>>
Re: ignitevisorcmd tool - alternate option
Posted by Rajiv Shah <ra...@gridgain.com>.
Hi Charlin,
I am working as a Principal Architect at GridGain.
Let me know if you would like to have a call to discuss your project and
needs, so I can figure out how to help you.
Regards,
Rajiv Shah
On Wed, Apr 10, 2024 at 8:01 AM Charlin S <ch...@hotelhub.com> wrote:
> Hi All,
> Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and
> found that
> ignitevisorcmd tool had been removed from Ignite 2.15 onwards. What is
> the alternative way for checking grids statistics and cache details without
> ignitevisorcmd tool.
>
> Thanks & Regards,
> Charlin
>
>