You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/19 10:00:26 UTC
[jira] [Commented] (IGNITE-3925) Output process ID to the log
during node start.
[ https://issues.apache.org/jira/browse/IGNITE-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502933#comment-15502933 ]
ASF GitHub Bot commented on IGNITE-3925:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1082
IGNITE-3925: Output process ID to the log during node start.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3925
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1082.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1082
----
commit ebf354c568d0802b7eed1cc6b9d251941dbce014
Author: nikolay_tikhonov <nt...@gridgain.com>
Date: 2016-09-16T11:32:13Z
IGNITE-3907 Fixed "Incorrect initialization CQ when node filter configured for cache"
commit c0b2b4797be4f250f6f1304ff27d45c72154608a
Author: Valentin Kulichenko <va...@gmail.com>
Date: 2016-09-16T21:59:35Z
IGNITE-3635 - Fixed StackOverflowError thrown from BinaryObject.toString()
commit c24cabafd69804b3ac8e2c08895c9b9b9597a7f3
Author: Valentin Kulichenko <va...@gmail.com>
Date: 2016-09-16T21:59:51Z
Merge remote-tracking branch 'community/ignite-1.6.8' into ignite-1.6.8
commit 333cdb6f780e091f8f0e50af46a9ea7727003916
Author: Andrey V. Mashenkov <an...@gmail.com>
Date: 2016-09-19T09:57:36Z
Jvm pid added to startup message
----
> Output process ID to the log during node start.
> -----------------------------------------------
>
> Key: IGNITE-3925
> URL: https://issues.apache.org/jira/browse/IGNITE-3925
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: 1.7
> Reporter: Vladimir Ozerov
> Assignee: Andrew Mashenkov
> Priority: Minor
> Fix For: 1.8
>
>
> It might be very useful to know process ID of Ignite node. However, we do not output this info to the log. Let's add it.
> I would output it after {{VM total memory}} message.
> Since there is no reliable way to get PID in Java, we do our best to get it, but never throw and error if it is impossible for some reason.
> Start point: {{IgniteKernal.start}} and various {{IgniteKernal.ack*}} methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)