[jira] [Updated] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12756:
Fix Version/s: 2.8.1
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056177#comment-17056177
]
Andrey N. Gura commented on IGNITE-12756:
-
Merged to master branch.
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura resolved IGNITE-12756.
-
Resolution: Fixed
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12756) TcpCommunicationSpi metrics implementation improvements
[
https://issues.apache.org/jira/browse/IGNITE-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056155#comment-17056155
]
Ignite TC Bot commented on IGNITE-12756:
{panel:title=Branch: [pull/7500/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5105188buildTypeId=IgniteTests24Java8_RunAll]
> TcpCommunicationSpi metrics implementation improvements
>
>
> Key: IGNITE-12756
> URL: https://issues.apache.org/jira/browse/IGNITE-12756
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implementation of IGNITE-12682 allows now to create sent/received counters by
> message direct type statically during SPI initialization. Data structure for
> this counters does have any contention so we can remove thread local
> HashMap's for this counters. As result we will also reduce memory footprint
> (we can use IntHashMap which is more memory effective and we will have only
> one map instance instead of map per thread).
> Also there is a couple of problems which could be solved during
> implementation this issue:
> - SPI uses internal API while we should extend IgniteSpiContext that will
> provide access to the {{GridMEtricManager}} functionality.
> - {{MetricManagerResource}} annotation is redundant and has only one usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12769) MetricRegistryMBean and OpenCensusExporterSpi have memory leak
Andrey N. Gura created IGNITE-12769:
---
Summary: MetricRegistryMBean and OpenCensusExporterSpi have memory
leak
Key: IGNITE-12769
URL: https://issues.apache.org/jira/browse/IGNITE-12769
Project: Ignite
Issue Type: Bug
Reporter: Andrey N. Gura
{{MetricRegistryMBean}} and {{OpenCensusExporterSpi}} have memory leak.
To the following maps values add but never remove (i.e. on remove corresponding
histogram or on change histogram buckets layout):
* {{MetricRegistryMBean.histogramNames}}
* {{OpenCensusMetricExporterSpi.histogramNames}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12769) MetricRegistryMBean and OpenCensusExporterSpi have memory leak
[
https://issues.apache.org/jira/browse/IGNITE-12769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12769:
Fix Version/s: 2.8.1
> MetricRegistryMBean and OpenCensusExporterSpi have memory leak
> --
>
> Key: IGNITE-12769
> URL: https://issues.apache.org/jira/browse/IGNITE-12769
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey N. Gura
>Priority: Major
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} and {{OpenCensusExporterSpi}} have memory leak.
> To the following maps values add but never remove (i.e. on remove
> corresponding histogram or on change histogram buckets layout):
> * {{MetricRegistryMBean.histogramNames}}
> * {{OpenCensusMetricExporterSpi.histogramNames}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12745) Compute job system view
[ https://issues.apache.org/jira/browse/IGNITE-12745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12745: - Fix Version/s: (was: 2.9) 2.8.1 > Compute job system view > --- > > Key: IGNITE-12745 > URL: https://issues.apache.org/jira/browse/IGNITE-12745 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8.1 > > Time Spent: 3.5h > Remaining Estimate: 0h > > ComputeTaskView shows compute tasks that was started(initiated) on the local > node. > We need to introduce another view that will show compute jobs - jobs that > executing on the local node but was initiated on some remote node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12768) MetricRegistryMBean doesn't show histogram values in case when histogram name contains underscore character
[
https://issues.apache.org/jira/browse/IGNITE-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12768:
Description:
{{MetricRegistryMBean}} doesn't show histogram values in case when histogram
name contains underscore character.
The problem in {{MetricRegistryMBean.searchHistogram()}} method which relies on
first underscore character in the fully qualified metric name. This method also
use relatively old and not effective API for string parsing (this API
implementation is synchronized). It should be replaced by simple
{{String.lastIndexOf()}} for example.
Reproducer:
{code:java}
package org.apache.ignite.spi.metric.jmx;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteException;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.processors.metric.MetricRegistry;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.junit.Test;
import javax.management.*;
import java.lang.management.ManagementFactory;
public class MetricRegistryMBeanTest extends GridCommonAbstractTest {
private static final String REGISTRY_NAME = "test_registry";
private static final String VALID_HISTOGRAM_NAME = "testhist";
private static final String INVALID_HISTOGRAM_NAME = "test_hist";
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
JmxMetricExporterSpi exporterSpi = new JmxMetricExporterSpi();
cfg.setMetricExporterSpi(exporterSpi);
return cfg;
}
@Test public void testBean() throws Exception {
Ignite ignite = startGrid();
MetricRegistry reg =
((IgniteEx)ignite).context().metric().registry(REGISTRY_NAME);
reg.histogram(VALID_HISTOGRAM_NAME, new long[] {10, 100}, null);
reg.histogram(INVALID_HISTOGRAM_NAME, new long[] {10, 100}, null);
assertNotNull(mbean(ignite).getAttribute(VALID_HISTOGRAM_NAME + '_' +
10 + '_' + 100));
assertEquals(0L, mbean(ignite).getAttribute(VALID_HISTOGRAM_NAME + '_'
+ 10 + '_' + 100));
assertNotNull(mbean(ignite).getAttribute(INVALID_HISTOGRAM_NAME + '_' +
10 + '_' + 100));
assertEquals(0L, mbean(ignite).getAttribute(INVALID_HISTOGRAM_NAME +
'_' + 10 + '_' + 100));
}
private static DynamicMBean mbean(Ignite ignite) {
try {
ObjectName mbeanName = U.makeMBeanName(ignite.name(), null,
REGISTRY_NAME);
MBeanServer mbeanSrv = ManagementFactory.getPlatformMBeanServer();
if (!mbeanSrv.isRegistered(mbeanName))
fail("MBean is not registered: " +
mbeanName.getCanonicalName());
return MBeanServerInvocationHandler.newProxyInstance(mbeanSrv,
mbeanName, DynamicMBean.class, false);
} catch (MalformedObjectNameException e) {
throw new IgniteException(e);
}
}
}
{code}
was:
{{MetricRegistryMBean}} doesn't show histogram values in case when histogram
name contains underscore character.
The problem in {{MetricRegistryMBean.searchHistogram()}} method which relies on
first underscore character in the fully qualified metric name. This method also
use relatively old and not effective API for string parsing (this API
implementation is synchronized). It should be replaced by simple
{{String.lastIndexOf()}} for example.
> MetricRegistryMBean doesn't show histogram values in case when histogram name
> contains underscore character
> ---
>
> Key: IGNITE-12768
> URL: https://issues.apache.org/jira/browse/IGNITE-12768
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} doesn't show histogram values in case when histogram
> name contains underscore character.
> The problem in {{MetricRegistryMBean.searchHistogram()}} method which relies
> on first underscore character in the fully qualified metric name. This method
> also use relatively old and not effective API for string parsing (this API
> implementation is synchronized). It should be replaced by simple
> {{String.lastIndexOf()}} for example.
> Reproducer:
> {code:java}
> package org.apache.ignite.spi.metric.jmx;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.processors.metric.MetricRegistry;
> import
[jira] [Updated] (IGNITE-12768) MetricRegistryMBean doesn't show histogram values in case when histogram name contains underscore character
[
https://issues.apache.org/jira/browse/IGNITE-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12768:
Labels: IEP-35 (was: )
> MetricRegistryMBean doesn't show histogram values in case when histogram name
> contains underscore character
> ---
>
> Key: IGNITE-12768
> URL: https://issues.apache.org/jira/browse/IGNITE-12768
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} doesn't show histogram values in case when histogram
> name contains underscore character.
> The problem in {{MetricRegistryMBean.searchHistogram()}} method which relies
> on first underscore character in the fully qualified metric name. This method
> also use relatively old and not effective API for string parsing (this API
> implementation is synchronized). It should be replaced by simple
> {{String.lastIndexOf()}} for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12768) MetricRegistryMBean doesn't show histogram values in case when histogram name contains underscore character
Andrey N. Gura created IGNITE-12768:
---
Summary: MetricRegistryMBean doesn't show histogram values in case
when histogram name contains underscore character
Key: IGNITE-12768
URL: https://issues.apache.org/jira/browse/IGNITE-12768
Project: Ignite
Issue Type: Bug
Reporter: Andrey N. Gura
Fix For: 2.8.1
{{MetricRegistryMBean}} doesn't show histogram values in case when histogram
name contains underscore character.
The problem in {{MetricRegistryMBean.searchHistogram()}} method which relies on
first underscore character in the fully qualified metric name. This method also
use relatively old and not effective API for string parsing (this API
implementation is synchronized). It should be replaced by simple
{{String.lastIndexOf()}} for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12763) OpenCensus integration example.
[ https://issues.apache.org/jira/browse/IGNITE-12763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056120#comment-17056120 ] Nikolay Izhikov commented on IGNITE-12763: -- Example tests - https://ci.ignite.apache.org/viewLog.html?buildId=5114609=queuedBuildOverviewTab > OpenCensus integration example. > --- > > Key: IGNITE-12763 > URL: https://issues.apache.org/jira/browse/IGNITE-12763 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We should provide to the user simple self-explaining example of the > integration with the opencensus. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12767) MetricRegistryMBean is not thread safe
[
https://issues.apache.org/jira/browse/IGNITE-12767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12767:
Issue Type: Bug (was: Improvement)
> MetricRegistryMBean is not thread safe
> --
>
> Key: IGNITE-12767
> URL: https://issues.apache.org/jira/browse/IGNITE-12767
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} is not thread safe due to usage of {{histogramNames}}
> instance of {{HashMap}} class. Changing {{HashMap}} to {{ConcurrentHashMap}}
> will not help a lot (likely) because method
> {{MetricUtils.histogramBucketNames()}} uses just {{put}} method
> ({{putIfAbsent}} will help I believe).
> {{OpenCensusExporterSpi}} uses the same
> {{MetricUtils.histogramBucketNames()}} method. But it isn't issue for this
> exporter because it is single threaded.
> Also {{MetricUtils.histogramBucketNames()}} method is responsible for
> histogram bucket's name representation. I believe that it is responsibility
> of metric exporter and this method should be removed from {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12767) MetricRegistryMBean is not thread safe
[
https://issues.apache.org/jira/browse/IGNITE-12767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12767:
Summary: MetricRegistryMBean is not thread safe (was: MetricRegistryMBean
is not hread safe)
> MetricRegistryMBean is not thread safe
> --
>
> Key: IGNITE-12767
> URL: https://issues.apache.org/jira/browse/IGNITE-12767
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} is not thread safe due to usage of {{histogramNames}}
> instance of {{HashMap}} class. Changing {{HashMap}} to {{ConcurrentHashMap}}
> will not help a lot (likely) because method
> {{MetricUtils.histogramBucketNames()}} uses just {{put}} method
> ({{putIfAbsent}} will help I believe).
> {{OpenCensusExporterSpi}} uses the same
> {{MetricUtils.histogramBucketNames()}} method. But it isn't issue for this
> exporter because it is single threaded.
> Also {{MetricUtils.histogramBucketNames()}} method is responsible for
> histogram bucket's name representation. I believe that it is responsibility
> of metric exporter and this method should be removed from {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12767) MetricRegistryMBean is not hread safe
[
https://issues.apache.org/jira/browse/IGNITE-12767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12767:
Labels: IEP-35 (was: )
> MetricRegistryMBean is not hread safe
> -
>
> Key: IGNITE-12767
> URL: https://issues.apache.org/jira/browse/IGNITE-12767
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} is not thread safe due to usage of {{histogramNames}}
> instance of {{HashMap}} class. Changing {{HashMap}} to {{ConcurrentHashMap}}
> will not help a lot (likely) because method
> {{MetricUtils.histogramBucketNames()}} uses just {{put}} method
> ({{putIfAbsent}} will help I believe).
> {{OpenCensusExporterSpi}} uses the same
> {{MetricUtils.histogramBucketNames()}} method. But it isn't issue for this
> exporter because it is single threaded.
> Also {{MetricUtils.histogramBucketNames()}} method is responsible for
> histogram bucket's name representation. I believe that it is responsibility
> of metric exporter and this method should be removed from {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12767) MetricRegistryMBean is not hread safe
Andrey N. Gura created IGNITE-12767:
---
Summary: MetricRegistryMBean is not hread safe
Key: IGNITE-12767
URL: https://issues.apache.org/jira/browse/IGNITE-12767
Project: Ignite
Issue Type: Improvement
Reporter: Andrey N. Gura
Fix For: 2.8.1
{{MetricRegistryMBean}} is not thread safe due to usage of {{histogramNames}}
instance of {{HashMap}} class. Changing {{HashMap}} to {{ConcurrentHashMap}}
will not help a lot (likely) because method
{{MetricUtils.histogramBucketNames()}} uses just {{put}} method
({{putIfAbsent}} will help I believe).
{{OpenCensusExporterSpi}} uses the same {{MetricUtils.histogramBucketNames()}}
method. But it isn't issue for this exporter because it is single threaded.
Also {{MetricUtils.histogramBucketNames()}} method is responsible for histogram
bucket's name representation. I believe that it is responsibility of metric
exporter and this method should be removed from {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12767) MetricRegistryMBean is not hread safe
[
https://issues.apache.org/jira/browse/IGNITE-12767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-12767:
Ignite Flags: (was: Docs Required,Release Notes Required)
> MetricRegistryMBean is not hread safe
> -
>
> Key: IGNITE-12767
> URL: https://issues.apache.org/jira/browse/IGNITE-12767
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Priority: Major
> Fix For: 2.8.1
>
>
> {{MetricRegistryMBean}} is not thread safe due to usage of {{histogramNames}}
> instance of {{HashMap}} class. Changing {{HashMap}} to {{ConcurrentHashMap}}
> will not help a lot (likely) because method
> {{MetricUtils.histogramBucketNames()}} uses just {{put}} method
> ({{putIfAbsent}} will help I believe).
> {{OpenCensusExporterSpi}} uses the same
> {{MetricUtils.histogramBucketNames()}} method. But it isn't issue for this
> exporter because it is single threaded.
> Also {{MetricUtils.histogramBucketNames()}} method is responsible for
> histogram bucket's name representation. I believe that it is responsibility
> of metric exporter and this method should be removed from {{MetricUtils}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12656) Cleanup GridCacheProcessor from functionality not related to its responsibility
[ https://issues.apache.org/jira/browse/IGNITE-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056065#comment-17056065 ] Vyacheslav Koptilin commented on IGNITE-12656: -- Hello [~langj], I have created IGNITE-12766 in order to fix the issue you mentioned. > Cleanup GridCacheProcessor from functionality not related to its > responsibility > --- > > Key: IGNITE-12656 > URL: https://issues.apache.org/jira/browse/IGNITE-12656 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, we have a couple of functionality in GridCacheProcessor not > directly related to its responsibility, like: > * initQueryStructuresForNotStartedCache > * addRemovedItemsCleanupTask > * setTxOwnerDumpRequestsAllowed > * longTransactionTimeDumpThreshold > * transactionTimeDumpSamplesCoefficient > * longTransactionTimeDumpSamplesPerSecondLimit > * broadcastToNodesSupportingFeature > * LocalAffinityFunction > * RemovedItemsCleanupTask > * TxTimeoutOnPartitionMapExchangeChangeFuture > * enableRebalance > We need to move them to the right places and make GridCacheProcessor code > cleaner. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12766) Node startup can be broken in case of using Local cache with persistence enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-12766:
-
Description:
Trying to upgrade from the previous version of Apache Ignite (AI 2.7.6 for
example) may result in the following exception when Local cache is used and
persistence enabled.
{code}
[2020-03-05 16:47:39,222][ERROR][main][IgniteKernal] Exception during start
processors, node will be stopped and close connections[2020-03-05
16:47:39,222][ERROR][main][IgniteKernal] Exception during start processors,
node will be stopped and close connectionsclass
org.apache.ignite.IgniteCheckedException: An error occurred during cache
configuration loading from file [file=...] at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:965)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:907)
at
org.apache.ignite.internal.processors.cache.GridLocalConfigManager.restoreCaches(GridLocalConfigManager.java:171)
at
org.apache.ignite.internal.processors.cache.GridLocalConfigManager.restoreCacheConfigurations(GridLocalConfigManager.java:124)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5198)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:488)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:824)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:5378)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1286) at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2054)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1704)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117) at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1035)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:921) at
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:820) at
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:690) at
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:659) at
org.apache.ignite.Ignition.start(Ignition.java:346) at
org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:38)Caused
by: class org.apache.ignite.IgniteCheckedException: Failed to find class with
given class loader for unmarshalling (make sure same versions of all classes
are available on all nodes or enable peer-class-loading)
[clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
cls=org.apache.ignite.internal.processors.cache.GridCacheProcessor$LocalAffinityFunction]
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:129)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:961)
... 18 moreCaused by: java.lang.ClassNotFoundException:
org.apache.ignite.internal.processors.cache.GridCacheProcessor$LocalAffinityFunction
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at
java.lang.ClassLoader.loadClass(ClassLoader.java:424) at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) at
java.lang.ClassLoader.loadClass(ClassLoader.java:357) at
java.lang.Class.forName0(Native Method) at
java.lang.Class.forName(Class.java:348) at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8870) at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:59)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1826) at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2000) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2245) at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2169) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2027) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2245) at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2169) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2027) at
[jira] [Created] (IGNITE-12766) Node startup can be broken in case of using Local cache with persistence enabled.
Vyacheslav Koptilin created IGNITE-12766:
Summary: Node startup can be broken in case of using Local cache
with persistence enabled.
Key: IGNITE-12766
URL: https://issues.apache.org/jira/browse/IGNITE-12766
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin
Fix For: 2.9
Trying to upgrade from the previous version of Apache Ignite (AI 2.7.6 for
example) may result in the following exception when Local cache is used and
persistence enabled.
{noformat}
[2020-03-05 16:47:39,222][ERROR][main][IgniteKernal] Exception during start
processors, node will be stopped and close connections[2020-03-05
16:47:39,222][ERROR][main][IgniteKernal] Exception during start processors,
node will be stopped and close connectionsclass
org.apache.ignite.IgniteCheckedException: An error occurred during cache
configuration loading from file [file=...] at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:965)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:907)
at
org.apache.ignite.internal.processors.cache.GridLocalConfigManager.restoreCaches(GridLocalConfigManager.java:171)
at
org.apache.ignite.internal.processors.cache.GridLocalConfigManager.restoreCacheConfigurations(GridLocalConfigManager.java:124)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5198)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:488)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:824)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:5378)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1286) at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2054)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1704)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117) at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1035)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:921) at
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:820) at
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:690) at
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:659) at
org.apache.ignite.Ignition.start(Ignition.java:346) at
org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:38)Caused
by: class org.apache.ignite.IgniteCheckedException: Failed to find class with
given class loader for unmarshalling (make sure same versions of all classes
are available on all nodes or enable peer-class-loading)
[clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
cls=org.apache.ignite.internal.processors.cache.GridCacheProcessor$LocalAffinityFunction]
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:129)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:961)
... 18 moreCaused by: java.lang.ClassNotFoundException:
org.apache.ignite.internal.processors.cache.GridCacheProcessor$LocalAffinityFunction
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at
java.lang.ClassLoader.loadClass(ClassLoader.java:424) at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) at
java.lang.ClassLoader.loadClass(ClassLoader.java:357) at
java.lang.Class.forName0(Native Method) at
java.lang.Class.forName(Class.java:348) at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8870) at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:59)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1826) at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2000) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2245) at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2169) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2027) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at
[jira] [Commented] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056046#comment-17056046 ] Maxim Muzafarov commented on IGNITE-12450: -- The issue reopened and must be cherry-picked to 2.8.1 release branch. > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8.1 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12765) Slim binary release and docker image for Apache Ignite
[
https://issues.apache.org/jira/browse/IGNITE-12765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12765:
-
Description:
1. Prepare Apache Ignite "slim" distribution (example:
https://github.com/apache/ignite/tree/ignite-slim)
2. Update configuration and check Apache Ignite RELEASE TeamCity Suite
according to a new additional package distribution.
See - discussion on dev-list
http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html
{code}
libs:
core/shmem/jcache
ignite-indexing
ignite-spring
libs/optional:
ignite-compress
ignite-rest-http
ignite-spring-data_2.2
ignite-log4j2
ignite-log4j
ignite-slf4j
ignite-opencensus
ignite-kubernetes
ignite-urideploy
ignite-jta
{code}
was:
1. Prepare Apache Ignite "slim" distribution (example:
https://github.com/apache/ignite/tree/ignite-slim)
2. Update configuration and check Apache Ignite RELEASE TeamCity Suite
according to a new additional package distribution.
See - discussion on dev-list
http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html
{code}
libs:
core/shmem/jcache
ignite-indexing
ignite-spring
libs/optional:
ignite-compress
ignite-kubernetes
ignite-log4j2
ignite-rest-http
ignite-spring-data_2.2
ignite-jta ignite-log4j ignite-opencensus ignite-slf4j
ignite-urideploy
* ignite-core
* ignite-indexing
* ignite-rest-http
* ignite-spring
* ignite-log4j
* ignite-log4j2
* ignite-slf4j
* ignite-urideploy
* ignite-kubernetes
* ignite-opencensus
{code}
> Slim binary release and docker image for Apache Ignite
> --
>
> Key: IGNITE-12765
> URL: https://issues.apache.org/jira/browse/IGNITE-12765
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Priority: Blocker
> Fix For: 2.8.1
>
>
> 1. Prepare Apache Ignite "slim" distribution (example:
> https://github.com/apache/ignite/tree/ignite-slim)
> 2. Update configuration and check Apache Ignite RELEASE TeamCity Suite
> according to a new additional package distribution.
> See - discussion on dev-list
> http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html
> {code}
> libs:
> core/shmem/jcache
> ignite-indexing
> ignite-spring
> libs/optional:
> ignite-compress
> ignite-rest-http
> ignite-spring-data_2.2
> ignite-log4j2
> ignite-log4j
> ignite-slf4j
> ignite-opencensus
> ignite-kubernetes
> ignite-urideploy
> ignite-jta
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12765) Slim binary release and docker image for Apache Ignite
Maxim Muzafarov created IGNITE-12765:
Summary: Slim binary release and docker image for Apache Ignite
Key: IGNITE-12765
URL: https://issues.apache.org/jira/browse/IGNITE-12765
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Fix For: 2.8.1
1. Prepare Apache Ignite "slim" distribution (example:
https://github.com/apache/ignite/tree/ignite-slim)
2. Update configuration and check Apache Ignite RELEASE TeamCity Suite
according to a new additional package distribution.
See - discussion on dev-list
http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html
{code}
libs:
core/shmem/jcache
ignite-indexing
ignite-spring
libs/optional:
ignite-compress
ignite-kubernetes
ignite-log4j2
ignite-rest-http
ignite-spring-data_2.2
ignite-jta ignite-log4j ignite-opencensus ignite-slf4j
ignite-urideploy
* ignite-core
* ignite-indexing
* ignite-rest-http
* ignite-spring
* ignite-log4j
* ignite-log4j2
* ignite-slf4j
* ignite-urideploy
* ignite-kubernetes
* ignite-opencensus
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12759) Getting a SecurityContext from GridSecurityProcessor
[ https://issues.apache.org/jira/browse/IGNITE-12759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-12759: - Description: Extend the _GridSecurityProcessor_ interface by adding _securityContext(UUID subjId)_ method and use this method to get the actual security context. (was: 1. Extend the _GridSecurityProcessor_ interface by adding _securityContext(UUID subjId)_ method and use this method to get the actual security context. 2. In the case when _GridSecurityProcessor_ cannot get a security context, we should return _the unknown security context_. All operations are forbidden with _the unknown security context_.) > Getting a SecurityContext from GridSecurityProcessor > > > Key: IGNITE-12759 > URL: https://issues.apache.org/jira/browse/IGNITE-12759 > Project: Ignite > Issue Type: Improvement > Components: security >Affects Versions: 2.8 >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-41 > > Extend the _GridSecurityProcessor_ interface by adding _securityContext(UUID > subjId)_ method and use this method to get the actual security context. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reopened IGNITE-12450: -- > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8.1 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12450: - Priority: Blocker (was: Major) > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Blocker > Labels: IEP-35 > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12450: - Fix Version/s: (was: 2.9) 2.8.1 > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8.1 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12764: - Priority: Blocker (was: Critical) > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Blocker > Fix For: 2.8.1 > > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12764: - Ignite Flags: (was: Release Notes Required) > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Blocker > Fix For: 2.8.1 > > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12764: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Blocker > Fix For: 2.8.1 > > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12450: - Fix Version/s: (was: 2.8) 2.9 > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35 > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056019#comment-17056019 ] Maxim Muzafarov commented on IGNITE-12450: -- [~NSAmelchev][~nizhikov] Folks, I've changed FixVersion to 2.9 since this commit haven't been cherry-picked to 2.8 > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35 > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12764: - Priority: Critical (was: Major) > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Critical > Fix For: 2.8.1 > > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12764: - Fix Version/s: 2.8.1 > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > Fix For: 2.8.1 > > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12764: - Component/s: sql > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ilya Kasnacheev >Priority: Major > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056014#comment-17056014 ] Ilya Kasnacheev commented on IGNITE-12764: -- Please see userlist post and related runnable reproducer. > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Critical > Fix For: 2.8.1 > > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12764: - Affects Version/s: 2.8 > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12764: - Attachment: SqlMain.java > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Kasnacheev >Priority: Major > Attachments: SqlMain.java > > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
Ilya Kasnacheev created IGNITE-12764: Summary: Regression: Thin JDBC streaming fails/BatchUpdateException if function is used Key: IGNITE-12764 URL: https://issues.apache.org/jira/browse/IGNITE-12764 Project: Ignite Issue Type: Bug Reporter: Ilya Kasnacheev insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) happily worked in 2.7.6 but will fail on 2.8.0 with: Exception in thread "main" java.sql.BatchUpdateException: class org.apache.ignite.IgniteCheckedException: null at org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) at java.base/java.lang.Thread.run(Thread.java:834) Suspected reason is that function RANDOM_UUID() is not processed correctly here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12745) Compute job system view
[
https://issues.apache.org/jira/browse/IGNITE-12745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056001#comment-17056001
]
Ignite TC Bot commented on IGNITE-12745:
{panel:title=Branch: [pull/7495/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5113565buildTypeId=IgniteTests24Java8_RunAll]
> Compute job system view
> ---
>
> Key: IGNITE-12745
> URL: https://issues.apache.org/jira/browse/IGNITE-12745
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.7.6
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
> Fix For: 2.9
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> ComputeTaskView shows compute tasks that was started(initiated) on the local
> node.
> We need to introduce another view that will show compute jobs - jobs that
> executing on the local node but was initiated on some remote node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12763) OpenCensus integration example.
[ https://issues.apache.org/jira/browse/IGNITE-12763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-12763: Assignee: Nikolay Izhikov > OpenCensus integration example. > --- > > Key: IGNITE-12763 > URL: https://issues.apache.org/jira/browse/IGNITE-12763 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > > We should provide to the user simple self-explaining example of the > integration with the opencensus. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12763) OpenCensus integration example.
Nikolay Izhikov created IGNITE-12763: Summary: OpenCensus integration example. Key: IGNITE-12763 URL: https://issues.apache.org/jira/browse/IGNITE-12763 Project: Ignite Issue Type: Sub-task Reporter: Nikolay Izhikov We should provide to the user simple self-explaining example of the integration with the opencensus. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12467) Python Thin Client Support for Transactions
[ https://issues.apache.org/jira/browse/IGNITE-12467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12467: --- Labels: iep-34 (was: ) > Python Thin Client Support for Transactions > --- > > Key: IGNITE-12467 > URL: https://issues.apache.org/jira/browse/IGNITE-12467 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7.6 >Reporter: Robert Emanuele >Priority: Major > Labels: iep-34 > > I see that https://issues.apache.org/jira/browse/IGNITE-9410 is marked as > resolved but I have not seen the changes in the python thin client, pyignite. > Am I looking in the wrong place > ([https://github.com/apache/ignite/tree/master/modules/platforms/python]), or > is there more work to do? > If there is more work, are there changes that I can port? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12762) PHP: Thin client: Transactions
[ https://issues.apache.org/jira/browse/IGNITE-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12762: --- Labels: PHP iep-34 (was: PHP) > PHP: Thin client: Transactions > -- > > Key: IGNITE-12762 > URL: https://issues.apache.org/jira/browse/IGNITE-12762 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexander Kovalev >Priority: Blocker > Labels: PHP, iep-34 > > dear colleagues, could you explain when in > [https://apacheignite.readme.io/docs/php-thin-client] > transaction support will be enabled? > I found an implementation for other languages, but support is needed > specifically for PHP > > I'd like to have a link from this issue to > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055970#comment-17055970 ] Artem Budnikov commented on IGNITE-12408: - > Do we have the ability to copy pages for new metrics and system view from > 2.7.6 to 2.8 docs? Yes, I'll do it when we finish working on the docs. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055968#comment-17055968 ] Nikolay Izhikov commented on IGNITE-12408: -- [~Artem Budnikov] I created 3 new system view pages. https://apacheignite.readme.io/docs/node_attributes https://apacheignite.readme.io/docs/baseline_nodes https://apacheignite.readme.io/docs/node_metrics It seems changes in 2.7.6 documentation don't propagated to the new 2.8.0 docs. Do we have the ability to copy pages for new metrics and system view from 2.7.6 to 2.8 docs? > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12762) PHP: Thin client: Transactions
[ https://issues.apache.org/jira/browse/IGNITE-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kovalev updated IGNITE-12762: --- Description: dear colleagues, could you explain when in [https://apacheignite.readme.io/docs/php-thin-client] transaction support will be enabled? I found an implementation for other languages, but support is needed specifically for PHP I'd like to have a link from this issue to [https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support] was: dear colleagues, could you explain when in https://apacheignite.readme.io/docs/php-thin-client transaction support will be enabled? I found an implementation for other languages, but support is needed specifically for PHP > PHP: Thin client: Transactions > -- > > Key: IGNITE-12762 > URL: https://issues.apache.org/jira/browse/IGNITE-12762 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexander Kovalev >Priority: Blocker > Labels: PHP > > dear colleagues, could you explain when in > [https://apacheignite.readme.io/docs/php-thin-client] > transaction support will be enabled? > I found an implementation for other languages, but support is needed > specifically for PHP > > I'd like to have a link from this issue to > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12762) PHP: Thin client: Transactions
Alexander Kovalev created IGNITE-12762: -- Summary: PHP: Thin client: Transactions Key: IGNITE-12762 URL: https://issues.apache.org/jira/browse/IGNITE-12762 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Alexander Kovalev dear colleagues, could you explain when in https://apacheignite.readme.io/docs/php-thin-client transaction support will be enabled? I found an implementation for other languages, but support is needed specifically for PHP -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055899#comment-17055899 ] Nikolay Izhikov commented on IGNITE-12408: -- [~Artem Budnikov] It seems, I doesn't have the permissions to edit those pages. I will create a copy of it, please, remove legacy pages after it. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12761) Add ability to disable check crc sums of stored pages due to invalidate_indexes.
Philipp Masharov created IGNITE-12761: - Summary: Add ability to disable check crc sums of stored pages due to invalidate_indexes. Key: IGNITE-12761 URL: https://issues.apache.org/jira/browse/IGNITE-12761 Project: Ignite Issue Type: Bug Reporter: Philipp Masharov Assignee: Philipp Masharov Add additional param to validate_indexes command org.apache.ignite.internal.commandline.cache.CacheSubcommands#VALIDATE_INDEXES*like here: org.apache.ignite.internal.commandline.cache.argument.IdleVerifyCommandArg#CHECK_CRC now by default this check is always enabled, need to be configurable like the same one in IdleVerifyCommandArg -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055876#comment-17055876 ] Artem Budnikov commented on IGNITE-12408: - [~nizhikov] I agree, please move the existing system views page, if you don't mind. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin reassigned IGNITE-12757: Assignee: Nikolai Kulagin > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Blocker > Fix For: 2.8.1 > > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12760) Prevent AssertionError on message unmarshalling, when classLoaderId contains id of node that already left
Denis Chudov created IGNITE-12760:
-
Summary: Prevent AssertionError on message unmarshalling, when
classLoaderId contains id of node that already left
Key: IGNITE-12760
URL: https://issues.apache.org/jira/browse/IGNITE-12760
Project: Ignite
Issue Type: Bug
Reporter: Denis Chudov
Assignee: Denis Chudov
Following assertion error triggers failure handler and crashes the node. Can
possibly crash the whole cluster.
{code:java}
2020-02-18
14:34:09.775\[ERROR]\[query-#146129%DPL_GRID%DplGridNodeName%]\[o.a.i.i.p.cache.GridCacheIoManager]
Failed to process message \[senderId=727757ed-4ad4-4779-bda9-081525725cce,
msg=GridCacheQueryRequest \[id=178,
cacheName=com.sbt.tokenization.data.entity.KEKEntity_DPL_union-module,
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null,
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false,
incMeta=false, all=false, keepBinary=true,
subjId=727757ed-4ad4-4779-bda9-081525725cce, taskHash=0, part=-1,
topVer=AffinityTopologyVersion \[topVer=97, minorTopVer=0], sendTimestamp=-1,
receiveTimestamp=-1, super=GridCacheIdMessage \[cacheId=-1129073400,
super=GridCacheMessage \[msgId=179, depInfo=GridDeploymentInfoBean
\[clsLdrId=c32670e3071-d30ee64b-0833-45d4-abbe-fb6282669caa, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
lastAffChangedTopVer=AffinityTopologyVersion \[topVer=8, minorTopVer=6],
err=null, skipPrepare=false
java.lang.AssertionError: null
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1576)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:584)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:102)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:301)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1565)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4300(GridIoManager.java:130)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1092)
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}
There is no fair reproducer for now, but it seems that we should prevent such
situation in general like following:
1) check the correctness of the message before it will be sent - inside of
GridCacheDeploymentManager#prepare. If we have the corresponding class loader
on local node, we can try to fix message and replace wrong class loader with
local one.
2) log suspicious deployments which we receive from
GridDeploymentManager#deploy - maybe we have obsolete deployments in caches.
3) possibly we can remove this assertion, we should have this class on sender
node and use it as class loader id, and if we don't, we will receive exception
on finishUnmarshall (Failed to peer load class) and try to process this
situation with GridCacheIoManager#processFailedMessage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12759) Getting a SecurityContext from GridSecurityProcessor
[ https://issues.apache.org/jira/browse/IGNITE-12759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-12759: - Fix Version/s: (was: 2.8.1) > Getting a SecurityContext from GridSecurityProcessor > > > Key: IGNITE-12759 > URL: https://issues.apache.org/jira/browse/IGNITE-12759 > Project: Ignite > Issue Type: Improvement > Components: security >Affects Versions: 2.8 >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-41 > > 1. Extend the _GridSecurityProcessor_ interface by adding > _securityContext(UUID subjId)_ method and use this method to get the actual > security context. > 2. In the case when _GridSecurityProcessor_ cannot get a security context, > we should return _the unknown security context_. All operations are forbidden > with _the unknown security context_. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055713#comment-17055713 ] Nikolay Izhikov commented on IGNITE-12408: -- > Since you are working on the system views, I'd like to mention that we > already have a page that contains the information about the system views > available in Ignite 2.7: https://apacheignite-sql.readme.io/docs/system-views I think we should move information about existing views to the new page. What do you think? * NODE_ATTRIBUTES * BASELINE_NODES * NODE_METRICS > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055711#comment-17055711 ] Nikolay Izhikov edited comment on IGNITE-12408 at 3/10/20, 8:55 AM: [~Artem Budnikov] Thanks for the feeback. I rewrote metrics and system view pages. Please, take a look. https://apacheignite.readme.io/docs/new-metrics https://apacheignite.readme.io/docs/system-views was (Author: nizhikov): [~Artem Budnikov] Thanks for the feeback. I rewrited metrics and system view pages. Please, take a look. https://apacheignite.readme.io/docs/new-metrics https://apacheignite.readme.io/docs/system-views > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055711#comment-17055711 ] Nikolay Izhikov commented on IGNITE-12408: -- [~Artem Budnikov] Thanks for the feeback. I rewrite metrics and system view pages. Please, take a look. https://apacheignite.readme.io/docs/new-metrics https://apacheignite.readme.io/docs/system-views > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055711#comment-17055711 ] Nikolay Izhikov edited comment on IGNITE-12408 at 3/10/20, 8:55 AM: [~Artem Budnikov] Thanks for the feeback. I rewrited metrics and system view pages. Please, take a look. https://apacheignite.readme.io/docs/new-metrics https://apacheignite.readme.io/docs/system-views was (Author: nizhikov): [~Artem Budnikov] Thanks for the feeback. I rewrite metrics and system view pages. Please, take a look. https://apacheignite.readme.io/docs/new-metrics https://apacheignite.readme.io/docs/system-views > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12759) Getting a SecurityContext from GridSecurityProcessor
Denis Garus created IGNITE-12759: Summary: Getting a SecurityContext from GridSecurityProcessor Key: IGNITE-12759 URL: https://issues.apache.org/jira/browse/IGNITE-12759 Project: Ignite Issue Type: Improvement Components: security Affects Versions: 2.8 Reporter: Denis Garus Fix For: 2.8.1 1. Extend the _GridSecurityProcessor_ interface by adding _securityContext(UUID subjId)_ method and use this method to get the actual security context. 2. In the case when _GridSecurityProcessor_ cannot get a security context, we should return _the unknown security context_. All operations are forbidden with _the unknown security context_. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12759) Getting a SecurityContext from GridSecurityProcessor
[ https://issues.apache.org/jira/browse/IGNITE-12759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus reassigned IGNITE-12759: Assignee: Denis Garus > Getting a SecurityContext from GridSecurityProcessor > > > Key: IGNITE-12759 > URL: https://issues.apache.org/jira/browse/IGNITE-12759 > Project: Ignite > Issue Type: Improvement > Components: security >Affects Versions: 2.8 >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-41 > Fix For: 2.8.1 > > > 1. Extend the _GridSecurityProcessor_ interface by adding > _securityContext(UUID subjId)_ method and use this method to get the actual > security context. > 2. In the case when _GridSecurityProcessor_ cannot get a security context, > we should return _the unknown security context_. All operations are forbidden > with _the unknown security context_. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12549) Scan query/iterator on a replicated cache may get wrong results
[ https://issues.apache.org/jira/browse/IGNITE-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055633#comment-17055633 ] Ivan Pavlukhin commented on IGNITE-12549: - [~macrergate], I believe we can include it into 2.8.1 but as far as I know neither 2.8.1 branch was created neither scope was discussed. We cannot put fix version 2.8.1 immediately here because RESOLVED ticket status can be misleading if the patch will not appear in 2.8.1 by some reason. It seems that we can add 2.8.1 fix version only when the fix will be merged to 2.8.1 branch. > Scan query/iterator on a replicated cache may get wrong results > --- > > Key: IGNITE-12549 > URL: https://issues.apache.org/jira/browse/IGNITE-12549 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7.6 >Reporter: Sergey Kosarev >Assignee: Sergey Kosarev >Priority: Critical > Fix For: 2.9 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Case 1 > 1. start server node 1 > 2. create and fill replicated cache with RebalanceMode.Async (as by default) > 3. start servr node 2 > 4. immediately execute scan query on the replicated cache((or just iterate > the cache)) on the node 2 > It can get empty or partial results. (if rebalance on node 2 is finished) > Case 2 > 1. start server node 1 > 2. create and fill replicated cache with RebalanceMode.Async (as by default) > 3. start client node 2 > 4. start server node 3 > 5. immediately execute scan query on the replicated cache((or just iterate > the cache)) on the client node 2 > It can get empty or partial results. (if rebalance on node 2 is not finished > and query is mapped on the node 2) > It looks like problem in the > org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter#nodes() > case REPLICATED: > if (prj != null || part != null) > return nodes(cctx, prj, part); > if (cctx.affinityNode()) > return *Collections.singletonList(cctx.localNode())*; > Collection affNodes = nodes(cctx, null, null); > return affNodes.isEmpty() ? affNodes : > *Collections.singletonList(F.rand(affNodes))*; > case PARTITIONED: > return nodes(cctx, prj, part); > which is executed in > org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter#executeScanQuery. > If executed on a just started node it obviously returns the local node > disregarding was it rebalanced or not. > If executed on a client it returns a random affinity node, so it also can be > not yet rebalanced node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
