Re: How suppress Ignite log message

2018-04-04 Thread aealexsandrov
Hello,

You can try to use next options:

-DIGNITE_NO_ASCII=true -DIGNITE_QUIET=false

1) IGNITE_NO_ASCII will turn off the Ignite ascii message:

if (System.getProperty(IGNITE_NO_ASCII) == null) {
String ver = "ver. " + ACK_VER_STR;

// Big thanks to: http://patorjk.com/software/taag
// Font name "Small Slant"
if (log.isInfoEnabled()) {
log.info(NL + NL +
">>>__    " + NL +
">>>   /  _/ ___/ |/ /  _/_  __/ __/  " + NL +
">>>  _/ // (7 7// /  / / / _/" + NL +
">>> /___/\\___/_/|_/___/ /_/ /___/   " + NL +

2)IGNITE_QUIET will hide other information from your example:

if (log.isQuiet())
U.quiet(false, "OS: " + U.osString());

if (log.isQuiet())
U.quiet(false, "VM information: " + U.jdkString());

Also you can try to change appenders options from the default log4j config
file:

^-- Logging by 'Log4JLogger [quiet=true,
config=/C:/GridGain/projects/gridgain/incubator-ignite/config/ignite-log4j.xml]'

Information about IGNITE_NO_ASCII , IGNITE_QUIET  and other
IgniteSystemProperties you can read here:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteSystemProperties.html

Best Regards,
Andrei




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: How suppress Ignite log message

2018-04-04 Thread Denis Magda
Paolo,

What was the part of the output you were concerned about? I haven't spotted
anything suspicious.

--
Denis

On Sat, Mar 24, 2018 at 8:55 AM, Paolo Di Tommaso  wrote:

> For the records, setting the sys property `IGNITE_QUIET=false` disable the
> output to the system output (a bit counterintuitive .. )
>
>
> p
>
> On Fri, Mar 23, 2018 at 12:13 PM, Paolo Di Tommaso <
> paolo.ditomm...@gmail.com> wrote:
>
>> Hi all,
>>
>> I'm migrating an application version 1.6 to 2.4.
>>
>> I've noticed the latter is printing to the stdout some logging
>> information (see below). How to hide that stuff?
>>
>> [12:10:58] OS: Mac OS X 10.11.6 x86_64
>> [12:10:58] VM information: Java(TM) SE Runtime Environment 1.8.0_161-b12
>> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.161-b12
>> [12:10:58] Initial heap size is 256MB (should be no less than 512MB, use
>> -Xms512m -Xmx512m).
>> [12:10:58] Configured plugins:
>> [12:10:58]   ^-- None
>> [12:10:58]
>> [12:11:00] Message queue limit is set to 0 which may lead to potential
>> OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due
>> to message queues growth on sender and receiver sides.
>> [12:11:00] Security status [authentication=off, tls/ssl=off]
>> [12:11:01] To start Console Management & Monitoring run
>> ignitevisorcmd.{sh|bat}
>> [12:11:01]
>> [12:11:01] Ignite node started OK (id=2e120cab, instance name=nextflow)
>> [12:11:01] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8,
>> offheap=3.2GB, heap=4.0GB]
>> [12:11:01] Data Regions Configured:
>> [12:11:01]   ^-- default [initSize=256.0 MiB, maxSize=3.2 GiB,
>> persistenceEnabled=false]
>>
>>
>>
>> p
>>
>
>


Re: How suppress Ignite log message

2018-03-24 Thread Paolo Di Tommaso
For the records, setting the sys property `IGNITE_QUIET=false` disable the
output to the system output (a bit counterintuitive .. )


p

On Fri, Mar 23, 2018 at 12:13 PM, Paolo Di Tommaso <
paolo.ditomm...@gmail.com> wrote:

> Hi all,
>
> I'm migrating an application version 1.6 to 2.4.
>
> I've noticed the latter is printing to the stdout some logging information
> (see below). How to hide that stuff?
>
> [12:10:58] OS: Mac OS X 10.11.6 x86_64
> [12:10:58] VM information: Java(TM) SE Runtime Environment 1.8.0_161-b12
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.161-b12
> [12:10:58] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [12:10:58] Configured plugins:
> [12:10:58]   ^-- None
> [12:10:58]
> [12:11:00] Message queue limit is set to 0 which may lead to potential
> OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due
> to message queues growth on sender and receiver sides.
> [12:11:00] Security status [authentication=off, tls/ssl=off]
> [12:11:01] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [12:11:01]
> [12:11:01] Ignite node started OK (id=2e120cab, instance name=nextflow)
> [12:11:01] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8,
> offheap=3.2GB, heap=4.0GB]
> [12:11:01] Data Regions Configured:
> [12:11:01]   ^-- default [initSize=256.0 MiB, maxSize=3.2 GiB,
> persistenceEnabled=false]
>
>
>
> p
>


How suppress Ignite log message

2018-03-23 Thread Paolo Di Tommaso
Hi all,

I'm migrating an application version 1.6 to 2.4.

I've noticed the latter is printing to the stdout some logging information
(see below). How to hide that stuff?

[12:10:58] OS: Mac OS X 10.11.6 x86_64
[12:10:58] VM information: Java(TM) SE Runtime Environment 1.8.0_161-b12
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.161-b12
[12:10:58] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[12:10:58] Configured plugins:
[12:10:58]   ^-- None
[12:10:58]
[12:11:00] Message queue limit is set to 0 which may lead to potential
OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due
to message queues growth on sender and receiver sides.
[12:11:00] Security status [authentication=off, tls/ssl=off]
[12:11:01] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[12:11:01]
[12:11:01] Ignite node started OK (id=2e120cab, instance name=nextflow)
[12:11:01] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8,
offheap=3.2GB, heap=4.0GB]
[12:11:01] Data Regions Configured:
[12:11:01]   ^-- default [initSize=256.0 MiB, maxSize=3.2 GiB,
persistenceEnabled=false]



p