-user if IgniteLogger would have similar
features as any common Logger.
On 08.06.2023 17:45, Konstantin Orlov wrote:
Hi,
Please review "IEP-107 Logging in Ignite 3” proposal
IEP-107 Logging in Ignite 3 - Apache Ignite - Apache Software
Foundation
<https://cwiki.apache.org/confl
gt;
>>
>>> On 8 Jun 2023, at 18:14, Ilya Korol wrote:
>>>
>>> Hi Konstantin. Thanks for you work.
>>>
>>> Despite you proposal is more about public API of logging Ignite
>> facility, I believe that this thread is the best place to highl
should have name which
> starts with "%%” prefix.
>
> --
> Regards,
> Konstantin Orlov
>
>
>
>
> > On 8 Jun 2023, at 18:14, Ilya Korol wrote:
> >
> > Hi Konstantin. Thanks for you work.
> >
> > Despite you proposal is more about publi
starts with
"%%” prefix.
--
Regards,
Konstantin Orlov
> On 8 Jun 2023, at 18:14, Ilya Korol wrote:
>
> Hi Konstantin. Thanks for you work.
>
> Despite you proposal is more about public API of logging Ignite facility, I
> believe that this thread is the best place
Hi Konstantin. Thanks for you work.
Despite you proposal is more about public API of logging Ignite
facility, I believe that this thread is the best place to highlight some
topic about internal details of IgniteLogger based on my experience with
Ignite 2
I already tried to initiate a
Hi,
Please review "IEP-107 Logging in Ignite 3” proposal
https://cwiki.apache.org/confluence/display/IGNITE/IEP-107+Logging+in+Ignite+3
--
Regards,
Konstantin Orlov
NSAmelchev merged PR #8:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/8
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
NSAmelchev opened a new pull request, #8:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/8
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To un
Maria Makedonskaya created IGNITE-14565:
---
Summary: Add additional update counter logging for detect causes
of AssertionError: LWM after HWM
Key: IGNITE-14565
URL: https://issues.apache.org/jira/browse
Stanilovsky Evgeny created IGNITE-14224:
---
Summary: Extend logging of client failure handling.
Key: IGNITE-14224
URL: https://issues.apache.org/jira/browse/IGNITE-14224
Project: Ignite
Paolo Bazzi created IGNITE-14125:
Summary: GridClusterStateProcessor: Logging at INFO level without
checking if INFO level is enabled
Key: IGNITE-14125
URL: https://issues.apache.org/jira/browse/IGNITE-14125
Alexander Lapin created IGNITE-13869:
Summary: Add extra map query logging within the debug level.
Key: IGNITE-13869
URL: https://issues.apache.org/jira/browse/IGNITE-13869
Project: Ignite
Maria Makedonskaya created IGNITE-13818:
---
Summary: Add extended logging topology for node start
Key: IGNITE-13818
URL: https://issues.apache.org/jira/browse/IGNITE-13818
Project: Ignite
Sergey Chugunov created IGNITE-13557:
Summary: Logging improvements for PDS memory restore process
Key: IGNITE-13557
URL: https://issues.apache.org/jira/browse/IGNITE-13557
Project: Ignite
Denis Mekhanikov created IGNITE-13487:
-
Summary: Decrease logging level for exceptions throws from compute
engine
Key: IGNITE-13487
URL: https://issues.apache.org/jira/browse/IGNITE-13487
Project
Yaroslav Molochkov created IGNITE-13323:
---
Summary: GridDhtPartitionsExchangeFuture logging improvements
Key: IGNITE-13323
URL: https://issues.apache.org/jira/browse/IGNITE-13323
Project: Ignite
you know your typical
>>>> historical rebalance speed, you can trigger an alert if it drops below
>>>> that.
>>>>
>>>>> 03.07.2020, 02:49, "Stanislav Lukyanov" :
>>>>>> Kirill,
>>>>>>
>
ve looked through the patch.
>>>>> Looks good, but it feels like the first thing someone will try to do
>>>>> given bytesRcvd and duration is to divide one by another to get an
>>>>> average speed.
>>>>> Do you think it's reasonable to
duration is to divide one by another to get an average
>>>> speed.
>>>> Do you think it's reasonable to also add it to the logs? Maybe even to
>>>> the metrics?
>>>>
>>>> Also, this works with historical rebalance, right? Can we specify how
>>
>>> Also, this works with historical rebalance, right? Can we specify how much
>>> data was transferred via historical or full rebalance from each supplier?
>>> Maybe even estimate transfer speed in entries and bytes for each rebalance
>>> type?
>>&
t;
>>> On 29 Jun 2020, at 11:50, Ivan Rakov wrote:
>>>
>>> +1 to Alex G.
>>>
>>> From my experience, the most interesting cases with Ignite rebalancing
>>> happen exactly in production. According to the fact that we already have
>>>
e even estimate transfer speed in entries and bytes for each rebalance
> type?
>
> Thanks,
> Stan
>
>> On 29 Jun 2020, at 11:50, Ivan Rakov wrote:
>>
>> +1 to Alex G.
>>
>> From my experience, the most interesting cases with Ignite rebalancing
>> ha
> +1 to Alex G.
>
> From my experience, the most interesting cases with Ignite rebalancing
> happen exactly in production. According to the fact that we already have
> detailed rebalancing logging, adding info about rebalance performance looks
> like a reasonable improvement. With ne
+1 to Alex G.
>From my experience, the most interesting cases with Ignite rebalancing
happen exactly in production. According to the fact that we already have
detailed rebalancing logging, adding info about rebalance performance looks
like a reasonable improvement. With new logs we'll be
lexey Goncharuk" :
> Hello Maxim, folks,
>
> ср, 6 мая 2020 г. в 21:01, Maxim Muzafarov :
>
>> We won't do performance analysis on the production environment. Each
>> time we need performance analysis it will be done on a test
>> environment with verbose
Hello Maxim, folks,
ср, 6 мая 2020 г. в 21:01, Maxim Muzafarov :
> We won't do performance analysis on the production environment. Each
> time we need performance analysis it will be done on a test
> environment with verbose logging enabled. Thus I suggest moving these
> chan
[2020-05-06 20:56:36,999][INFO ][...] Completed rebalance chain:
> >> [rebalanceId=2, entries=200, duration=50ms, bytesRcvd=10M]
> >>
> >> Another thing I would suggest: add rebalanceId to all messages for
> ease of
> >> grepping and to distinguish multiple re
rsion.
>>
>> Regarding the "detailed" message - I wasn't able to figure out any case
>> where it is useful. Not sure if we need it at all.
>> Kirill Tkalenko, can you give me an example?
>>
>> ср, 6 мая 2020 г. в 21:01, Maxim Muzafarov :
>>
or put it under debug logging.
Information about selected suppliers can already be obtained from logs:
[2020-05-06 20:56:37,034][INFO ][...] Prepared rebalancing [grp=cache1,
mode=ASYNC, supplier=94a3fcbc-18d5-4c64-b0ab-4313aba1,
partitionsCount=11, topVer=AffinityTopologyVersion [topVer=3
> On Mon, 25 May 2020 at 12:36, Ivan Pavlukhin wrote:
>>
>> Maxim,
>>
>> I looked into the code and checked how do we setup uncaught exception
>> handlers for internal executors. Indeed it looks not good (OOME leads
>> to failure handling, other exceptions are sil
ing, other exceptions are silently ignored). Logging
> sounds good.
>
> Have doubts about failure handling (e.g. terminating a node). I
> remember at least one related discussion [1]. And here are some
> statements which causes my doubts:
> 1. Not only assertion errors are a progr
Maxim,
I looked into the code and checked how do we setup uncaught exception
handlers for internal executors. Indeed it looks not good (OOME leads
to failure handling, other exceptions are silently ignored). Logging
sounds good.
Have doubts about failure handling (e.g. terminating a node). I
> >> if (change)
> >> CUR_PLC.set(oldPlc);
> >> }
> >> ```
> >>
> >> If an exception thrown from `withContext` it is hidden from the user.
> >>
> >> > 4 мая 2020 г., в 19:15, Maxim Muzafarov написал(а):
&
исал(а):
>> >
>> > Igniters,
>> >
>> >
>> > I've spent a couple of days in debug mode and found that some of the
>> > configured ExecutorServices of an Ignite instance completely hide
>> > assertion errors without any logging and
d that some of the
> > configured ExecutorServices of an Ignite instance completely hide
> > assertion errors without any logging and node killing. This may
> > violate some internal guarantees and hide serious errors.
> >
> > Let's consider, for instance, GridDht
true that the rebalance process
>> still requires additional information for analyzing issues. Please,
>> don't think that I'm against your changes :-)
>>
>> * My short answer. *
>>
>> We won't do performance analysis on the production env
Hi, Maxim! Unfortunately, I delayed my answer.
The production environment may not be ideal and problems may occur in it. I
only suggest adding a little logging to understand some of the cases that may
occur during operation. In addition, this functionality can be disabled by the
system
Anton Vinogradov created IGNITE-13009:
-
Summary: NoopTimeBag should be used if logging disabled
Key: IGNITE-13009
URL: https://issues.apache.org/jira/browse/IGNITE-13009
Project: Ignite
Hi, Igniters!
>>
>> I'd like to share a new small feature in AI [1].
>>
>> Current rebalance logging does not allow you to quickly answer following
>> questions:
>> 1)How long was the balance(divided by supplier)?
>> 2)How many records and bytes
; * My short answer. *
>
> We won't do performance analysis on the production environment. Each
> time we need performance analysis it will be done on a test
> environment with verbose logging enabled. Thus I suggest moving these
> changes to a separate `profiling` module and exten
onment. Each
time we need performance analysis it will be done on a test
environment with verbose logging enabled. Thus I suggest moving these
changes to a separate `profiling` module and extend the logging much
more without any ышяу limitations. The same as these [2] [3]
activities do.
Let's
short version of the message (with supplier statistics) will show up?
In general, I have no objections.
On Mon, May 4, 2020 at 10:38 AM ткаленко кирилл
wrote:
> Hi, Igniters!
>
> I'd like to share a new small feature in AI [1].
>
> Current rebalance logging does not allow you t
Denis Garus created IGNITE-12983:
Summary: Logging exceptions inside
IgniteSecurityProcessor#withContext(java.util.UUID)
Key: IGNITE-12983
URL: https://issues.apache.org/jira/browse/IGNITE-12983
e of days in debug mode and found that some of the
> configured ExecutorServices of an Ignite instance completely hide
> assertion errors without any logging and node killing. This may
> violate some internal guarantees and hide serious errors.
>
> Let's consider, for instan
Igniters,
I've spent a couple of days in debug mode and found that some of the
configured ExecutorServices of an Ignite instance completely hide
assertion errors without any logging and node killing. This may
violate some internal guarantees and hide serious errors.
Let's consider, fo
Hi, Igniters!
I'd like to share a new small feature in AI [1].
Current rebalance logging does not allow you to quickly answer following
questions:
1)How long was the balance(divided by supplier)?
2)How many records and bytes per supplier were rebalanced?
3)How many times did rebalance re
Sergey Chugunov created IGNITE-12878:
Summary: Improve logging for async writing of Binary Metadata
Key: IGNITE-12878
URL: https://issues.apache.org/jira/browse/IGNITE-12878
Project: Ignite
Stepan Pilschikov created IGNITE-12673:
--
Summary: ML examples logging
Key: IGNITE-12673
URL: https://issues.apache.org/jira/browse/IGNITE-12673
Project: Ignite
Issue Type: Bug
Mykhaylo Stepanov created IGNITE-12526:
--
Summary: WAL file archiver logging bug
Key: IGNITE-12526
URL: https://issues.apache.org/jira/browse/IGNITE-12526
Project: Ignite
Issue Type: Bug
; --
>>> Ilya Kasnacheev
>>>
>>>
>>> чт, 26 дек. 2019 г. в 12:10, Ivan Pavlukhin :
>>>
>>>> Ilya,
>>>>
>>>> Indeed the matters can be improved.
>>>>
>>>> Is not it useful to mark what regio
what region is default? Also some doubts
>>> about internal memory regions. It is not obvious that we should print
>>> an information about them for every user. If we need to have some
>>> determinism about offheap memory than I can think about logging
>>> amounts f
t;
>> Indeed the matters can be improved.
>>
>> Is not it useful to mark what region is default? Also some doubts
>> about internal memory regions. It is not obvious that we should print
>> an information about them for every user. If we need to have some
>> determini
Ilya Kasnacheev created IGNITE-12505:
Summary: Improve logging of data regions on startup
Key: IGNITE-12505
URL: https://issues.apache.org/jira/browse/IGNITE-12505
Project: Ignite
Issue
ffheap memory than I can think about logging
> amounts for internal needs of total ones (a sum for all regions).
>
> вт, 24 дек. 2019 г. в 15:38, Ilya Kasnacheev :
> >
> > Hello!
> >
> > It came to my attention that we output data regions' configurations twice
&g
about logging
amounts for internal needs of total ones (a sum for all regions).
вт, 24 дек. 2019 г. в 15:38, Ilya Kasnacheev :
>
> Hello!
>
> It came to my attention that we output data regions' configurations twice
> when starting node, but we never output list of data regions
Hello!
It came to my attention that we output data regions' configurations twice
when starting node, but we never output list of data regions (including
system, etc) that were actually started.
First we have IgniteConfiguration printed (quiet=false):
2019-07-24 02:33:33.918[INFO ][Thread-139][o.a
PetrovMikhail created IGNITE-12250:
--
Summary: Adds REST requests processing logging.
Key: IGNITE-12250
URL: https://issues.apache.org/jira/browse/IGNITE-12250
Project: Ignite
Issue Type
Andrey Gura created IGNITE-12231:
Summary: RollbackRecord's must be flushed after logging to WAL
Key: IGNITE-12231
URL: https://issues.apache.org/jira/browse/IGNITE-12231
Project: I
Ilya Kasnacheev created IGNITE-12178:
Summary: DEBUG logging may throw exception from toString of tx
objects
Key: IGNITE-12178
URL: https://issues.apache.org/jira/browse/IGNITE-12178
Project
Kirill Tkalenko created IGNITE-12080:
Summary: Add extended logging for rebalance
Key: IGNITE-12080
URL: https://issues.apache.org/jira/browse/IGNITE-12080
Project: Ignite
Issue Type
Anton Kalashnikov created IGNITE-11545:
--
Summary: Logging baseline auto-adjust
Key: IGNITE-11545
URL: https://issues.apache.org/jira/browse/IGNITE-11545
Project: Ignite
Issue Type: Bug
Dmitriy Pavlov created IGNITE-11486:
---
Summary: Support Automatic modules for ignite-zookeeper: Resolve
issues with logging packages conflict
Key: IGNITE-11486
URL: https://issues.apache.org/jira/browse/IGNITE
Ivan Rakov created IGNITE-11199:
---
Summary: Extend logging for client-server connections in TCP
discovery
Key: IGNITE-11199
URL: https://issues.apache.org/jira/browse/IGNITE-11199
Project: Ignite
Sergey Antonov created IGNITE-10826:
---
Summary: Control.sh add logging to file
Key: IGNITE-10826
URL: https://issues.apache.org/jira/browse/IGNITE-10826
Project: Ignite
Issue Type
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1922
---
Github user akuznetsov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/5581
---
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5581
IGNITE-10552 Web Agent: Improve logging when cluster topology changed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Alexey Kuznetsov created IGNITE-10552:
-
Summary: Web Agent: Improve logging when cluster topology changed
Key: IGNITE-10552
URL: https://issues.apache.org/jira/browse/IGNITE-10552
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5413
---
GitHub user voropava opened a pull request:
https://github.com/apache/ignite/pull/5413
IGNITE-10295 Added info logging for long connection establish methodsâ¦
â¦, removed useless logging of Sending Full Message.
You can merge this pull request into a Git repository by running
Pavel Voronkin created IGNITE-10295:
---
Summary: Rework Sending Full Message logging.
Key: IGNITE-10295
URL: https://issues.apache.org/jira/browse/IGNITE-10295
Project: Ignite
Issue Type
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/5211
---
Alexey Kuznetsov created IGNITE-10089:
-
Summary: Web Console: Implement debug logging and allow to enable
it at runtime
Key: IGNITE-10089
URL: https://issues.apache.org/jira/browse/IGNITE-10089
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5211
IGNITE-10062: improve logging on binary recovery
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-10062
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5156
---
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5156
IGNITE-10033: fix logging according coding guidelines
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-10033
Alternatively
Alexey Goncharuk created IGNITE-:
Summary: Add verbose logging for node recovery
Key: IGNITE-
URL: https://issues.apache.org/jira/browse/IGNITE-
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-9934:
-
Summary: Improve logging on partition map exchange
Key: IGNITE-9934
URL: https://issues.apache.org/jira/browse/IGNITE-9934
Project: Ignite
Issue
Max Shonichev created IGNITE-9859:
-
Summary: add debug logging on resendPartitions cause
Key: IGNITE-9859
URL: https://issues.apache.org/jira/browse/IGNITE-9859
Project: Ignite
Issue Type
Pavel Kovalenko created IGNITE-9649:
---
Summary: Rework logging in important places
Key: IGNITE-9649
URL: https://issues.apache.org/jira/browse/IGNITE-9649
Project: Ignite
Issue Type
GitHub user ololo3000 opened a pull request:
https://github.com/apache/ignite/pull/4635
IGNITE-9149 Get rid of logging remaining supplier nodes rebalance time
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ololo3000/ignite
Maxim Muzafarov created IGNITE-9149:
---
Summary: Get rid of logging remaining supllier nodes rebalance time
Key: IGNITE-9149
URL: https://issues.apache.org/jira/browse/IGNITE-9149
Project: Ignite
Sergey Chugunov created IGNITE-9003:
---
Summary: walSegmentsCleared piece of checkpoint logging improvement
Key: IGNITE-9003
URL: https://issues.apache.org/jira/browse/IGNITE-9003
Project: Ignite
Ilya Kasnacheev created IGNITE-8948:
---
Summary: Allow checking of LOGGING status via SQL/JDBC
Key: IGNITE-8948
URL: https://issues.apache.org/jira/browse/IGNITE-8948
Project: Ignite
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4244
---
Andrew Mashenkov created IGNITE-8878:
Summary: Make WebConsole agent logging more verbose.
Key: IGNITE-8878
URL: https://issues.apache.org/jira/browse/IGNITE-8878
Project: Ignite
Issue
GitHub user andrewmed opened a pull request:
https://github.com/apache/ignite/pull/4244
IGNITE-8737: Improve checkpoint logging information
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewmed/ignite ignite-8737-2
Github user andrewmed closed the pull request at:
https://github.com/apache/ignite/pull/4186
---
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4225
IGNITE-8827 disable WAL logging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8827
Alternatively
Alexey Goncharuk created IGNITE-8798:
Summary: Move transaction recovery logging to INFO level
Key: IGNITE-8798
URL: https://issues.apache.org/jira/browse/IGNITE-8798
Project: Ignite
GitHub user andrewmed opened a pull request:
https://github.com/apache/ignite/pull/4186
IGNITE-8737: Improve checkpoint logging information
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewmed/ignite ignite-8737
Alexey Goncharuk created IGNITE-8737:
Summary: Improve checkpoint logging information
Key: IGNITE-8737
URL: https://issues.apache.org/jira/browse/IGNITE-8737
Project: Ignite
Issue Type
Stanilovsky Evgeny created IGNITE-8724:
--
Summary: Skip logging 3-rd parameter while calling U.warn with
initialized logger.
Key: IGNITE-8724
URL: https://issues.apache.org/jira/browse/IGNITE-8724
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4087
---
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4087
IGNITE-8636 debug logging for client join scenario
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Sergey Chugunov created IGNITE-8636:
---
Summary: Debug logging improvements for Partition Map Exchange
process
Key: IGNITE-8636
URL: https://issues.apache.org/jira/browse/IGNITE-8636
Project: Ignite
Alexey Kuznetsov created IGNITE-8536:
Summary: DirectMemoryRegion: Introduce checkpoint buffer
configuration and improve logging o start
Key: IGNITE-8536
URL: https://issues.apache.org/jira/browse/IGNITE
Taras Ledkov created IGNITE-8024:
Summary: Enhance JDBC logging
Key: IGNITE-8024
URL: https://issues.apache.org/jira/browse/IGNITE-8024
Project: Ignite
Issue Type: Task
Components
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/3598
---
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/3598
---
1 - 100 of 165 matches
Mail list logo
