ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-7637) Drop IGNITE_DAEMON property.
Date Tue, 06 Feb 2018 15:45:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Mashenkov updated IGNITE-7637:
-------------------------------------
    Description: 
We have IGNITE_DAEMON JVM property that just duplicates grid configuration property.

Usually, system options are used to override config defaults or as temporary solution to turn
on\off some Ignite modes that can't be done via config. 

Seems, this option usage is error prone as 
 * it is not really override an config option
 * we ignore this option in most cases when we check config.isDaemon().
 * it causes performance issue IGNITE-7508.

Also, I see no case when this option can be useful.

Let's drop IGNITE_DAEMON option and revert a IGNITE-7508.

  was:
We have IGNITE_DAEMON JVM property that just duplicates grid configuration property.

Usually, system options are used to override config defaults or as temporary solution to turn
on\off some Ignite modes that can't be done via config. 

Seems, this option usage is error prone as :
 * it is not really override an config option and it causes performance issue IGNITE-7508,
so we should cache it.
 * 
 * 
Also, I see no case when this option can be useful.

Let's drop IGNITE_DAEMON option and revert a IGNITE-7508.


> Drop IGNITE_DAEMON property.
> ----------------------------
>
>                 Key: IGNITE-7637
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7637
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Andrew Mashenkov
>            Priority: Major
>             Fix For: 3.0
>
>
> We have IGNITE_DAEMON JVM property that just duplicates grid configuration property.
> Usually, system options are used to override config defaults or as temporary solution
to turn on\off some Ignite modes that can't be done via config. 
> Seems, this option usage is error prone as 
>  * it is not really override an config option
>  * we ignore this option in most cases when we check config.isDaemon().
>  * it causes performance issue IGNITE-7508.
> Also, I see no case when this option can be useful.
> Let's drop IGNITE_DAEMON option and revert a IGNITE-7508.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message