[jira] [Updated] (IGNITE-14030) Java thin client: Add containKeys, clearKey, clearKeys and getAndPutIfAbsent operations to API
[ https://issues.apache.org/jira/browse/IGNITE-14030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14030: Release Note: Java thin: Added containsKeys, clearKey, clearKeys and getAndPutIfAbsent > Java thin client: Add containKeys, clearKey, clearKeys and getAndPutIfAbsent > operations to API > -- > > Key: IGNITE-14030 > URL: https://issues.apache.org/jira/browse/IGNITE-14030 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > It's needed to add containKeys, clearKey, clearKeys and getAndPutIfAbsent > operations to java thin client API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13871) Removing MVCC public API
[ https://issues.apache.org/jira/browse/IGNITE-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-13871: Assignee: Nikolay Izhikov > Removing MVCC public API > > > Key: IGNITE-13871 > URL: https://issues.apache.org/jira/browse/IGNITE-13871 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Nikolay Izhikov >Priority: Blocker > > The community has agreed that MVCC public API should be removed. > Vote thread > http://apache-ignite-developers.2346864.n4.nabble.com/Removing-MVCC-public-API-tp50550.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14046) Update ducktape version to 0.8.2 in ignite-ducktape module
[ https://issues.apache.org/jira/browse/IGNITE-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271924#comment-17271924 ] Anton Vinogradov commented on IGNITE-14046: --- Merged to ignite-ducktape. Thanks for your contribution. > Update ducktape version to 0.8.2 in ignite-ducktape module > -- > > Key: IGNITE-14046 > URL: https://issues.apache.org/jira/browse/IGNITE-14046 > Project: Ignite > Issue Type: Task >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Critical > Time Spent: 0.5h > Remaining Estimate: 0h > > + 11 java at docker > + background service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13957:
Release Note: Fix exception during query entity validation when no query
fields are defined
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:255)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.Grid
[jira] [Updated] (IGNITE-14060) UsageTest#multiRootConfigurationTest does not compile in the main branch
[ https://issues.apache.org/jira/browse/IGNITE-14060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-14060: - Fix Version/s: 3.0.0-alpha2 > UsageTest#multiRootConfigurationTest does not compile in the main branch > > > Key: IGNITE-14060 > URL: https://issues.apache.org/jira/browse/IGNITE-14060 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha1 >Reporter: Valentin Kulichenko >Assignee: Sergey Chugunov >Priority: Critical > Fix For: 3.0.0-alpha2 > > > [~sergey-chugunov] Sergey, looks like you created this test. Please take a > look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14060) UsageTest#multiRootConfigurationTest does not compile in the main branch
[ https://issues.apache.org/jira/browse/IGNITE-14060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov reassigned IGNITE-14060: Assignee: Sergey Chugunov > UsageTest#multiRootConfigurationTest does not compile in the main branch > > > Key: IGNITE-14060 > URL: https://issues.apache.org/jira/browse/IGNITE-14060 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha1 >Reporter: Valentin Kulichenko >Assignee: Sergey Chugunov >Priority: Critical > > [~sergey-chugunov] Sergey, looks like you created this test. Please take a > look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13029) Support Spring Data repositories initialization with Spring Boot auto-starter
[
https://issues.apache.org/jira/browse/IGNITE-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271879#comment-17271879
]
Alexey Plotnik commented on IGNITE-13029:
-
Default way to enable repositories is to assing @EnableIgniteRepositories to
Spring Configuration, basically adding a single line of code.
When using Spring Boot we are forced to use {{spring-boot-autoconfigure-ext}}
artifact, its purpose to initialize Ignite instance. Important: this module
knows nothing about spring-data at all, it's just an ignite core specific
auto-configurer. I guess it's not correct to add @EnableIgniteRepositories to
org.apache.ignite.springframework.boot.autoconfigure.IgniteAutoConfiguration
Another way is to create standalone artifact, i.e.
{{spring-boot-starter-data-ignite}}, an autoconfig class will look like this:
{code}
@EnableIgniteRepositories
public class IgniteDataAutoConfiguration {
}
{code}
The issue here is that by default spring data will be looking for Repository
classes in packages described in {{basePackages}} parameter of annotation, so
it expect something like:
{code}
@EnableIgniteRepositories(basePackages = "com.gridgain.investigate")
public class IgniteDataAutoConfiguration {
}
{code}
If base package is not defined, the one where internal auto-configuration class
of {{spring-boot-autoconfigure-ext}} located will be used
(org.apache.ignite.springframework.boot.data.autoconfigure) which is wrong. To
avoid that behaviour we must somehown parametrize basePackages value and
provide correct packages from user application.
It looks like there are too many steps to just move @EnableIgniteRepositories
from regular spring configuration to auto-configuration.
Could anyone talk to me about motivation of this improvement?
> Support Spring Data repositories initialization with Spring Boot auto-starter
> -
>
> Key: IGNITE-13029
> URL: https://issues.apache.org/jira/browse/IGNITE-13029
> Project: Ignite
> Issue Type: Improvement
> Components: spring, springdata
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Alexey Plotnik
>Priority: Major
> Labels: newbie
>
> It's required to use {{@EnableIgniteRepositories}} annotation and follow this
> procedure to enable Ignite Spring Data repositories:
> https://apacheignite-mix.readme.io/docs/spring-data#spring-data-and-apache-ignite-configuration
> Support the Spring Data repositories enablement via the Spring Boot
> auto-starter if Spring Boot is used by a project:
> https://apacheignite-mix.readme.io/docs/spring-boot
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14060) UsageTest#multiRootConfigurationTest does not compile in the main branch
[ https://issues.apache.org/jira/browse/IGNITE-14060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-14060: - Summary: UsageTest#multiRootConfigurationTest does not compile in the main branch (was: UsageTest#multiRootConfigurationTest does not compile in main) > UsageTest#multiRootConfigurationTest does not compile in the main branch > > > Key: IGNITE-14060 > URL: https://issues.apache.org/jira/browse/IGNITE-14060 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha1 >Reporter: Valentin Kulichenko >Priority: Critical > > [~sergey-chugunov] Sergey, looks like you created this test. Please take a > look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14060) UsageTest#multiRootConfigurationTest does not compile in main
[ https://issues.apache.org/jira/browse/IGNITE-14060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-14060: - Summary: UsageTest#multiRootConfigurationTest does not compile in main (was: UsageTest#multiRootConfigurationTest fails in main) > UsageTest#multiRootConfigurationTest does not compile in main > - > > Key: IGNITE-14060 > URL: https://issues.apache.org/jira/browse/IGNITE-14060 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha1 >Reporter: Valentin Kulichenko >Priority: Critical > > [~sergey-chugunov] Sergey, looks like you created this test. Please take a > look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14060) UsageTest#multiRootConfigurationTest fails in main
Valentin Kulichenko created IGNITE-14060: Summary: UsageTest#multiRootConfigurationTest fails in main Key: IGNITE-14060 URL: https://issues.apache.org/jira/browse/IGNITE-14060 Project: Ignite Issue Type: Bug Affects Versions: 3.0.0-alpha1 Reporter: Valentin Kulichenko [~sergey-chugunov] Sergey, looks like you created this test. Please take a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13863) Python thin client hangs when object has primitive null field
[
https://issues.apache.org/jira/browse/IGNITE-13863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-13863:
-
Description:
The first run of python client returns empty result set, all consequence runs
just hang:
{code:java}
from pyignite import Client, GenericObjectMeta
import collections
from pyignite.datatypes import *
if __name__ == '__main__':
client = Client()
client.connect('localhost', 10800)
cache = client.get_cache('Batch')
#client.register_binary_type(BatchConfigurationPK)
#client.register_binary_type(BatchConfiguration)
result = cache.scan()
print([b for b in result])
{code}
{code:java}
public class ObjectTest {
@QuerySqlField
private String field1;
@QuerySqlField
private String field2;
@QuerySqlField
private String field3;
@QuerySqlField
private String field4;
@QuerySqlField
private Boolean enabled;
public ObjectTest(String field1, String field2, String field3) {
this.field1 = field1;
this.field2 = field2;
this.field3 = field3;
}
}
{code}
{code:java}
public static void main(String[] args) throws IgniteException {
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
IgniteCache cache = ignite.getOrCreateCache("Batch");
for (int i = 0; i < 100; i++) {
cache.put(i, new ObjectTest("" + i, "" + i, "" + i));
}
}
{code}
was:
The first run of python client returns empty result set, all consequence runs
just hang:
{code:java}
from pygridgain import Client, GenericObjectMeta
import collections
from pygridgain.datatypes import *
if __name__ == '__main__':
client = Client()
client.connect('localhost', 10800)
cache = client.get_cache('Batch')
#client.register_binary_type(BatchConfigurationPK)
#client.register_binary_type(BatchConfiguration)
result = cache.scan()
print([b for b in result])
{code}
{code:java}
public class ObjectTest {
@QuerySqlField
private String field1;
@QuerySqlField
private String field2;
@QuerySqlField
private String field3;
@QuerySqlField
private String field4;
@QuerySqlField
private Boolean enabled;
public ObjectTest(String field1, String field2, String field3) {
this.field1 = field1;
this.field2 = field2;
this.field3 = field3;
}
}
{code}
{code:java}
public static void main(String[] args) throws IgniteException {
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
IgniteCache cache = ignite.getOrCreateCache("Batch");
for (int i = 0; i < 100; i++) {
cache.put(i, new ObjectTest("" + i, "" + i, "" + i));
}
}
{code}
> Python thin client hangs when object has primitive null field
> -
>
> Key: IGNITE-13863
> URL: https://issues.apache.org/jira/browse/IGNITE-13863
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.9
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>
> The first run of python client returns empty result set, all consequence runs
> just hang:
> {code:java}
> from pyignite import Client, GenericObjectMeta
> import collections
> from pyignite.datatypes import *
> if __name__ == '__main__':
> client = Client()
> client.connect('localhost', 10800)
> cache = client.get_cache('Batch')
> #client.register_binary_type(BatchConfigurationPK)
> #client.register_binary_type(BatchConfiguration)
> result = cache.scan()
> print([b for b in result])
> {code}
> {code:java}
> public class ObjectTest {
> @QuerySqlField
> private String field1;
> @QuerySqlField
> private String field2;
> @QuerySqlField
> private String field3;
> @QuerySqlField
> private String field4;
> @QuerySqlField
> private Boolean enabled;
> public ObjectTest(String field1, String field2, String field3) {
> this.field1 = field1;
> this.field2 = field2;
> this.field3 = field3;
> }
> }
> {code}
> {code:java}
> public static void main(String[] args) throws IgniteException {
> Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
> IgniteCache cache = ignite.getOrCreateCache("Batch");
> for (int i = 0; i < 100; i++) {
> cache.put(i, new ObjectTest("" + i, "" + i, "" + i));
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14059) Thin Python client doesn't work with nested complex objects
[ https://issues.apache.org/jira/browse/IGNITE-14059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14059: - Attachment: Main.java > Thin Python client doesn't work with nested complex objects > --- > > Key: IGNITE-14059 > URL: https://issues.apache.org/jira/browse/IGNITE-14059 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > Attachments: Main.java, main.py > > > Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14059) Thin Python client doesn't work with nested complex objects
[ https://issues.apache.org/jira/browse/IGNITE-14059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14059: - Attachment: (was: Main.java) > Thin Python client doesn't work with nested complex objects > --- > > Key: IGNITE-14059 > URL: https://issues.apache.org/jira/browse/IGNITE-14059 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > Attachments: main.py > > > Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14059) Thin Python client doesn't work with nested complex objects
Igor Sapego created IGNITE-14059: Summary: Thin Python client doesn't work with nested complex objects Key: IGNITE-14059 URL: https://issues.apache.org/jira/browse/IGNITE-14059 Project: Ignite Issue Type: Bug Components: python, thin client Affects Versions: python-0.3.4 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: python-0.4.0 Attachments: main.py Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14056) Python thin: Readme and other docs are outdated
[ https://issues.apache.org/jira/browse/IGNITE-14056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271691#comment-17271691 ] Igor Sapego commented on IGNITE-14056: -- TC pass: https://ci.ignite.apache.org/buildConfiguration/IgniteThinClients_Tests_ThinClientPython/5843329 > Python thin: Readme and other docs are outdated > --- > > Key: IGNITE-14056 > URL: https://issues.apache.org/jira/browse/IGNITE-14056 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The readme files for thin clients should be updated accordingly as now > they're separate products be following rules: > * readme is located in root directory > * how to install from zip > * how to upgrade if a previous version installed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14058) Python Thin client: get boolean type return integers
Igor Sapego created IGNITE-14058:
Summary: Python Thin client: get boolean type return integers
Key: IGNITE-14058
URL: https://issues.apache.org/jira/browse/IGNITE-14058
Project: Ignite
Issue Type: Bug
Components: python, thin client
Affects Versions: python-0.3.4
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: python-0.4.0
Steps:
- put boolean value in cluster
{code}
from pyignite import Client
from pyignite.datatypes import *
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("test")
cache.put(1, [True, False], key_hint=IntObject, value_hint=BoolArrayObject)
{code}
- get value
{code}
from pyignite import Client
from pyignite.datatypes import *
client = Client()
client.connect('127.0.0.1', 10800)
cache = client.get_or_create_cache("test")
result = cache.get(1, key_hint=IntObject)
print(*[str(arr_item).lower() for arr_item in result])
{code}
Actual:
- return integers
{code}
0 1
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14016) Prepare an RPM package for Ignite 3.0
[
https://issues.apache.org/jira/browse/IGNITE-14016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271608#comment-17271608
]
Valentin Kulichenko commented on IGNITE-14016:
--
[~vveider], if the issue is related to the home folder, can we not create it
for the {{ignite}} user at all? If it's currently needed only for
{{.ignitecfg}} file, then I'm sure something can be done on the CLI tool side.
AFAIK, some other databases (Postgres?) follow a similar approach. Can we check
how these databases address the issue?
> Prepare an RPM package for Ignite 3.0
> -
>
> Key: IGNITE-14016
> URL: https://issues.apache.org/jira/browse/IGNITE-14016
> Project: Ignite
> Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Attachments: rhel.log
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13601) Ignite-rest-http and ignite-kubernetes include vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Baryshnikov reassigned IGNITE-13601: - Assignee: Igor Baryshnikov > Ignite-rest-http and ignite-kubernetes include vulnerable dependencies > -- > > Key: IGNITE-13601 > URL: https://issues.apache.org/jira/browse/IGNITE-13601 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.8.1 >Reporter: Andrew Story >Assignee: Igor Baryshnikov >Priority: Blocker > Labels: 2.9.1-rc > > The ignite-rest-http and ignite-kubernetes modules include a vulnerable > version of the jackson-databind library. This was spotted in 2.8.1. > This component jackson-databind-2.9.6.jar is flagged as having numerous > critical, high and medium security vulnerabilities, one of which is > described here: > [https://nvd.nist.gov/vuln/detail/CVE-2019-14540] > More here: > [http://apache-ignite-users.70518.x6.nabble.com/Critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-jackson-r-td34032.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12955) Document a new command control.sh --cache check_index_inline_sizes
[ https://issues.apache.org/jira/browse/IGNITE-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271569#comment-17271569 ] Nikita Safonov commented on IGNITE-12955: - Hi [~mmuzaf], sure! > Document a new command control.sh --cache check_index_inline_sizes > -- > > Key: IGNITE-12955 > URL: https://issues.apache.org/jira/browse/IGNITE-12955 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Maxim Muzafarov >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > Please look at IGNITE-12942 and devlist discussion linked to IGNITE-12942 for > all information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14057) Python thin: implement support for big-endianness
Igor Sapego created IGNITE-14057: Summary: Python thin: implement support for big-endianness Key: IGNITE-14057 URL: https://issues.apache.org/jira/browse/IGNITE-14057 Project: Ignite Issue Type: Bug Components: python, thin client Affects Versions: python-0.3.4 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: python-0.4.0 Currently, big endian byte order is not supported in Python Thin client. Need to implement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14057) Python thin: implement support for big-endianness
[ https://issues.apache.org/jira/browse/IGNITE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14057: - Issue Type: Improvement (was: Bug) > Python thin: implement support for big-endianness > - > > Key: IGNITE-14057 > URL: https://issues.apache.org/jira/browse/IGNITE-14057 > Project: Ignite > Issue Type: Improvement > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > > Currently, big endian byte order is not supported in Python Thin client. Need > to implement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13385) Documentation of cache warm-up strategy
[ https://issues.apache.org/jira/browse/IGNITE-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271565#comment-17271565 ] Maxim Muzafarov commented on IGNITE-13385: -- Cherry-picked to 2.10 > Documentation of cache warm-up strategy > --- > > Key: IGNITE-13385 > URL: https://issues.apache.org/jira/browse/IGNITE-13385 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Kirill Tkalenko >Assignee: Nikita Safonov >Priority: Blocker > Labels: IEP-40, important > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Need to add documentation about the warm-up strategies that are implemented > for IEP-40, as well as about the possibility of stopping it via control.sh > and jmx. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12955) Document a new command control.sh --cache check_index_inline_sizes
[ https://issues.apache.org/jira/browse/IGNITE-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271556#comment-17271556 ] Maxim Muzafarov commented on IGNITE-12955: -- [~nsafonov] Hello, I've prepared the patch. Can you please review my changes? > Document a new command control.sh --cache check_index_inline_sizes > -- > > Key: IGNITE-12955 > URL: https://issues.apache.org/jira/browse/IGNITE-12955 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Maxim Muzafarov >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > Please look at IGNITE-12942 and devlist discussion linked to IGNITE-12942 for > all information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13957:
Ignite Flags: (was: Docs Required,Release Notes Required)
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:255)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAto
[jira] [Commented] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271523#comment-17271523
]
Pavel Tupitsyn commented on IGNITE-13957:
-
Merged to master: 2d6dcc9e0ee559b9daccfc8f5c592ecc13a0ddbd
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:255)
> at
> org.apache.ignite.internal.processors.cache.distrib
[jira] [Updated] (IGNITE-12203) Rebalance is loading partitions already loading after cancellation without WAL
[ https://issues.apache.org/jira/browse/IGNITE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12203: - Fix Version/s: (was: 2.10) > Rebalance is loading partitions already loading after cancellation without WAL > -- > > Key: IGNITE-12203 > URL: https://issues.apache.org/jira/browse/IGNITE-12203 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > I have seen from log partition miss warnings and after that rebelance was > canceled and was forcibly restarted but already over another suppliers. In > case when added nodes without a storage in persistent cluster it can lead to > several times fully rebalance. It seem to bee because we have not updated > partitions state until rebalance finished. > Should to prevent partition eviction until rebalance on all nodes completed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12852: - Fix Version/s: (was: 2.10) > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Critical > Time Spent: 0.5h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12905) QueryKeyValueIterable missing custom spliterator() implementation
[
https://issues.apache.org/jira/browse/IGNITE-12905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12905:
-
Fix Version/s: (was: 2.10)
> QueryKeyValueIterable missing custom spliterator() implementation
> -
>
> Key: IGNITE-12905
> URL: https://issues.apache.org/jira/browse/IGNITE-12905
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 2.8
> Environment: Windows 10
> JDK 1.8.0_172
> ignite-core 2.8.0
> reactor-core 3.3.3
>Reporter: Johnny Galatikitis
>Assignee: Johnny Galatikitis
>Priority: Critical
> Attachments:
> IGNITE-12905_-_add_QueryKeyValueSpliterator_and_corresponding_test.patch
>
> Time Spent: 6h
> Remaining Estimate: 0h
>
> We are using apache ignite with reactor-core and since reactors upgrade from
> 3.2.12 to 3.3.3 {code:java}
> org.apache.ignite.internal.processors.query.QueryKeyValueIterable.iterator
> {code}
> is called multiple times. It starts with:
> 1. calling iterable.spliterator().hasCharacteristics(Spliterator.SIZED),
> where iterable is instanceof QueryKeyValueIterable
> 2. calls default implementation
> Spliterators.spliteratorUnknownSize(iterator(), 0)
> 3. which in turn calls ignite's QueryKeyValueIterable.iterator() call and
> that "uses it up" for subsequent calls, i.e. throw IgniteException "Iterator
> is already fetched or query was cancelled."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10417) notifyDiscoveryListener() call can be lost.
[ https://issues.apache.org/jira/browse/IGNITE-10417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-10417: - Fix Version/s: (was: 2.10) > notifyDiscoveryListener() call can be lost. > --- > > Key: IGNITE-10417 > URL: https://issues.apache.org/jira/browse/IGNITE-10417 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Critical > > 1) ServerImpl:5455 notifyDiscoveryListener can not be called in case of > spiState != CONNECTED, for example DISCONNECTING which is valid state > nevetheless inside notifyDiscoveryListener we check spiState == CONNECTED || > spiState == DISCONNECTING, also we need to improve logging in > notifyDiscoveryListener(). > 2) Improve logging on duplicated custom discovery event. > 3) Add assert if msg.creatorNodeId() doesn't exist in topology this is bad > behaviour taht should lead to node fail. > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12464) Service metrics
[ https://issues.apache.org/jira/browse/IGNITE-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271515#comment-17271515 ] Maxim Muzafarov commented on IGNITE-12464: -- Folks, any updates? > Service metrics > --- > > Key: IGNITE-12464 > URL: https://issues.apache.org/jira/browse/IGNITE-12464 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Nikolay Izhikov >Assignee: Vladimir Steshin >Priority: Minor > Labels: IEP-35 > Fix For: 2.10 > > Time Spent: 20.5h > Remaining Estimate: 0h > > We should provide the following metrics for each deployed service: > * -Count of executions- - this number seems useless, because, we can compute > it just by summing all histograms values. > * Histogram of executions duration -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13472) JDBC bulkload operations are processed with wrong security context
[
https://issues.apache.org/jira/browse/IGNITE-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-13472:
-
Fix Version/s: (was: 2.10)
> JDBC bulkload operations are processed with wrong security context
> --
>
> Key: IGNITE-13472
> URL: https://issues.apache.org/jira/browse/IGNITE-13472
> Project: Ignite
> Issue Type: Bug
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
> {code:java}
> [12:02:56] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true]]class
> org.apache.ignite.IgniteCheckedException: Authorization failed
> [perm=CACHE_PUT, name=test-bulkload-cache,
> subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
> type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7589)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:979)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.plugin.security.SecurityException:
> Authorization failed [perm=CACHE_PUT, name=test-bulkload-cache,
> subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
> type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
> at
> org.apache.ignite.internal.processors.security.impl.TestSecurityProcessor.authorize(TestSecurityProcessor.java:153)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:207)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.checkSecurityPermission(DataStreamerUpdateJob.java:170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:123)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7087)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:971)
> ... 4 more
> {code}
> This exception means the put operation is processed with node context instead
> of user. Also, operation doesn't finish successfully.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13878) Allocated RAM is always 0 for non-persistent regions of persistent cluster
[ https://issues.apache.org/jira/browse/IGNITE-13878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271514#comment-17271514 ] Maxim Muzafarov commented on IGNITE-13878: -- Folks, can we move this issue to the next release? > Allocated RAM is always 0 for non-persistent regions of persistent cluster > -- > > Key: IGNITE-13878 > URL: https://issues.apache.org/jira/browse/IGNITE-13878 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.9 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#wrapMetricsMemoryProvider > The logic in overridden nextRegion() method for the DirectMemoryProvider in > the case above does not work for non-persistent data regions, as an example, > region with persistenceEnabled=false, initSize = maxSize = 2G has only a > single chunk that writes into > memMetrics.updateCheckpointBufferSize(chunkSize) instead of > memMetrics.updateOffHeapSize(chunkSize). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13596) Add flag to DataRecord to differentiate records on primary and backup nodes
[ https://issues.apache.org/jira/browse/IGNITE-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13596: - Fix Version/s: (was: 2.10) > Add flag to DataRecord to differentiate records on primary and backup nodes > --- > > Key: IGNITE-13596 > URL: https://issues.apache.org/jira/browse/IGNITE-13596 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > Time Spent: 10m > Remaining Estimate: 0h > > To be able to minimize CDC processing volume we should be able to > differentiate DataRecords in WAL on primary and backup nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-2176:
Fix Version/s: (was: 2.10)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Major
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> 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:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(Bin
[jira] [Updated] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12779:
-
Fix Version/s: (was: 2.10)
2.11
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, we should improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> Let's add a link to a full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271511#comment-17271511
]
Maxim Muzafarov commented on IGNITE-12779:
--
[~NSAmelchev]
Can you proceed with the merge?
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, we should improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> Let's add a link to a full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11075) Index rebuild procedure over cache partition file
[
https://issues.apache.org/jira/browse/IGNITE-11075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11075:
-
Fix Version/s: (was: 2.10)
> Index rebuild procedure over cache partition file
> -
>
> Key: IGNITE-11075
> URL: https://issues.apache.org/jira/browse/IGNITE-11075
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Maxim Muzafarov
>Assignee: Sergey Kalashnikov
>Priority: Major
> Labels: iep-28
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The node can own partition when partition data is rebalanced and cache
> indexes are ready. For the message-based cluster rebalancing, approach
> indexes are rebuilding simultaneously with cache data loading. For the
> file-based rebalancing approach, the index rebuild procedure must be finished
> before the partition state is set to the OWNING state.
> We need to rebuild local SQL indexes (the {{index.bin}} file) when partition
> file has been received. Crash-recovery guarantees must be supported by a node
> since index-rebuild performs on the node in the topology.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13112) The current security context should be obtained using the IgniteSecurity interface only.
[ https://issues.apache.org/jira/browse/IGNITE-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13112: - Fix Version/s: (was: 2.10) > The current security context should be obtained using the IgniteSecurity > interface only. > > > Key: IGNITE-13112 > URL: https://issues.apache.org/jira/browse/IGNITE-13112 > Project: Ignite > Issue Type: Bug > Components: cache, security >Affects Versions: 2.8.1 >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-41 > Time Spent: 4h 50m > Remaining Estimate: 0h > > For getting the current security context, we have to use the IgniteSecurity > interface only. > We need to get rid of all other ways to transfer a security subject id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13596) Add flag to DataRecord to differentiate records on primary and backup nodes
[ https://issues.apache.org/jira/browse/IGNITE-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271507#comment-17271507 ] Maxim Muzafarov commented on IGNITE-13596: -- [~nizhikov] Do we still need this issue pinned to 2.10 release or can move it to the next? > Add flag to DataRecord to differentiate records on primary and backup nodes > --- > > Key: IGNITE-13596 > URL: https://issues.apache.org/jira/browse/IGNITE-13596 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > To be able to minimize CDC processing volume we should be able to > differentiate DataRecords in WAL on primary and backup nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13441) Cache (Restarts) 1 failed with Execution timeout
[ https://issues.apache.org/jira/browse/IGNITE-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13441: - Fix Version/s: (was: 2.10) > Cache (Restarts) 1 failed with Execution timeout > > > Key: IGNITE-13441 > URL: https://issues.apache.org/jira/browse/IGNITE-13441 > Project: Ignite > Issue Type: Task >Reporter: Nikita Tolstunov >Assignee: Alexey Scherbakov >Priority: Major > Attachments: > Ignite_Tests_2.4_Java_8_9_10_11_Cache_Restarts_1_22724.log.zip > > Time Spent: 20m > Remaining Estimate: 0h > > Suite [Cache(Restarts) > 1|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E&mode=builds] > regularly fails with execution timeout. > I found that in some cases > IgniteCacheNearRestartRollbackSelfTest#testRestarts caused it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13767) Remove Python PHP and Node.js thin clients from main repository
[ https://issues.apache.org/jira/browse/IGNITE-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13767: - Fix Version/s: (was: 2.10) > Remove Python PHP and Node.js thin clients from main repository > --- > > Key: IGNITE-13767 > URL: https://issues.apache.org/jira/browse/IGNITE-13767 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.9 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Need to remove the following directories, as we now have separate repos for > Python, Node.js and PHP thin clients: > modules/platforms/python > modules/platforms/nodejs > modules/platforms/php > > Also, need to check all the places in code where those directories are > referenced. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12553) [IEP-35] public Java metric API
[ https://issues.apache.org/jira/browse/IGNITE-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12553: - Fix Version/s: (was: 2.10) > [IEP-35] public Java metric API > --- > > Key: IGNITE-12553 > URL: https://issues.apache.org/jira/browse/IGNITE-12553 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Critical > Labels: IEP-35 > Time Spent: 20m > Remaining Estimate: 0h > > Right now, there is no simple way to get metrics values from the java code. > We need to create a java API to access metric values. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12553) [IEP-35] public Java metric API
[ https://issues.apache.org/jira/browse/IGNITE-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271506#comment-17271506 ] Maxim Muzafarov commented on IGNITE-12553: -- The issue moved to the next release due to inactivity. > [IEP-35] public Java metric API > --- > > Key: IGNITE-12553 > URL: https://issues.apache.org/jira/browse/IGNITE-12553 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Critical > Labels: IEP-35 > Time Spent: 20m > Remaining Estimate: 0h > > Right now, there is no simple way to get metrics values from the java code. > We need to create a java API to access metric values. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-3212) Servers get stuck with the warning "Failed to wait for initial partition map exchange" during falover test
[
https://issues.apache.org/jira/browse/IGNITE-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-3212:
Fix Version/s: (was: 2.10)
> Servers get stuck with the warning "Failed to wait for initial partition map
> exchange" during falover test
> --
>
> Key: IGNITE-3212
> URL: https://issues.apache.org/jira/browse/IGNITE-3212
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Priority: Critical
> Fix For: 3.0
>
>
> Servers being restarted during failover test get stuck after some time with
> the warning "Failed to wait for initial partition map exchange".
> {noformat}
> [08:44:41,303][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager]
> Added new node to topology: TcpDiscoveryNode
> [id=db557f04-43b7-4e28-ae0d-d4dcf4139c89, addrs=
> [10.20.0.222, 127.0.0.1], sockAddrs=[fosters-222/10.20.0.222:47503,
> /10.20.0.222:47503, /127.0.0.1:47503], discPort=47503, order=44, intOrder=32,
> lastExchangeTime=1464
> 363880917, loc=false, ver=1.6.0#20160525-sha1:48321a40, isClient=false]
> [08:44:41,304][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager]
> Topology snapshot [ver=44, servers=19, clients=1, CPUs=64, heap=160.0GB]
> [08:45:11,455][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager]
> Added new node to topology: TcpDiscoveryNode
> [id=6fae61a7-c1c1-40e5-8ad0-8bf5d6c86eb7, addrs=
> [10.20.0.223, 127.0.0.1], sockAddrs=[fosters-223/10.20.0.223:47503,
> /10.20.0.223:47503, /127.0.0.1:47503], discPort=47503, order=45, intOrder=33,
> lastExchangeTime=1464
> 363910999, loc=false, ver=1.6.0#20160525-sha1:48321a40, isClient=false]
> [08:45:11,455][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager]
> Topology snapshot [ver=45, servers=20, clients=1, CPUs=64, heap=170.0GB]
> [08:45:19,942][INFO ][ignite-update-notifier-timer][GridUpdateNotifier]
> Update status is not available.
> [08:46:20,370][WARN ][main][GridCachePartitionExchangeManager] Failed to wait
> for initial partition map exchange. Possible reasons are:
> ^-- Transactions in deadlock.
> ^-- Long running transactions (ignore if this is the case).
> ^-- Unreleased explicit locks.
> [08:48:30,375][WARN ][main][GridCachePartitionExchangeManager] Still waiting
> for initial partition map exchange ...
> {noformat}
> "Failed to wait for partition release future" warnings are on other nodes.
> {noformat}
> [08:09:45,822][WARN
> ][exchange-worker-#82%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=29,
> minorTopVer=0], node=cab5d0e0-7365-4774-8f99-d9f131c5d896]. Dumping pending
> objects that might be the cause:
> [08:09:45,822][WARN
> ][exchange-worker-#82%null%][GridCachePartitionExchangeManager] Ready
> affinity version: AffinityTopologyVersion [topVer=28, minorTopVer=1]
> [08:09:45,826][WARN
> ][exchange-worker-#82%null%][GridCachePartitionExchangeManager] Last exchange
> future: GridDhtPartitionsExchangeFuture ...
> {noformat}
> Load config:
> - 1 client, 20 servers (5 servers per 1 host)
> - warmup 60
> - duration 66h
> - preload 5M
> - key range 10M
> - operations: PUT PUT_ALL GET GET_ALL INVOKE INVOKE_ALL REMOVE REMOVE_ALL
> PUT_IF_ABSENT REPLACE
> - backups count 3
> - 3 servers restart every 15 min with 30 sec step, pause between stop and
> start 5min
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11970) Excessive use of memory in continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11970: - Fix Version/s: (was: 2.11) > Excessive use of memory in continuous queries > - > > Key: IGNITE-11970 > URL: https://issues.apache.org/jira/browse/IGNITE-11970 > Project: Ignite > Issue Type: Bug >Reporter: Igor Belyakov >Assignee: Igor Belyakov >Priority: Critical > Time Spent: 40m > Remaining Estimate: 0h > > When we prepare to send an entry into the continuous query's filter and > listener, we store it in an instance of CacheContinuousQueryEventBuffer.Batch. > The batch is an array of entries of size > IGNITE_CONTINUOUS_QUERY_SERVER_BUFFER_SIZE (default is 1000) that stores the > currently received entries (we need it for the case of concurrent updates to > make sure that we preserve the order of update counters). > The issue is that when we process a part of the array we keep the links to > the processed entries until we exhaust the array (after when we finally clear > it). Because of that we may store up to 999 garbage objects which can be a > lot if the entries are big. > Need to clear the entries right after we've processed them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11970) Excessive use of memory in continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11970: - Fix Version/s: (was: 2.10) 2.11 > Excessive use of memory in continuous queries > - > > Key: IGNITE-11970 > URL: https://issues.apache.org/jira/browse/IGNITE-11970 > Project: Ignite > Issue Type: Bug >Reporter: Igor Belyakov >Assignee: Igor Belyakov >Priority: Critical > Fix For: 2.11 > > Time Spent: 40m > Remaining Estimate: 0h > > When we prepare to send an entry into the continuous query's filter and > listener, we store it in an instance of CacheContinuousQueryEventBuffer.Batch. > The batch is an array of entries of size > IGNITE_CONTINUOUS_QUERY_SERVER_BUFFER_SIZE (default is 1000) that stores the > currently received entries (we need it for the case of concurrent updates to > make sure that we preserve the order of update counters). > The issue is that when we process a part of the array we keep the links to > the processed entries until we exhaust the array (after when we finally clear > it). Because of that we may store up to 999 garbage objects which can be a > lot if the entries are big. > Need to clear the entries right after we've processed them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271411#comment-17271411
]
Konstantin Orlov commented on IGNITE-13957:
---
[~ptupitsyn], the patch looks good to me.
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:255)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atom
[jira] [Commented] (IGNITE-13877) Error restarting the node with switching from disabled WAL archiving to enabled
[
https://issues.apache.org/jira/browse/IGNITE-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271407#comment-17271407
]
Ignite TC Bot commented on IGNITE-13877:
{panel:title=Branch: [pull/8681/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5842880]]
* IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate1[walMode=FSYNC] -
New test duration 77s is more that 1 minute
* IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate0[walMode=FSYNC] -
New test duration 77s is more that 1 minute
* IgnitePdsTestSuite:
WalArchiveConsistencyTest.testNotChangeWalSegmentsWitTruncate[walMode=FSYNC] -
New test duration 77s is more that 1 minute
{panel}
{panel:title=Branch: [pull/8681/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 1{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5842880]]
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWithoutTruncate[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testNotChangeWalSegmentsWitTruncate[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate1[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate1[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWithoutTruncate[walMode=FSYNC]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testIncreaseWalSegmentsWithoutTruncate[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate0[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate0[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testNotChangeWalSegmentsWitTruncate[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testIncreaseWalSegmentsWithoutTruncate[walMode=FSYNC]
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5842386&buildTypeId=IgniteTests24Java8_RunAll]
> Error restarting the node with switching from disabled WAL archiving to
> enabled
> ---
>
> Key: IGNITE-13877
> URL: https://issues.apache.org/jira/browse/IGNITE-13877
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Attachments: Ignite13877Test.java
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If a user starts a node with WAL archiving disabled, and then poured data
> there and there were more than *DataStorageConfiguration#walSegments* and
> then wants to restart a node with WAL archiving enabled, they will fail due
> to the following error:
> {noformat}
> SEVERE: Critical system error detected. Will be handled accordingly to
> configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false,
> timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.StorageException: Failed to read
> checkpoint record from WAL, persistence consistency cannot be guaranteed.
> Make sure configuration points to correct WAL folders and WAL folder is
> properly mounted [ptr=FileWALPointer [idx=11, fileOff=15864934, len=21409],
> walPath=db/wal, walArchive=db/wal/archive]]]
> class
> org.apache.ignite.internal.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=FileWALPointer [idx=11, fileOff=15864934,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2324)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:799)
> at
> org.apache.ignite.internal.proces
[jira] [Commented] (IGNITE-14039) Add warnings about WAL enable/disable requiring topology stability
[ https://issues.apache.org/jira/browse/IGNITE-14039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271387#comment-17271387 ] Maxim Muzafarov commented on IGNITE-14039: -- Cherry-picked to 2.10 > Add warnings about WAL enable/disable requiring topology stability > -- > > Key: IGNITE-14039 > URL: https://issues.apache.org/jira/browse/IGNITE-14039 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Blocker > Fix For: 2.10 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Due to IGNITE-13976 WAL enable/disable is not suitable for any kind of > changing topology and will cause cache to go into inconsistent state. We need > to add warnings to javadoc, runtime and documentation, and provide tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271386#comment-17271386 ] Maxim Muzafarov commented on IGNITE-13912: -- [~ktkale...@gridgain.com] Thanks, cherry-picked to 2.10. > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: reproducer.zip, server1-full-wal-checkpoint.log, > wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, > wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, > wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11303) Python thin client: best effort affinity
[ https://issues.apache.org/jira/browse/IGNITE-11303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-11303: - Fix Version/s: python-0.4.0 > Python thin client: best effort affinity > > > Key: IGNITE-11303 > URL: https://issues.apache.org/jira/browse/IGNITE-11303 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: python-0.3.4 >Reporter: Dmitry Melnichuk >Assignee: Igor Sapego >Priority: Major > Labels: Python, Python3, iep-23, thin > Fix For: python-0.4.0 > > Time Spent: 6h 20m > Remaining Estimate: 0h > > The goal is to implement > [IEP-23|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] > using background thread (`threading` module). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11303) Python thin client: best effort affinity
[ https://issues.apache.org/jira/browse/IGNITE-11303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-11303: - Affects Version/s: python-0.3.4 > Python thin client: best effort affinity > > > Key: IGNITE-11303 > URL: https://issues.apache.org/jira/browse/IGNITE-11303 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: python-0.3.4 >Reporter: Dmitry Melnichuk >Assignee: Igor Sapego >Priority: Major > Labels: Python, Python3, iep-23, thin > Time Spent: 6h 20m > Remaining Estimate: 0h > > The goal is to implement > [IEP-23|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] > using background thread (`threading` module). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11303) Python thin client: best effort affinity
[ https://issues.apache.org/jira/browse/IGNITE-11303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-11303: - Component/s: python > Python thin client: best effort affinity > > > Key: IGNITE-11303 > URL: https://issues.apache.org/jira/browse/IGNITE-11303 > Project: Ignite > Issue Type: New Feature > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Dmitry Melnichuk >Assignee: Igor Sapego >Priority: Major > Labels: Python, Python3, iep-23, thin > Fix For: python-0.4.0 > > Time Spent: 6h 20m > Remaining Estimate: 0h > > The goal is to implement > [IEP-23|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] > using background thread (`threading` module). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14056) Python thin: Readme and other docs are outdated
[ https://issues.apache.org/jira/browse/IGNITE-14056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14056: - Fix Version/s: python-0.4.0 > Python thin: Readme and other docs are outdated > --- > > Key: IGNITE-14056 > URL: https://issues.apache.org/jira/browse/IGNITE-14056 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > > The readme files for thin clients should be updated accordingly as now > they're separate products be following rules: > * readme is located in root directory > * how to install from zip > * how to upgrade if a previous version installed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: (was: php-1.0.0)
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: php-1.0.0
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2, php-1.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14056) Python thin: Readme and other docs are outdated
[ https://issues.apache.org/jira/browse/IGNITE-14056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14056: - Affects Version/s: python-0.3.4 > Python thin: Readme and other docs are outdated > --- > > Key: IGNITE-14056 > URL: https://issues.apache.org/jira/browse/IGNITE-14056 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > > The readme files for thin clients should be updated accordingly as now > they're separate products be following rules: > * readme is located in root directory > * how to install from zip > * how to upgrade if a previous version installed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: (was: python-0.3.4)
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: python-1.0.0
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2, python-1.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: (was: python-1.0.0)
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: python-0.4.0
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2, python-0.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: python-0.3.4
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2, python-0.3.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-14001:
--
Fix Version/s: (was: python-0.4.0)
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14056) Python thin: Readme and other docs are outdated
Igor Sapego created IGNITE-14056: Summary: Python thin: Readme and other docs are outdated Key: IGNITE-14056 URL: https://issues.apache.org/jira/browse/IGNITE-14056 Project: Ignite Issue Type: Bug Components: python, thin client Reporter: Igor Sapego Assignee: Igor Sapego The readme files for thin clients should be updated accordingly as now they're separate products be following rules: * readme is located in root directory * how to install from zip * how to upgrade if a previous version installed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271364#comment-17271364 ] Kirill Tkalenko commented on IGNITE-13912: -- Hi, [~mmuzaf]! If IGNITE-13831 is at 2.10 then yes. > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: reproducer.zip, server1-full-wal-checkpoint.log, > wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, > wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, > wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271362#comment-17271362 ] Maxim Muzafarov commented on IGNITE-13912: -- Folks, since the cause seem to be not fixed do we really need the issue in 2.10? > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: reproducer.zip, server1-full-wal-checkpoint.log, > wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, > wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, > wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14039) Add warnings about WAL enable/disable requiring topology stability
[ https://issues.apache.org/jira/browse/IGNITE-14039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271361#comment-17271361 ] Nikita Safonov commented on IGNITE-14039: - [~ilyak] I'm on it. > Add warnings about WAL enable/disable requiring topology stability > -- > > Key: IGNITE-14039 > URL: https://issues.apache.org/jira/browse/IGNITE-14039 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Blocker > Fix For: 2.10 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Due to IGNITE-13976 WAL enable/disable is not suitable for any kind of > changing topology and will cause cache to go into inconsistent state. We need > to add warnings to javadoc, runtime and documentation, and provide tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14047) .NET: Release build fails because of missing nuget executable
[
https://issues.apache.org/jira/browse/IGNITE-14047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271360#comment-17271360
]
Pavel Tupitsyn commented on IGNITE-14047:
-
Merged to master: 727897f6e091466f552d299a9dafbc5fd962bb78
> .NET: Release build fails because of missing nuget executable
> -
>
> Key: IGNITE-14047
> URL: https://issues.apache.org/jira/browse/IGNITE-14047
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NuGet executable is not downloaded when {{-skipNuGet}} is specified, but it
> is required for .NET Framework build.
> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_ApacheIgniteNightlyReleaseBuildNetCpp/5838928?buildTab=log&focusLine=3&linesState=805
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13957:
Description:
{{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
corresponding classes can't be found.
* The bug was introduced in 2.9
* There is no problem when some query entity fields are defined
Reproducer in .NET
{code}
// CacheQueriesCodeConfigurationTest
///
/// Tests query entity validation when no has been set.
///
[Test]
public void TestMissingQueryAttributes()
{
using (var ignite =
Ignition.Start(TestUtils.GetTestConfiguration()))
{
var cfg = new CacheConfiguration(
TestUtils.TestName,
new QueryEntity(typeof(string),
typeof(MissingAttributesTest)));
var cache = ignite.GetOrCreateCache(cfg);
cache["1"] = new MissingAttributesTest {Foo = "Bar"};
}
}
///
/// Class without any attributes.
///
private class MissingAttributesTest
{
/** */
public string Foo { get; set; }
}
{code}
Exception:
{code}
Apache.Ignite.Core.Cache.CacheException : class
org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
in Java [platformId=0, typeId=1242226865].
> Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
class
'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
in Java [platformId=0, typeId=1242226865].
> Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
in Java [platformId=0, typeId=1242226865].
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
at
org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
.NET class
'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
in Java [platformId=0, typeId=1242226865].
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:255)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1169)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:634)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2596)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2575)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1316)
... 3 more
Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException: Failed to
resolve .NET class
'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
in Java [platformId=0, typeId=1242226865].
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:717)
at
org.apache.ignite.internal
[jira] [Commented] (IGNITE-14030) Java thin client: Add containKeys, clearKey, clearKeys and getAndPutIfAbsent operations to API
[ https://issues.apache.org/jira/browse/IGNITE-14030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271356#comment-17271356 ] Mikhail Petrov commented on IGNITE-14030: - [~alex_pl], Thanks a lot for the review! > Java thin client: Add containKeys, clearKey, clearKeys and getAndPutIfAbsent > operations to API > -- > > Key: IGNITE-14030 > URL: https://issues.apache.org/jira/browse/IGNITE-14030 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > It's needed to add containKeys, clearKey, clearKeys and getAndPutIfAbsent > operations to java thin client API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271341#comment-17271341
]
Pavel Tupitsyn edited comment on IGNITE-13957 at 1/25/21, 2:39 PM:
---
[~korlov] please review. I've restored the logic that existed before
IGNITE-13075.
was (Author: ptupitsyn):
[~korlov] please review.
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET (TODO: add both .NET and Java tests for this)
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
> at
> org.apache.ignite.internal.processors.cach
[jira] [Commented] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271341#comment-17271341
]
Pavel Tupitsyn commented on IGNITE-13957:
-
[~korlov] please review.
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET (TODO: add both .NET and Java tests for this)
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.validateKeyAndValue(GridCacheContext.java:1916)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:555)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:457)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:255)
> at
> org.apache.ignite.internal.processors.c
[jira] [Commented] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271334#comment-17271334
]
Ignite TC Bot commented on IGNITE-13957:
{panel:title=Branch: [pull/8694/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8694/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842148]]
* {color:#013220}dll:
CacheQueriesCodeConfigurationTest.TestQueryEntityValidationWithMissingQueryAttributes
- PASSED{color}
{color:#8b}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842147]]
* {color:#013220}exe:
CacheQueriesCodeConfigurationTest.TestQueryEntityValidationWithMissingQueryAttributes
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5842172&buildTypeId=IgniteTests24Java8_RunAll]
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET (TODO: add both .NET and Java tests for this)
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:840)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(Ignite
[jira] [Issue Comment Deleted] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13957:
Comment: was deleted
(was: {panel:title=Branch: [pull/8694/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842109]]
* ZookeeperDiscoverySpiTestSuite1: ZookeeperClientTest.testConnectionLoss4 -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5842091]]
{color:#d04437}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842094]]
* ClientTestSuite: ComputeTaskTest.testExecuteTaskConcurrentLoad - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842146]]
* IgnitePdsTestSuite4:
RebalanceCancellationTest.testRebalanceDynamicCacheOnMixedCluster - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8694/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842148]]
* {color:#013220}dll:
CacheQueriesCodeConfigurationTest.TestQueryEntityValidationWithMissingQueryAttributes
- PASSED{color}
{color:#8b}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842147]]
* {color:#013220}exe:
CacheQueriesCodeConfigurationTest.TestQueryEntityValidationWithMissingQueryAttributes
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5842172&buildTypeId=IgniteTests24Java8_RunAll])
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET (TODO: add both .NET and Java tests for this)
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl
[jira] [Updated] (IGNITE-14055) Deadlock in timeoutObjectProcessor between 'send message' & 'handshake timeout'
[
https://issues.apache.org/jira/browse/IGNITE-14055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov updated IGNITE-14055:
---
Summary: Deadlock in timeoutObjectProcessor between 'send message' &
'handshake timeout' (was: Deadlock in timeoutObjectProcessor between 'send
messag'e & 'handshake timeout')
> Deadlock in timeoutObjectProcessor between 'send message' & 'handshake
> timeout'
> ---
>
> Key: IGNITE-14055
> URL: https://issues.apache.org/jira/browse/IGNITE-14055
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Attachments: StartServerWithTxPuts (1).java, freeze (1).sh
>
>
> Cluster hangs after jvm pauses on one of server nodes.
> Scenario:
> 1. Start three server nodes with put operations using StartServerWithTxPuts.
> 2. Emulate jvm freezes on one server node by running the attached script:
> {{*sh freeze.sh *}}
> 3. Wait until the script has finished.
> Result:
> The cluster hangs on tx put operations.
> The first server node continuously prints:
> {noformat}
> [2020-11-03 09:36:01,719][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57714][2020-11-03 09:36:01,720][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:01,922][INFO
> ][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57716][2020-11-03 09:36:01,922][INFO
> ][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,124][INFO
> ][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57718][2020-11-03 09:36:02,125][INFO
> ][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,326][INFO
> ][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57720][2020-11-03 09:36:02,327][INFO
> ][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,528][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57722][2020-11-03 09:36:02,529][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3]}}
> {noformat}
> The second node prints long running transactions in prepared state ignoring
> the default tx timeout:
>
> {noformat}
> [2020-11-03 09:36:46,199][WARN
> ][sys-#83%56b4f715-82d6-4d63-ba99-441ffcd673b4%][diagnostic] >>> Future
> [startTime=09:33:08.496, curTime=09:36:46.181, fut=GridNearTxFinishFuture
> [futId=425decc8571-4ce98554-8c56-4daf-a7a9-5b9bff52fa08, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=LinkedHashSet [IgniteTxEntry [txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [part=833, val=833, hasValBytes=true],
> cacheId=-923393186], val=TxEntryValueHolder [val=CacheObjectByteArrayImpl
> [arrLen=1048576], op=CREATE], prevVal=TxEntryValueHolder [val=null, op=NOOP],
> oldVal=TxEntryValueHolder [val=null, op=NOOP], entryProcessorsCol=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=CacheEntryPredicate[] [], filter
[jira] [Updated] (IGNITE-14055) Deadlock in timeoutObjectProcessor between 'send messag'e & 'handshake timeout'
[
https://issues.apache.org/jira/browse/IGNITE-14055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov updated IGNITE-14055:
---
Attachment: StartServerWithTxPuts (1).java
> Deadlock in timeoutObjectProcessor between 'send messag'e & 'handshake
> timeout'
> ---
>
> Key: IGNITE-14055
> URL: https://issues.apache.org/jira/browse/IGNITE-14055
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Attachments: StartServerWithTxPuts (1).java, freeze (1).sh
>
>
> Cluster hangs after jvm pauses on one of server nodes.
> Scenario:
> 1. Start three server nodes with put operations using StartServerWithTxPuts.
> 2. Emulate jvm freezes on one server node by running the attached script:
> {{*sh freeze.sh *}}
> 3. Wait until the script has finished.
> Result:
> The cluster hangs on tx put operations.
> The first server node continuously prints:
> {noformat}
> [2020-11-03 09:36:01,719][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57714][2020-11-03 09:36:01,720][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:01,922][INFO
> ][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57716][2020-11-03 09:36:01,922][INFO
> ][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,124][INFO
> ][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57718][2020-11-03 09:36:02,125][INFO
> ][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,326][INFO
> ][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57720][2020-11-03 09:36:02,327][INFO
> ][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,528][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57722][2020-11-03 09:36:02,529][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3]}}
> {noformat}
> The second node prints long running transactions in prepared state ignoring
> the default tx timeout:
>
> {noformat}
> [2020-11-03 09:36:46,199][WARN
> ][sys-#83%56b4f715-82d6-4d63-ba99-441ffcd673b4%][diagnostic] >>> Future
> [startTime=09:33:08.496, curTime=09:36:46.181, fut=GridNearTxFinishFuture
> [futId=425decc8571-4ce98554-8c56-4daf-a7a9-5b9bff52fa08, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=LinkedHashSet [IgniteTxEntry [txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [part=833, val=833, hasValBytes=true],
> cacheId=-923393186], val=TxEntryValueHolder [val=CacheObjectByteArrayImpl
> [arrLen=1048576], op=CREATE], prevVal=TxEntryValueHolder [val=null, op=NOOP],
> oldVal=TxEntryValueHolder [val=null, op=NOOP], entryProcessorsCol=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=CacheEntryPredicate[] [], filtersPassed=false,
> filtersSet=true, entry=GridDhtDetachedCacheEntry
> [super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=
[jira] [Updated] (IGNITE-14055) Deadlock in timeoutObjectProcessor between 'send messag'e & 'handshake timeout'
[
https://issues.apache.org/jira/browse/IGNITE-14055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov updated IGNITE-14055:
---
Attachment: freeze (1).sh
> Deadlock in timeoutObjectProcessor between 'send messag'e & 'handshake
> timeout'
> ---
>
> Key: IGNITE-14055
> URL: https://issues.apache.org/jira/browse/IGNITE-14055
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Attachments: StartServerWithTxPuts (1).java, freeze (1).sh
>
>
> Cluster hangs after jvm pauses on one of server nodes.
> Scenario:
> 1. Start three server nodes with put operations using StartServerWithTxPuts.
> 2. Emulate jvm freezes on one server node by running the attached script:
> {{*sh freeze.sh *}}
> 3. Wait until the script has finished.
> Result:
> The cluster hangs on tx put operations.
> The first server node continuously prints:
> {noformat}
> [2020-11-03 09:36:01,719][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57714][2020-11-03 09:36:01,720][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:01,922][INFO
> ][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57716][2020-11-03 09:36:01,922][INFO
> ][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,124][INFO
> ][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57718][2020-11-03 09:36:02,125][INFO
> ][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,326][INFO
> ][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57720][2020-11-03 09:36:02,327][INFO
> ][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
> 09:36:02,528][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
> rmtAddr=/127.0.0.1:57722][2020-11-03 09:36:02,529][INFO
> ][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
> Received incoming connection from remote node while connecting to this node,
> rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
> rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3]}}
> {noformat}
> The second node prints long running transactions in prepared state ignoring
> the default tx timeout:
>
> {noformat}
> [2020-11-03 09:36:46,199][WARN
> ][sys-#83%56b4f715-82d6-4d63-ba99-441ffcd673b4%][diagnostic] >>> Future
> [startTime=09:33:08.496, curTime=09:36:46.181, fut=GridNearTxFinishFuture
> [futId=425decc8571-4ce98554-8c56-4daf-a7a9-5b9bff52fa08, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=LinkedHashSet [IgniteTxEntry [txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [part=833, val=833, hasValBytes=true],
> cacheId=-923393186], val=TxEntryValueHolder [val=CacheObjectByteArrayImpl
> [arrLen=1048576], op=CREATE], prevVal=TxEntryValueHolder [val=null, op=NOOP],
> oldVal=TxEntryValueHolder [val=null, op=NOOP], entryProcessorsCol=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=CacheEntryPredicate[] [], filtersPassed=false,
> filtersSet=true, entry=GridDhtDetachedCacheEntry
> [super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImp
[jira] [Updated] (IGNITE-14055) Deadlock in timeoutObjectProcessor between 'send messag'e & 'handshake timeout'
[
https://issues.apache.org/jira/browse/IGNITE-14055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov updated IGNITE-14055:
---
Description:
Cluster hangs after jvm pauses on one of server nodes.
Scenario:
1. Start three server nodes with put operations using StartServerWithTxPuts.
2. Emulate jvm freezes on one server node by running the attached script:
{{*sh freeze.sh *}}
3. Wait until the script has finished.
Result:
The cluster hangs on tx put operations.
The first server node continuously prints:
{noformat}
[2020-11-03 09:36:01,719][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57714][2020-11-03 09:36:01,720][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:01,922][INFO
][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57716][2020-11-03 09:36:01,922][INFO
][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:02,124][INFO
][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57718][2020-11-03 09:36:02,125][INFO
][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:02,326][INFO
][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57720][2020-11-03 09:36:02,327][INFO
][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:02,528][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57722][2020-11-03 09:36:02,529][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3]}}
{noformat}
The second node prints long running transactions in prepared state ignoring
the default tx timeout:
{noformat}
[2020-11-03 09:36:46,199][WARN
][sys-#83%56b4f715-82d6-4d63-ba99-441ffcd673b4%][diagnostic] >>> Future
[startTime=09:33:08.496, curTime=09:36:46.181, fut=GridNearTxFinishFuture
[futId=425decc8571-4ce98554-8c56-4daf-a7a9-5b9bff52fa08, tx=GridNearTxLocal
[mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
[entries=LinkedHashSet [IgniteTxEntry [txKey=IgniteTxKey
[key=KeyCacheObjectImpl [part=833, val=833, hasValBytes=true],
cacheId=-923393186], val=TxEntryValueHolder [val=CacheObjectByteArrayImpl
[arrLen=1048576], op=CREATE], prevVal=TxEntryValueHolder [val=null, op=NOOP],
oldVal=TxEntryValueHolder [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1,
conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
[super=GridCacheMapEntry [key=KeyCacheObjectImpl [part=833, val=833,
hasValBytes=true], val=null, ver=GridCacheVersion [topVer=0, order=0,
nodeOrder=0], hash=833, extras=null, flags=0]]], prepared=0, locked=false,
nodeId=07583a9d-36c8-4100-a69c-8cbd26ca82c9, locMapped=false, expiryPlc=null,
transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
xidVer=GridCacheVersion [topVer=215865159, order=1604385188157, nodeOrder=2]]],
explicitLock=false, queryUpdate=false, dhtVer=null, last=false, nearEntries=0,
clientFirst=false, node=07583a9d-36c8-4100-a69c-8cbd26ca82c9]],
nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null,
hasRemoteLocks=false, trackTimeout=false, sys
[jira] [Created] (IGNITE-14055) Deadlock in timeoutObjectProcessor between 'send messag'e & 'handshake timeout'
Anton Kalashnikov created IGNITE-14055:
--
Summary: Deadlock in timeoutObjectProcessor between 'send messag'e
& 'handshake timeout'
Key: IGNITE-14055
URL: https://issues.apache.org/jira/browse/IGNITE-14055
Project: Ignite
Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov
Cluster hangs after jvm pauses on one of server nodes.
Scenario:
1. Start three server nodes with put operations using StartServerWithTxPuts.
2. Emulate jvm freezes on one server node by running the attached script:
{{*sh freeze.sh *}}
3. Wait until the script has finished.
Result:
The cluster hangs on tx put operations.
The first server node continuously prints:
{{{noformat}}}
{{}}{{[2020-11-03 09:36:01,719][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57714][2020-11-03 09:36:01,720][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:01,922][INFO
][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57716][2020-11-03 09:36:01,922][INFO
][grid-nio-worker-tcp-comm-0-#23%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:02,124][INFO
][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57718][2020-11-03 09:36:02,125][INFO
][grid-nio-worker-tcp-comm-1-#24%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:02,326][INFO
][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57720][2020-11-03 09:36:02,327][INFO
][grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3][2020-11-03
09:36:02,528][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:47100,
rmtAddr=/127.0.0.1:57722][2020-11-03 09:36:02,529][INFO
][grid-nio-worker-tcp-comm-3-#26%TcpCommunicationSpi%][TcpCommunicationSpi]
Received incoming connection from remote node while connecting to this node,
rejecting [locNode=5defd32f-5bdb-4b9e-8a6e-5ee268edac42, locNodeOrder=1,
rmtNode=07583a9d-36c8-4100-a69c-8cbd26ca82c9, rmtNodeOrder=3]}}
{{{noformat}}}{{}}
The second node prints long running transactions in prepared state ignoring the
default tx timeout:
{{{noformat}}}
{{1}}{{[2020-11-03 09:36:46,199][WARN
][sys-#83%56b4f715-82d6-4d63-ba99-441ffcd673b4%][diagnostic] >>> Future
[startTime=09:33:08.496, curTime=09:36:46.181, fut=GridNearTxFinishFuture
[futId=425decc8571-4ce98554-8c56-4daf-a7a9-5b9bff52fa08, tx=GridNearTxLocal
[mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
[entries=LinkedHashSet [IgniteTxEntry [txKey=IgniteTxKey
[key=KeyCacheObjectImpl [part=833, val=833, hasValBytes=true],
cacheId=-923393186], val=TxEntryValueHolder [val=CacheObjectByteArrayImpl
[arrLen=1048576], op=CREATE], prevVal=TxEntryValueHolder [val=null, op=NOOP],
oldVal=TxEntryValueHolder [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1,
conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
[super=GridCacheMapEntry [key=KeyCacheObjectImpl [part=833, val=833,
hasValBytes=true], val=null, ver=GridCacheVersion [topVer=0, order=0,
nodeOrder=0], hash=833, extras=null, flags=0]]], prepared=0, locked=false,
nodeId=07583a9d-36c8-4100-a69c-8cbd26ca82c9, locMapped=false, expiryPlc=null,
transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
xidVer=GridCacheVersion [topVer=215865159, order=1604385188157, nodeOrder=2]]],
explicitLock=false, queryUpdate=false, dhtVer=n
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271269#comment-17271269 ] Kirill Tkalenko commented on IGNITE-13912: -- Hi, [~mmuzaf]! The Root cause has not yet been clarified so that it can be repaired. > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: reproducer.zip, server1-full-wal-checkpoint.log, > wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, > wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, > wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14053) Remove status check message at all.
[ https://issues.apache.org/jira/browse/IGNITE-14053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14053: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Remove status check message at all. > --- > > Key: IGNITE-14053 > URL: https://issues.apache.org/jira/browse/IGNITE-14053 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14054) Improve discovery ducktest: add partial network drop.
[ https://issues.apache.org/jira/browse/IGNITE-14054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14054: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Improve discovery ducktest: add partial network drop. > - > > Key: IGNITE-14054 > URL: https://issues.apache.org/jira/browse/IGNITE-14054 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271267#comment-17271267 ] Maxim Muzafarov commented on IGNITE-13912: -- [~ktkale...@gridgain.com], [~shm] Folks, I've read this thread but it seems I haven't got the result. Is the above issue fixed in the provided patch? > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: reproducer.zip, server1-full-wal-checkpoint.log, > wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, > wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, > wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13895) SSL usage in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-13895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergei Ryzhov updated IGNITE-13895:
---
Description:
SSL usage in ducktape tests
Necessary:
- server, client and admin must connect with different certificates.
- be able to enable ssl for all tests via globals.
- be able to set the ssl parameters for tests via globals.
certificates are generated at startup ./run-test.sh
{code}
Root
- CA
- Server
- Client
- Admin
{code}
for run all tests with ssl you may use globals:
{code}
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True", "ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True","server": {"key_store_jks": "admin.jks"}, "client":
{"key_store_jks": "admin.jks"}, "admin": {"key_store_jks": "client.jks"},
"ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/ssl_test.py -gj
'{"use_ssl":"True","server": {"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "client":
{"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "admin":
{"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/client.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}}'
{code}
was:
SSL usage in ducktape tests
Necessary:
- server, client and admin must connect with different certificates.
- be able to enable ssl for all tests via globals.
- be able to set the ssl parameters for tests via globals.
certificates are generated at startup ./run-test.sh
{code}
Root
- CA
- Server
- Client
- Admin
{code}
for run all tests with ssl you may use globals:
{code}
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True", "ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True","server": {"key_store_jks": "admin.jks"}, "client":
{"key_store_jks": "admin.jks"}, "admin": {"key_store_jks": "client.jks"},
"ignite_versions":"2.9.0"}'
{code}
> SSL usage in ducktape tests
> ---
>
> Key: IGNITE-13895
> URL: https://issues.apache.org/jira/browse/IGNITE-13895
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> SSL usage in ducktape tests
> Necessary:
> - server, client and admin must connect with different certificates.
> - be able to enable ssl for all tests via globals.
> - be able to set the ssl parameters for tests via globals.
> certificates are generated at startup ./run-test.sh
> {code}
> Root
> - CA
>- Server
>- Client
>- Admin
> {code}
> for run all tests with ssl you may use globals:
> {code}
> ./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
> '{"use_ssl":"True", "ignite_versions":"2.9.0"}'
> ./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
> '{"use_ssl":"True","server": {"key_store_jks": "admin.jks"}, "client":
> {"key_store_jks": "admin.jks"}, "admin": {"key_store_jks": "client.jks"},
> "ignite_versions":"2.9.0"}'
> ./docker/run_tests.sh -t ./ignitetest/tests/ssl_test.py -gj
> '{"use_ssl":"True","server": {"key_store_path":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
> "trust_store_jks":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"},
> "client": {"key_store_path":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
> "trust_store_jks":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "admin":
> {"key_store_path":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/client.jks",
> "trust_store_jks":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14054) Improve discovery ducktest: add partial network drop.
Vladimir Steshin created IGNITE-14054: - Summary: Improve discovery ducktest: add partial network drop. Key: IGNITE-14054 URL: https://issues.apache.org/jira/browse/IGNITE-14054 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13895) SSL usage in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-13895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergei Ryzhov updated IGNITE-13895:
---
Description:
SSL usage in ducktape tests
Necessary:
- server, client and admin must connect with different certificates.
- be able to enable ssl for all tests via globals.
- be able to set the ssl parameters for tests via globals.
certificates are generated at startup ./run-test.sh
{code}
Root
- CA
- Server
- Client
- Admin
{code}
for run all tests with ssl you may use globals:
{code}
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True", "ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True","server": {"key_store_jks": "admin.jks"}, "client":
{"key_store_jks": "admin.jks"}, "admin": {"key_store_jks": "client.jks"},
"ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/ssl_test.py -gj
'{"use_ssl":"True","server": {"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "client":
{"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "admin":
{"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/client.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}}'
{code}
was:
SSL usage in ducktape tests
Necessary:
- server, client and admin must connect with different certificates.
- be able to enable ssl for all tests via globals.
- be able to set the ssl parameters for tests via globals.
certificates are generated at startup ./run-test.sh
{code}
Root
- CA
- Server
- Client
- Admin
{code}
for run all tests with ssl you may use globals:
{code}
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True", "ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
'{"use_ssl":"True","server": {"key_store_jks": "admin.jks"}, "client":
{"key_store_jks": "admin.jks"}, "admin": {"key_store_jks": "client.jks"},
"ignite_versions":"2.9.0"}'
./docker/run_tests.sh -t ./ignitetest/tests/ssl_test.py -gj
'{"use_ssl":"True","server": {"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "client":
{"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "admin":
{"key_store_path":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/client.jks",
"trust_store_jks":
"/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}}'
{code}
> SSL usage in ducktape tests
> ---
>
> Key: IGNITE-13895
> URL: https://issues.apache.org/jira/browse/IGNITE-13895
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> SSL usage in ducktape tests
> Necessary:
> - server, client and admin must connect with different certificates.
> - be able to enable ssl for all tests via globals.
> - be able to set the ssl parameters for tests via globals.
> certificates are generated at startup ./run-test.sh
> {code}
> Root
> - CA
>- Server
>- Client
>- Admin
> {code}
> for run all tests with ssl you may use globals:
> {code}
> ./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
> '{"use_ssl":"True", "ignite_versions":"2.9.0"}'
> ./docker/run_tests.sh -t ./ignitetest/tests/self_test.py -gj
> '{"use_ssl":"True","server": {"key_store_jks": "admin.jks"}, "client":
> {"key_store_jks": "admin.jks"}, "admin": {"key_store_jks": "client.jks"},
> "ignite_versions":"2.9.0"}'
> ./docker/run_tests.sh -t ./ignitetest/tests/ssl_test.py -gj
> '{"use_ssl":"True","server": {"key_store_path":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
> "trust_store_jks":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"},
> "client": {"key_store_path":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/admin.jks",
> "trust_store_jks":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}, "admin":
> {"key_store_path":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/client.jks",
> "trust_store_jks":
> "/opt/ignite-dev/modules/ducktests/tests/other_dir/truststore.jks"}}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13970) [Ducktape: Thin client] Cache API Test
[ https://issues.apache.org/jira/browse/IGNITE-13970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13970: -- Description: Need to check put/get (atomic, tx) and other cache API works while the user uses TC. +jinja2 based spring configuration. was:Need to check put/get (atomic, tx) and other cache API works while the user uses TC. > [Ducktape: Thin client] Cache API Test > -- > > Key: IGNITE-13970 > URL: https://issues.apache.org/jira/browse/IGNITE-13970 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Evgeniya Vdovets >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Need to check put/get (atomic, tx) and other cache API works while the user > uses TC. > +jinja2 based spring configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14046) Update ducktape version to 0.8.2 in ignite-ducktape module
[ https://issues.apache.org/jira/browse/IGNITE-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14046: -- Description: + 11 java at docker + background service > Update ducktape version to 0.8.2 in ignite-ducktape module > -- > > Key: IGNITE-14046 > URL: https://issues.apache.org/jira/browse/IGNITE-14046 > Project: Ignite > Issue Type: Task >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Critical > > + 11 java at docker > + background service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13446) Configs inside Ducktests logs should be pretty printed
[
https://issues.apache.org/jira/browse/IGNITE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-13446:
--
Sprint: Ducktape Sprint 1
> Configs inside Ducktests logs should be pretty printed
> --
>
> Key: IGNITE-13446
> URL: https://issues.apache.org/jira/browse/IGNITE-13446
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov (Obsolete, actual is "av")
>Assignee: Sergei Ryzhov
>Priority: Critical
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, I see the following inside the logs
> {code}
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>
> http://www.springframework.org/schema/beans/spring-beans.xsd";>
>
>
>
>
> value="/mnt/service/ignite-log4j.xml"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
>
> ducker02
>
> ducker03
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction">
>
> class="org.apache.ignite.internal.ducktest.tests.cellular_affinity_test.CellularAffinityBackupFilter">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14046) Update ducktape version to 0.8.2 in ignite-ducktape module
[ https://issues.apache.org/jira/browse/IGNITE-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14046: -- Sprint: Ducktape Sprint 1 > Update ducktape version to 0.8.2 in ignite-ducktape module > -- > > Key: IGNITE-14046 > URL: https://issues.apache.org/jira/browse/IGNITE-14046 > Project: Ignite > Issue Type: Task >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14046) Update ducktape version to 0.8.2 in ignite-ducktape module
[ https://issues.apache.org/jira/browse/IGNITE-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-14046: - Assignee: Ivan Daschinskiy > Update ducktape version to 0.8.2 in ignite-ducktape module > -- > > Key: IGNITE-14046 > URL: https://issues.apache.org/jira/browse/IGNITE-14046 > Project: Ignite > Issue Type: Task >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13980) Remove duplicated ping: processing and raising StatusCheckMessage.
[ https://issues.apache.org/jira/browse/IGNITE-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13980: -- Summary: Remove duplicated ping: processing and raising StatusCheckMessage. (was: Remove duplicated ping: status check message.) > Remove duplicated ping: processing and raising StatusCheckMessage. > -- > > Key: IGNITE-13980 > URL: https://issues.apache.org/jira/browse/IGNITE-13980 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14027) Switching Auto-adjust on does not trigger including existent nodes(which are not in BLT) to the BLT
[
https://issues.apache.org/jira/browse/IGNITE-14027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271261#comment-17271261
]
Ignite TC Bot commented on IGNITE-14027:
{panel:title=Branch: [pull/8679/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8679/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5838582]]
* {color:#013220}IgniteBasicTestSuite:
BaselineAutoAdjustTest.testJoinBltExistingNode - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
BaselineAutoAdjustInMemoryTest.testJoinBltExistingNode - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5838642&buildTypeId=IgniteTests24Java8_RunAll]
> Switching Auto-adjust on does not trigger including existent nodes(which are
> not in BLT) to the BLT
> ---
>
> Key: IGNITE-14027
> URL: https://issues.apache.org/jira/browse/IGNITE-14027
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.9.1
>Reporter: Semyon Danilov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> * Start cluster with AA on
> * Disable AA
> * Start new node - it joins topology, not the BL
> * Enable AA
> Expected:
> * As _softTimeout_ passes, the node joins the BLT
> Actual:
> * The node remains out of BLT
> With that new note won't join BLT until either another new node started or AA
> disabled and the node is included in the BLT manually
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14053) Remove status check message at all.
Vladimir Steshin created IGNITE-14053: - Summary: Remove status check message at all. Key: IGNITE-14053 URL: https://issues.apache.org/jira/browse/IGNITE-14053 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13973) Calcite integration. Query get frozen if assertion error was thrown
[
https://issues.apache.org/jira/browse/IGNITE-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reassigned IGNITE-13973:
-
Assignee: Konstantin Orlov
> Calcite integration. Query get frozen if assertion error was thrown
> ---
>
> Key: IGNITE-13973
> URL: https://issues.apache.org/jira/browse/IGNITE-13973
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Critical
>
> Need to fix the issue and verify that assertion error on any stage of query
> planning/execution (this includes fragment splitting, serialisation and
> deserialisation phases) doesn't lead to freezes.
> Mentioned problem could be reproduced for example as follow:
> 1) place fake {{assert false}} inside {{IgniteMergeJoin(RelInput input)}}
> 2) run {{CalciteQueryProcessorTest.query2()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13687: - Fix Version/s: 2.11 > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14047) .NET: Release build fails because of missing nuget executable
[
https://issues.apache.org/jira/browse/IGNITE-14047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271255#comment-17271255
]
Ignite TC Bot commented on IGNITE-14047:
{panel:title=Branch: [pull/8695/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5842236]]
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842241]]
* IgniteCacheTestSuite7:
TransactionIntegrityWithPrimaryIndexCorruptionTest.testPrimaryIndexCorruptionDuringCommitBackupColocatedThrowsChecked
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5842277]]
{color:#d04437}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842201]]
* ClientTestSuite: ServicesTest.testServiceTimeout - Test has low fail rate in
base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8695/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5842279&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Release build fails because of missing nuget executable
> -
>
> Key: IGNITE-14047
> URL: https://issues.apache.org/jira/browse/IGNITE-14047
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NuGet executable is not downloaded when {{-skipNuGet}} is specified, but it
> is required for .NET Framework build.
> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_ApacheIgniteNightlyReleaseBuildNetCpp/5838928?buildTab=log&focusLine=3&linesState=805
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271254#comment-17271254 ] Kirill Tkalenko commented on IGNITE-13912: -- Hi, [~shm]! Re-producer should look like a test that can be easily run on an open project. I have no experience with running k8s, so I cannot run the test. It seems that in the beginning you can figure out why the PME(exchange) happens. > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: reproducer.zip, server1-full-wal-checkpoint.log, > wal-checkpoint-logs, wal_dir_contents, wal_grows_from_peak.PNG, > wal_issue_reproduced.PNG, wal_usage.PNG, wal_usage_dec12.PNG, > wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13957) GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value when QueryEntity.fields is not set
[
https://issues.apache.org/jira/browse/IGNITE-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271226#comment-17271226
]
Ignite TC Bot commented on IGNITE-13957:
{panel:title=Branch: [pull/8694/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842109]]
* ZookeeperDiscoverySpiTestSuite1: ZookeeperClientTest.testConnectionLoss4 -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5842091]]
{color:#d04437}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842094]]
* ClientTestSuite: ComputeTaskTest.testExecuteTaskConcurrentLoad - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842146]]
* IgnitePdsTestSuite4:
RebalanceCancellationTest.testRebalanceDynamicCacheOnMixedCluster - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8694/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842148]]
* {color:#013220}dll:
CacheQueriesCodeConfigurationTest.TestQueryEntityValidationWithMissingQueryAttributes
- PASSED{color}
{color:#8b}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5842147]]
* {color:#013220}exe:
CacheQueriesCodeConfigurationTest.TestQueryEntityValidationWithMissingQueryAttributes
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5842172&buildTypeId=IgniteTests24Java8_RunAll]
> GridQueryProcessor.validateKeyAndValue attempts to deserialize key and value
> when QueryEntity.fields is not set
> ---
>
> Key: IGNITE-13957
> URL: https://issues.apache.org/jira/browse/IGNITE-13957
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.9, 2.9.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridQueryProcessor.validateKeyAndValue}} attempts to deserialize cache key
> and value on {{put}} when {{QueryEntity.fields}} is not set, and fails when
> corresponding classes can't be found.
> * The bug was introduced in 2.9
> * There is no problem when some query entity fields are defined
> Reproducer in .NET (TODO: add both .NET and Java tests for this)
> {code}
> // CacheQueriesCodeConfigurationTest
> ///
> /// Tests query entity validation when no cref="QuerySqlFieldAttribute"/> has been set.
> ///
> [Test]
> public void TestMissingQueryAttributes()
> {
> using (var ignite =
> Ignition.Start(TestUtils.GetTestConfiguration()))
> {
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(string),
> typeof(MissingAttributesTest)));
> var cache = ignite.GetOrCreateCache MissingAttributesTest>(cfg);
> cache["1"] = new MissingAttributesTest {Foo = "Bar"};
> }
> }
> ///
> /// Class without any attributes.
> ///
> private class MissingAttributesTest
> {
> /** */
> public string Foo { get; set; }
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Cache.CacheException : class
> org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.IgniteException : Failed to resolve .NET
> class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> > Apache.Ignite.Core.Common.JavaException : javax.cache.CacheException:
> class org.apache.ignite.IgniteCheckedException: Failed to resolve .NET class
> 'Apache.Ignite.Core.Tests.Cache.Query.CacheQueriesCodeConfigurationTest+MissingAttributesTest'
> in Java [platformId=0, typeId=1242226865].
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1263)
> at
> org.apache.ignite.internal.processors.cac
[jira] [Comment Edited] (IGNITE-13999) Switch to SHA-512 for jar checksum calculation.
[ https://issues.apache.org/jira/browse/IGNITE-13999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271223#comment-17271223 ] Peter Ivanov edited comment on IGNITE-13999 at 1/25/21, 10:22 AM: -- Currently it seem to be impossible to create sha512 hashsums other than use custom code, which leads to uncertainty in goal — where we really should do it now. Infra team is asked for possible solutions: https://issues.apache.org/jira/browse/INFRA-21336 For now, ticket is on pause until further information available. was (Author: vveider): Currently it seem to be impossible to create sha512 hashsums other than use custom code. Infra team is asked for possible solutions: https://issues.apache.org/jira/browse/INFRA-21336 For now, ticket is on pause until further information available. > Switch to SHA-512 for jar checksum calculation. > --- > > Key: IGNITE-13999 > URL: https://issues.apache.org/jira/browse/IGNITE-13999 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Andrey Mashenkov >Assignee: Peter Ivanov >Priority: Major > Labels: ignite-3 > > maven-deploy-plugin is responsible for signing jar. However, it seems SHA-1 > is hardcoded there. > In the latest apache parent pom (org.apache:apache:23) a > checksum-maven-plugin is used as a workaround to sign jars with SHA-512. But > it signs only source jar and do not affect binary jar. -- This message was sent by Atlassian Jira (v8.3.4#803005)
