You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Raymond Wilson <ra...@trimble.com> on 2020/12/29 05:50:29 UTC
Feature request: On demand thread dumps from Ignite
Many of the discussion threads here will generate a request for the Jave
Ignite thread dump to help triage an issue.
This is not difficult to do with command line Java tooling if you can
easily access the server running the node. However, access to those nodes
may not be simple (especially in production) and requires hands-on manual
intervention to produce.
There does not seem to be a way for an Ignite client (eg: the C# client we
use in our implementation) to ask the local Ignite node to dump the thread
state to the log based on conditions the client itself may determine.
If this is actually the case then please point me at it:) Otherwise, is
this something worth adding to the backlog?
Thanks,
Raymond.
--
<http://www.trimble.com/>
Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wilson@trimble.com
<https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
Re[2]: Feature request: On demand thread dumps from Ignite
Posted by Zhenya Stanilovsky <ar...@mail.ru>.
I understand that you use C# of course, you can use var process = new Process ( ) for it and furthet jstack -l PID call
>Hi Zhenya,
>
>We use the IA C# client (deployed in a.Net Core implementation using containers on AWS EKS) so this makes it hard for us to run Java closures from the C# client, which is why a client interface capability would be useful!
>
>Thanks,
>Raymond.
>
>On Tue, Dec 29, 2020 at 8:38 PM Zhenya Stanilovsky < arzamas123@mail.ru > wrote:
>>
>>You can call it through compute api [1], i suppose.
>>
>>[1] https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing
>>
>>>Many of the discussion threads here will generate a request for the Jave Ignite thread dump to help triage an issue.
>>>
>>>This is not difficult to do with command line Java tooling if you can easily access the server running the node. However, access to those nodes may not be simple (especially in production) and requires hands-on manual intervention to produce.
>>>
>>>There does not seem to be a way for an Ignite client (eg: the C# client we use in our implementation) to ask the local Ignite node to dump the thread state to the log based on conditions the client itself may determine.
>>>
>>>If this is actually the case then please point me at it:) Otherwise, is this something worth adding to the backlog?
>>>
>>>Thanks,
>>>Raymond.
>>> --
>>>
>>>Raymond Wilson
>>>Solution Architect, Civil Construction Software Systems (CCSS)
>>>11 Birmingham Drive | Christchurch, New Zealand
>>>+64-21-2013317 Mobile
>>>raymond_wilson@trimble.com
>>>
>>>
>>
>>
>>
>>
>
> --
>
>Raymond Wilson
>Solution Architect, Civil Construction Software Systems (CCSS)
>11 Birmingham Drive | Christchurch, New Zealand
>+64-21-2013317 Mobile
>raymond_wilson@trimble.com
>
>
Re: Feature request: On demand thread dumps from Ignite
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I guess you could find a way to run ThreadDumpPrinterTask or better yet a
VisorThreadDumpTask.
I guess we should have thread dumping in the upcoming ignitectl.
Can you file a ticket?
Regards,
--
Ilya Kasnacheev
вт, 29 дек. 2020 г. в 10:42, Raymond Wilson <ra...@trimble.com>:
> Hi Zhenya,
>
> We use the IA C# client (deployed in a.Net Core implementation using
> containers on AWS EKS) so this makes it hard for us to run Java closures
> from the C# client, which is why a client interface capability would be
> useful!
>
> Thanks,
> Raymond.
>
>
> On Tue, Dec 29, 2020 at 8:38 PM Zhenya Stanilovsky <ar...@mail.ru>
> wrote:
>
>>
>> You can call it through compute api [1], i suppose.
>>
>> [1]
>> https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing
>>
>>
>> Many of the discussion threads here will generate a request for the Jave
>> Ignite thread dump to help triage an issue.
>>
>> This is not difficult to do with command line Java tooling if you can
>> easily access the server running the node. However, access to those nodes
>> may not be simple (especially in production) and requires hands-on manual
>> intervention to produce.
>>
>> There does not seem to be a way for an Ignite client (eg: the C# client
>> we use in our implementation) to ask the local Ignite node to dump the
>> thread state to the log based on conditions the client itself may determine.
>>
>> If this is actually the case then please point me at it:) Otherwise, is
>> this something worth adding to the backlog?
>>
>> Thanks,
>> Raymond.
>>
>> --
>> <http://www.trimble.com/>
>> Raymond Wilson
>> Solution Architect, Civil Construction Software Systems (CCSS)
>> 11 Birmingham Drive | Christchurch, New Zealand
>> +64-21-2013317 Mobile
>> raymond_wilson@trimble.com
>> <//...@trimble.com>
>>
>>
>>
>> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>>
>>
>>
>>
>>
>>
>
>
> --
> <http://www.trimble.com/>
> Raymond Wilson
> Solution Architect, Civil Construction Software Systems (CCSS)
> 11 Birmingham Drive | Christchurch, New Zealand
> +64-21-2013317 Mobile
> raymond_wilson@trimble.com
>
>
> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>
Re: Feature request: On demand thread dumps from Ignite
Posted by Raymond Wilson <ra...@trimble.com>.
Hi Zhenya,
We use the IA C# client (deployed in a.Net Core implementation using
containers on AWS EKS) so this makes it hard for us to run Java closures
from the C# client, which is why a client interface capability would be
useful!
Thanks,
Raymond.
On Tue, Dec 29, 2020 at 8:38 PM Zhenya Stanilovsky <ar...@mail.ru>
wrote:
>
> You can call it through compute api [1], i suppose.
>
> [1]
> https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing
>
>
> Many of the discussion threads here will generate a request for the Jave
> Ignite thread dump to help triage an issue.
>
> This is not difficult to do with command line Java tooling if you can
> easily access the server running the node. However, access to those nodes
> may not be simple (especially in production) and requires hands-on manual
> intervention to produce.
>
> There does not seem to be a way for an Ignite client (eg: the C# client we
> use in our implementation) to ask the local Ignite node to dump the thread
> state to the log based on conditions the client itself may determine.
>
> If this is actually the case then please point me at it:) Otherwise, is
> this something worth adding to the backlog?
>
> Thanks,
> Raymond.
>
> --
> <http://www.trimble.com/>
> Raymond Wilson
> Solution Architect, Civil Construction Software Systems (CCSS)
> 11 Birmingham Drive | Christchurch, New Zealand
> +64-21-2013317 Mobile
> raymond_wilson@trimble.com
> <//...@trimble.com>
>
>
>
> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
>
>
>
>
>
>
--
<http://www.trimble.com/>
Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wilson@trimble.com
<https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
Re: Feature request: On demand thread dumps from Ignite
Posted by Zhenya Stanilovsky <ar...@mail.ru>.
You can call it through compute api [1], i suppose.
[1] https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing
>Many of the discussion threads here will generate a request for the Jave Ignite thread dump to help triage an issue.
>
>This is not difficult to do with command line Java tooling if you can easily access the server running the node. However, access to those nodes may not be simple (especially in production) and requires hands-on manual intervention to produce.
>
>There does not seem to be a way for an Ignite client (eg: the C# client we use in our implementation) to ask the local Ignite node to dump the thread state to the log based on conditions the client itself may determine.
>
>If this is actually the case then please point me at it:) Otherwise, is this something worth adding to the backlog?
>
>Thanks,
>Raymond.
> --
>
>Raymond Wilson
>Solution Architect, Civil Construction Software Systems (CCSS)
>11 Birmingham Drive | Christchurch, New Zealand
>+64-21-2013317 Mobile
>raymond_wilson@trimble.com
>
>