My point is different. Before I had to do this only assuming that “Ignite will
spend 99%” sending events:
<property name="includeEventTypes">
<list>
<!--Task execution events-->
<util:constant
static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED"/>
<util:constant
static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED"/>
<util:constant
static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED"/>
<util:constant
static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT"/>
</list>
</property>
Now the platform forces me to do that (probably thinking that I’m crazy if I
want to waste resources for metrics and giving one more change to contemplate
the decision):
<property name="eventStorageSpi">
<bean
class="org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpi"/>
</property>
Does the issue make sense to you know?
—
Denis
> On Sep 7, 2017, at 7:25 PM, Dmitriy Setrakyan <[email protected]> wrote:
>
> On Thu, Sep 7, 2017 at 7:19 PM, Denis Magda <[email protected]> wrote:
>
>> Any metric from of org.apache.ignite.events.EventType (cache operations,
>> compute, etc.)
>>
>
> If you enable them all, Ignite will spend 99% of its time doing event
> notifications.
>
>
>>
>> —
>> Denis
>>
>>> On Sep 7, 2017, at 7:15 PM, Dmitriy Setrakyan <[email protected]>
>> wrote:
>>>
>>> Denis, which metrics are you talking about?
>>>
>>> On Thu, Sep 7, 2017 at 7:12 PM, Denis Magda <[email protected]> wrote:
>>>
>>>> Igniters,
>>>>
>>>> It was a surprise for me to reveal that even if the default config is
>> used
>>>> [1] I still will not see the metrics in Web Console or in a custom app.
>>>> However, the config was left unchanged for a while and from the first
>> look
>>>> encompassed everything we need to start getting metrics.
>>>>
>>>> But, after looking into the issue, it was determined that this bean has
>> to
>>>> added explicitly:
>>>>
>>>> <property name="eventStorageSpi">
>>>> <bean class="org.apache.ignite.spi.eventstorage.memory.
>>>> MemoryEventStorageSpi"/>
>>>> </property>
>>>>
>>>> So, my question, what do we do next? It’s ridiculous to force setting
>> this
>>>> parameter. The NoopEventStorageSpi (default) simply ignores all the
>> events.
>>>> Why doesn’t it accept them, send to the subscribers and skips? Then
>> it’s up
>>>> to a subscriber to decide what to do next.
>>>>
>>>> [1] https://github.com/apache/ignite/blob/master/examples/
>>>> config/example-default.xml <https://github.com/apache/
>>>> ignite/blob/master/examples/config/example-default.xml>
>>>>
>>>> —
>>>> Denis
>>
>>
