[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[
https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov updated IGNITE-15918:
Affects Version/s: 2.11
> Whorng dimension for AveragePutTime and AverageGetTime
> --
>
> Key: IGNITE-15918
> URL: https://issues.apache.org/jira/browse/IGNITE-15918
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Igor Akkuratov
>Priority: Minor
> Labels: .NET, Documentation
>
> After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and
> AverageGetTime.
> {code:java}
> ///
> /// The mean time to execute gets.
> ///
> ///
> /// The time in ms.
> ///
> float AverageGetTime { get; }
> ///
> /// The mean time to execute puts.
> ///
> ///
> /// The time in s.
> ///
> float AveragePutTime { get; }{code}
> Return value for getTime in ms, for putTime in s whenever in javadoc there
> are both in µs
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheMetrics.html#getAveragePutTime--
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[
https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov updated IGNITE-15918:
Labels: .NET Documentation (was: .NET)
> Whorng dimension for AveragePutTime and AverageGetTime
> --
>
> Key: IGNITE-15918
> URL: https://issues.apache.org/jira/browse/IGNITE-15918
> Project: Ignite
> Issue Type: Bug
>Reporter: Igor Akkuratov
>Priority: Minor
> Labels: .NET, Documentation
>
> After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and
> AverageGetTime.
> {code:java}
> ///
> /// The mean time to execute gets.
> ///
> ///
> /// The time in ms.
> ///
> float AverageGetTime { get; }
> ///
> /// The mean time to execute puts.
> ///
> ///
> /// The time in s.
> ///
> float AveragePutTime { get; }{code}
> Return value for getTime in ms, for putTime in s whenever in javadoc there
> are both in µs
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheMetrics.html#getAveragePutTime--
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[
https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov updated IGNITE-15918:
Description:
After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and
AverageGetTime.
{code:java}
///
/// The mean time to execute gets.
///
///
/// The time in ms.
///
float AverageGetTime { get; }
///
/// The mean time to execute puts.
///
///
/// The time in s.
///
float AveragePutTime { get; }{code}
Return value for getTime in ms, for putTime in s whenever in javadoc there are
both in µs
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheMetrics.html#getAveragePutTime--
was:
After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and
AverageGetTime.
We
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.ICacheMetrics.html
> Whorng dimension for AveragePutTime and AverageGetTime
> --
>
> Key: IGNITE-15918
> URL: https://issues.apache.org/jira/browse/IGNITE-15918
> Project: Ignite
> Issue Type: Bug
>Reporter: Igor Akkuratov
>Priority: Minor
> Labels: .NET
>
> After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and
> AverageGetTime.
> {code:java}
> ///
> /// The mean time to execute gets.
> ///
> ///
> /// The time in ms.
> ///
> float AverageGetTime { get; }
> ///
> /// The mean time to execute puts.
> ///
> ///
> /// The time in s.
> ///
> float AveragePutTime { get; }{code}
> Return value for getTime in ms, for putTime in s whenever in javadoc there
> are both in µs
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheMetrics.html#getAveragePutTime--
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[ https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-15918: Labels: .NET (was: ) > Whorng dimension for AveragePutTime and AverageGetTime > -- > > Key: IGNITE-15918 > URL: https://issues.apache.org/jira/browse/IGNITE-15918 > Project: Ignite > Issue Type: Bug >Reporter: Igor Akkuratov >Priority: Minor > Labels: .NET > > After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and > AverageGetTime. > We > https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.ICacheMetrics.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[ https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-15918: Description: After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and AverageGetTime. We https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.ICacheMetrics.html was:After IGNITE-4234 there are wrongs dimensions for mertics > Whorng dimension for AveragePutTime and AverageGetTime > -- > > Key: IGNITE-15918 > URL: https://issues.apache.org/jira/browse/IGNITE-15918 > Project: Ignite > Issue Type: Bug >Reporter: Igor Akkuratov >Priority: Minor > > After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and > AverageGetTime. > We > https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.ICacheMetrics.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[ https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-15918: Description: After IGNITE-4234 there are wrongs dimensions for mertics (was: After) > Whorng dimension for AveragePutTime and AverageGetTime > -- > > Key: IGNITE-15918 > URL: https://issues.apache.org/jira/browse/IGNITE-15918 > Project: Ignite > Issue Type: Bug >Reporter: Igor Akkuratov >Priority: Minor > > After IGNITE-4234 there are wrongs dimensions for mertics -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
[ https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-15918: Description: After > Whorng dimension for AveragePutTime and AverageGetTime > -- > > Key: IGNITE-15918 > URL: https://issues.apache.org/jira/browse/IGNITE-15918 > Project: Ignite > Issue Type: Bug >Reporter: Igor Akkuratov >Priority: Minor > > After -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15918) Whorng dimension for AveragePutTime and AverageGetTime
Igor Akkuratov created IGNITE-15918: --- Summary: Whorng dimension for AveragePutTime and AverageGetTime Key: IGNITE-15918 URL: https://issues.apache.org/jira/browse/IGNITE-15918 Project: Ignite Issue Type: Bug Reporter: Igor Akkuratov -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14676) Send ignite events to zabbix
[ https://issues.apache.org/jira/browse/IGNITE-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-14676: Description: There are a lot of events that can be monitored by logs only, like pme or rebalance start and so on. I want to create EventStorege that would be able to send events to different monitoring systems. was:There are a lot of events on node > Send ignite events to zabbix > > > Key: IGNITE-14676 > URL: https://issues.apache.org/jira/browse/IGNITE-14676 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > > There are a lot of events that can be monitored by logs only, like pme or > rebalance start and so on. > I want to create EventStorege that would be able to send events to different > monitoring systems. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14676) Send ignite events to zabbix
[ https://issues.apache.org/jira/browse/IGNITE-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-14676: Summary: Send ignite events to zabbix (was: Send grid events to zabbix) > Send ignite events to zabbix > > > Key: IGNITE-14676 > URL: https://issues.apache.org/jira/browse/IGNITE-14676 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > > There are a lot of events on node -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14676) Send grid events to zabbix
[ https://issues.apache.org/jira/browse/IGNITE-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-14676: Description: There are a lot of events on node > Send grid events to zabbix > -- > > Key: IGNITE-14676 > URL: https://issues.apache.org/jira/browse/IGNITE-14676 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > > There are a lot of events on node -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14676) Send grid events to zabbix
Igor Akkuratov created IGNITE-14676: --- Summary: Send grid events to zabbix Key: IGNITE-14676 URL: https://issues.apache.org/jira/browse/IGNITE-14676 Project: Ignite Issue Type: Improvement Reporter: Igor Akkuratov Assignee: Igor Akkuratov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12920) Static hierarchy in jmx tree
[
https://issues.apache.org/jira/browse/IGNITE-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov reassigned IGNITE-12920:
---
Assignee: Igor Akkuratov
> Static hierarchy in jmx tree
>
>
> Key: IGNITE-12920
> URL: https://issues.apache.org/jira/browse/IGNITE-12920
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Akkuratov
>Assignee: Igor Akkuratov
>Priority: Major
> Attachments: image-2020-04-20-17-05-36-451.png
>
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains
> classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader
> is been changing after node restart and monitoring systems rediscover new
> metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to
> create single monitoring template for different deployments. It can also make
> troubles if you want to start more then one ignite instance in single jvm. In
> this case you'll have to set {color:#1d1c1d}igniteInstanceName{color}
> property to add one more level with the name of this instance. It will affect
> jmx tree hierarchy as well.
> I propose to make hierarchy unchangeable and select one of the following
> values.
> If exist instancename
> else if exist consistantId
>
> In cases with enabled persistent storage consistent id would be the same
> between node restarts, in in-memory cases you will be able to specify
> instanceName.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12920) Static hierarchy in jmx tree
[
https://issues.apache.org/jira/browse/IGNITE-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov reassigned IGNITE-12920:
---
Assignee: (was: Igor Akkuratov)
> Static hierarchy in jmx tree
>
>
> Key: IGNITE-12920
> URL: https://issues.apache.org/jira/browse/IGNITE-12920
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Akkuratov
>Priority: Major
> Attachments: image-2020-04-20-17-05-36-451.png
>
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains
> classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader
> is been changing after node restart and monitoring systems rediscover new
> metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to
> create single monitoring template for different deployments. It can also make
> troubles if you want to start more then one ignite instance in single jvm. In
> this case you'll have to set {color:#1d1c1d}igniteInstanceName{color}
> property to add one more level with the name of this instance. It will affect
> jmx tree hierarchy as well.
> I propose to make hierarchy unchangeable and select one of the following
> values.
> If exist instancename
> else if exist consistantId
>
> In cases with enabled persistent storage consistent id would be the same
> between node restarts, in in-memory cases you will be able to specify
> instanceName.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12920) Static hierarchy in jmx tree
[
https://issues.apache.org/jira/browse/IGNITE-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov updated IGNITE-12920:
Description:
Current jmx tree hierarchy depends on jvm and ignite options and contains
classloader by default.
!image-2020-04-20-17-05-36-451.png!
Monitoring systems like zabbix use bean path to discover metrics. Classloader
is been changing after node restart and monitoring systems rediscover new
metrics. If you'll try to disable classloader with option
{code:java}
IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
the jmx tree will exclude one level. This behavior excludes an opportunity to
create single monitoring template for different deployments. It can also make
troubles if you want to start more then one ignite instance in single jvm. In
this case you'll have to set {color:#1d1c1d}igniteInstanceName{color} property
to add one more level with the name of this instance. It will affect jmx tree
hierarchy as well.
I propose to make hierarchy unchangeable and select one of the following
values.
If exist instancename
else if exist consistantId
In cases with enabled persistent storage consistent id would be the same
between node restarts, in in-memory cases you will be able to specify
instanceName.
was:
Current jmx tree hierarchy depends on jvm and ignite options and by default
contains classloader.
!image-2020-04-20-17-05-36-451.png!
Monitoring systems like zabbix use bean path to discover metrics. In this case
classloader would be new after each node restart. If you'll disable classloader
with option {color:#1d1c1d}{color}
{code:java}
IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
{color:#1d1c1d}{color} the jmx tree would exclude one level. This behavior
excludes an opportunity to create single monitoring template for different
deployments. And make troubles if you want to start more then one ignite
instance in single jvm. In this case you should set
{color:#1d1c1d}igniteInstanceName{color} property to add one more level with
instance name. And it's also changes jmx tree hierarchy.
I offer to make hierarchy unchangeable and select one of the following values.
If exist instancename
else if exist consistantId
In persistent cases consistent id would be the same between node restarts.
> Static hierarchy in jmx tree
>
>
> Key: IGNITE-12920
> URL: https://issues.apache.org/jira/browse/IGNITE-12920
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Akkuratov
>Assignee: Igor Akkuratov
>Priority: Major
> Attachments: image-2020-04-20-17-05-36-451.png
>
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains
> classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader
> is been changing after node restart and monitoring systems rediscover new
> metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to
> create single monitoring template for different deployments. It can also make
> troubles if you want to start more then one ignite instance in single jvm. In
> this case you'll have to set {color:#1d1c1d}igniteInstanceName{color}
> property to add one more level with the name of this instance. It will affect
> jmx tree hierarchy as well.
> I propose to make hierarchy unchangeable and select one of the following
> values.
> If exist instancename
> else if exist consistantId
>
> In cases with enabled persistent storage consistent id would be the same
> between node restarts, in in-memory cases you will be able to specify
> instanceName.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12920) Static hierarchy in jmx tree
[
https://issues.apache.org/jira/browse/IGNITE-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov updated IGNITE-12920:
Attachment: (was: image-2020-04-20-17-05-16-972.png)
> Static hierarchy in jmx tree
>
>
> Key: IGNITE-12920
> URL: https://issues.apache.org/jira/browse/IGNITE-12920
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Akkuratov
>Assignee: Igor Akkuratov
>Priority: Major
> Attachments: image-2020-04-20-17-05-36-451.png
>
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains
> classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader
> is been changing after node restart and monitoring systems rediscover new
> metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to
> create single monitoring template for different deployments. It can also make
> troubles if you want to start more then one ignite instance in single jvm. In
> this case you'll have to set {color:#1d1c1d}igniteInstanceName{color}
> property to add one more level with the name of this instance. It will affect
> jmx tree hierarchy as well.
> I propose to make hierarchy unchangeable and select one of the following
> values.
> If exist instancename
> else if exist consistantId
>
> In cases with enabled persistent storage consistent id would be the same
> between node restarts, in in-memory cases you will be able to specify
> instanceName.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12920) Static hierarchy in jmx tree
Igor Akkuratov created IGNITE-12920:
---
Summary: Static hierarchy in jmx tree
Key: IGNITE-12920
URL: https://issues.apache.org/jira/browse/IGNITE-12920
Project: Ignite
Issue Type: Improvement
Reporter: Igor Akkuratov
Assignee: Igor Akkuratov
Attachments: image-2020-04-20-17-05-16-972.png,
image-2020-04-20-17-05-36-451.png
Current jmx tree hierarchy depends on jvm and ignite options and by default
contains classloader.
!image-2020-04-20-17-05-36-451.png!
Monitoring systems like zabbix use bean path to discover metrics. In this case
classloader would be new after each node restart. If you'll disable classloader
with option {color:#1d1c1d}{color}
{code:java}
IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
{color:#1d1c1d}{color} the jmx tree would exclude one level. This behavior
excludes an opportunity to create single monitoring template for different
deployments. And make troubles if you want to start more then one ignite
instance in single jvm. In this case you should set
{color:#1d1c1d}igniteInstanceName{color} property to add one more level with
instance name. And it's also changes jmx tree hierarchy.
I offer to make hierarchy unchangeable and select one of the following values.
If exist instancename
else if exist consistantId
In persistent cases consistent id would be the same between node restarts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12889) checkRingLatency loops if there is only one server node with client in topology
[ https://issues.apache.org/jira/browse/IGNITE-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-12889: Description: If there is only one server node with any count of clients in topology call checkRingLatency loops until any server node join the topology. > checkRingLatency loops if there is only one server node with client in > topology > --- > > Key: IGNITE-12889 > URL: https://issues.apache.org/jira/browse/IGNITE-12889 > Project: Ignite > Issue Type: Bug >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Major > > If there is only one server node with any count of clients in topology call > checkRingLatency loops until any server node join the topology. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12889) checkRingLatency loops if there is only one server node with client in topology
Igor Akkuratov created IGNITE-12889: --- Summary: checkRingLatency loops if there is only one server node with client in topology Key: IGNITE-12889 URL: https://issues.apache.org/jira/browse/IGNITE-12889 Project: Ignite Issue Type: Bug Reporter: Igor Akkuratov Assignee: Igor Akkuratov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11282) NullPointerException if transaction enabled and using byte[] for key/value
[
https://issues.apache.org/jira/browse/IGNITE-11282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998262#comment-16998262
]
Igor Akkuratov commented on IGNITE-11282:
-
Resolved with https://issues.apache.org/jira/browse/IGNITE-12116
> NullPointerException if transaction enabled and using byte[] for key/value
> --
>
> Key: IGNITE-11282
> URL: https://issues.apache.org/jira/browse/IGNITE-11282
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Courtney
>Assignee: Igor Akkuratov
>Priority: Blocker
> Attachments: Screen Shot 2019-02-10 at 15.02.19.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> I have debugged this and found the problem is because of hashCode comparison
> failure. You can see in the screenshot below.
> {code:java}
> txMap == null ? null : txMap.get(key)
> {code}
> this will fail to get the entry but they the key is in fact in the map, it's
> the only entry and if a proper array comparison is done e.g. using
> `Arrays.equals` as shown in the eval window then the key would match. !Screen
> Shot 2019-02-10 at 15.02.19.png!
> If running without `-ea` then the exception is
> {code:java}
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> io.hypi.arc.ignite.ArcIgniteUtils.lambda$asFuture$f0cf812f$1(ArcIgniteUtils.java:21)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:300)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:287)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.ja
[jira] [Updated] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-11091: Description: It's possible to create indexes with same name but in different cases using SqlFieldsQuery, but visor shows all indexes in upper case. So it's impossible to select which one you need. (was: Visor shows all indexes in upper case) > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > > It's possible to create indexes with same name but in different cases using > SqlFieldsQuery, but visor shows all indexes in upper case. So it's impossible > to select which one you need. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-11091: Description: Visor shows all indexes in upper case > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > > Visor shows all indexes in upper case -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11282) NullPointerException if transaction enabled and using byte[] for key/value
[
https://issues.apache.org/jira/browse/IGNITE-11282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov reassigned IGNITE-11282:
---
Assignee: Igor Akkuratov
> NullPointerException if transaction enabled and using byte[] for key/value
> --
>
> Key: IGNITE-11282
> URL: https://issues.apache.org/jira/browse/IGNITE-11282
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Courtney
>Assignee: Igor Akkuratov
>Priority: Blocker
> Attachments: Screen Shot 2019-02-10 at 15.02.19.png
>
>
> I have debugged this and found the problem is because of hashCode comparison
> failure. You can see in the screenshot below.
> {code:java}
> txMap == null ? null : txMap.get(key)
> {code}
> this will fail to get the entry but they the key is in fact in the map, it's
> the only entry and if a proper array comparison is done e.g. using
> `Arrays.equals` as shown in the eval window then the key would match. !Screen
> Shot 2019-02-10 at 15.02.19.png!
> If running without `-ea` then the exception is
> {code:java}
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> io.hypi.arc.ignite.ArcIgniteUtils.lambda$asFuture$f0cf812f$1(ArcIgniteUtils.java:21)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:300)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:287)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> org.apache.igni
[jira] [Commented] (IGNITE-11112) control.sh incorrect work with the key '--force'.
[
https://issues.apache.org/jira/browse/IGNITE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754700#comment-16754700
]
Igor Akkuratov commented on IGNITE-2:
-
"-force" option was used instead of "–force". That has been interpreted as
consistent id. After that empty response was returned.
> control.sh incorrect work with the key '--force'.
> -
>
> Key: IGNITE-2
> URL: https://issues.apache.org/jira/browse/IGNITE-2
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrey Kalinin
>Priority: Major
>
> control.sh --wal delete with the key --force produces the error
> control.sh --host --wal delete --force
> {code:java}
> Control utility [ver. 2.5.1-p142#20181016-sha1:f983e74f]
> 2018 Copyright(C) Apache Software Foundation
> User: ***
>
> Warning: the command will delete unused WAL segments.
> Press 'y' to continue . . . Error: Task map operation produced no mapped
> jobs: GridTaskSessionImpl
> [taskName=org.apache.ignite.internal.visor.misc.VisorWalTask,
> dep=GridDeployment [...]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:528)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:764)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:489)
> at
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:227)
> at
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsync(GridTaskCommandHandler.java:163)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:318)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:99)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:174)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11091) Visor shows all indexes in upper case
Igor Akkuratov created IGNITE-11091: --- Summary: Visor shows all indexes in upper case Key: IGNITE-11091 URL: https://issues.apache.org/jira/browse/IGNITE-11091 Project: Ignite Issue Type: Task Components: cache Affects Versions: 2.7, 2.6, 2.5 Reporter: Igor Akkuratov Assignee: Igor Akkuratov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
