[jira] [Commented] (IGNITE-12175) ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
[
https://issues.apache.org/jira/browse/IGNITE-12175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931923#comment-16931923
]
Richard Crossley commented on IGNITE-12175:
---
Hi,
I raised the original question on Stack Overflow.
I have added my test case script and the Python traceback that is produced.
Python version: 3.6.8
> ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
> -
>
> Key: IGNITE-12175
> URL: https://issues.apache.org/jira/browse/IGNITE-12175
> Project: Ignite
> Issue Type: Improvement
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Priority: Major
> Attachments: Python_Traceback.txt, main.py
>
>
> Subj:
> pyodbc.Error: ('HYC00', '[HYC00] Data type is not supported. [typeId=-9] (0)
> (SQLBindParameter)')
> https://stackoverflow.com/questions/57971252/python-string-to-varchar-mapping-using-odbc-with-apache-ignite-not-supported/57973839#57973839
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12175) ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
[
https://issues.apache.org/jira/browse/IGNITE-12175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Crossley updated IGNITE-12175:
--
Attachment: main.py
> ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
> -
>
> Key: IGNITE-12175
> URL: https://issues.apache.org/jira/browse/IGNITE-12175
> Project: Ignite
> Issue Type: Improvement
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Priority: Major
> Attachments: Python_Traceback.txt, main.py
>
>
> Subj:
> pyodbc.Error: ('HYC00', '[HYC00] Data type is not supported. [typeId=-9] (0)
> (SQLBindParameter)')
> https://stackoverflow.com/questions/57971252/python-string-to-varchar-mapping-using-odbc-with-apache-ignite-not-supported/57973839#57973839
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12175) ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
[
https://issues.apache.org/jira/browse/IGNITE-12175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Crossley updated IGNITE-12175:
--
Attachment: Python_Traceback.txt
> ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
> -
>
> Key: IGNITE-12175
> URL: https://issues.apache.org/jira/browse/IGNITE-12175
> Project: Ignite
> Issue Type: Improvement
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Priority: Major
> Attachments: Python_Traceback.txt
>
>
> Subj:
> pyodbc.Error: ('HYC00', '[HYC00] Data type is not supported. [typeId=-9] (0)
> (SQLBindParameter)')
> https://stackoverflow.com/questions/57971252/python-string-to-varchar-mapping-using-odbc-with-apache-ignite-not-supported/57973839#57973839
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.
[
https://issues.apache.org/jira/browse/IGNITE-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931911#comment-16931911
]
Amelchev Nikita commented on IGNITE-12027:
--
[~NIzhikov], thank you for review. Visa is ok.
> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
> at
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap =
> ctx.topology().partitionMap(false);}} is null.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.
[
https://issues.apache.org/jira/browse/IGNITE-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931903#comment-16931903
]
Ignite TC Bot commented on IGNITE-12027:
{panel:title=Branch: [pull/6738/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4606238buildTypeId=IgniteTests24Java8_RunAll]
> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
> at
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap =
> ctx.topology().partitionMap(false);}} is null.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931735#comment-16931735
]
Pavel Tupitsyn commented on IGNITE-12176:
-
[~ashapkin] good point, mentioned in commit message.
Merged to master: cce9cc4fc03142a35059f7526a3e53814662c8e9
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
>
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
>
>
>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-11461: --- Assignee: (was: Dmitriy Pavlov) > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > This type of failure is named package inference, but it is strictly > prohibited > http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Following table contains currenly investigated Ignite modules if this > applicability as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > Notes || > |ignite-code|(/)|(/)| | > |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use > ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is > required by user manually. | > |ignite-compress | (x) | (/) not releaseed | > org.apache.ignite.internal.processors.compress package conflict | > |ignite-direct-io|(x) blocked by indexind | (/) | > org.apache.ignite.internal.processors.cache.persistence.file package conflict > | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected | | > |ignite-ml |(x) blocked by indexing | | | > |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - > EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| | > |ignite-slf4j | (/)|(/)| | > |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | > (/) | Usage with slf4j may break compilation because conflict of packages | > |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API > breaking is possibleif hibernate core classes not used by third party code | > |ignite-zookeeper| (x) IGNITE-11486 | (/) | | > |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging > from both commons.logging and spring.jcl conflict | > https://jira.spring.io/browse/SPR-16605 | > |ignite-ml | (/) master (x) 2.7 | | | > |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | (/) | > Only spring needs to be fixed | -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts
[
https://issues.apache.org/jira/browse/IGNITE-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-11464:
---
Assignee: (was: Dmitriy Pavlov)
> Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix
> queries and visor package conflicts
>
>
> Key: IGNITE-11464
> URL: https://issues.apache.org/jira/browse/IGNITE-11464
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> error: the unnamed module reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: the unnamed module reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: the unnamed module reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
>
> C:\projects\incubator-ignite\modules\dev-utils\ignite-modules-test\src\test\java\module-info.java:18:
> error: module ignite_modules_test reads package org.apache.lucene.search
> from both lucene.sandbox and lucene.core
> module ignite_modules_test
> {noformat}
>
> Some of these errors probably can be fixed by workarounds for dependencies:
> 2 errors coming from duplicate packages declared in code and indexing:
> - error: module ignite.core reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> - error: module ignite.core reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-7182) Slow sorting of pages collection on checkpoint begin can cause zero dropdown even with throttling enabled
[
https://issues.apache.org/jira/browse/IGNITE-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov resolved IGNITE-7182.
Fix Version/s: (was: 2.8)
Resolution: Won't Fix
Benchmarking does not show any performance boost from another sorting
> Slow sorting of pages collection on checkpoint begin can cause zero dropdown
> even with throttling enabled
> -
>
> Key: IGNITE-7182
> URL: https://issues.apache.org/jira/browse/IGNITE-7182
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Affects Versions: 2.3
>Reporter: Ivan Rakov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> Tests show that GridCacheDatabaseSharedManager#splitAndSortCpPagesIfNeeded
> call can last several seconds on nodes with big amount of memory (>10GB). We
> should optimize sorting algorithm, possibly making it multithreaded.
> Another option to make pages write throttling more smooth is to get rid of
> this heuristic:
> {noformat}
> // Starting with 0.05 to avoid throttle right after
> checkpoint start
> // 7/12 is maximum ratio of dirty pages
> dirtyRatioThreshold = (dirtyRatioThreshold * 0.95 + 0.05) * 7
> / 12;
> {noformat}
> We should replace "magic" lower bound 0.05 * 7 / 12 with the real percentage
> of dirty pages at the moment of
> GridCacheDatabaseSharedManager.Checkpointer#markCheckpointBegin call return.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-7584) Smooth decrease WAL write speed if low work segments left
[ https://issues.apache.org/jira/browse/IGNITE-7584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-7584. Fix Version/s: (was: 2.8) Resolution: Won't Fix > Smooth decrease WAL write speed if low work segments left > - > > Key: IGNITE-7584 > URL: https://issues.apache.org/jira/browse/IGNITE-7584 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > Smooth decrease of the write speed in WAL when approaching the exhaustion of > current segments in the working directory. > Now archiver segment switch involves file copying and may be bottleneck of > speed of grid operation. > Now if out of work segments occurs, grid put speed drop down to 0 ops/sec > ocurred. > This isssue was fixed under IGNITE-7017 with providing new 'NoArchvier' mode, > but in case archiver based WAL is already used by end-user, it is required to > have opportunity to smooth decrease speed instead of drop to 0. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12122) Remove setIncludeEventTypes from GridAbstractTest.
[ https://issues.apache.org/jira/browse/IGNITE-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931687#comment-16931687 ] Maxim Muzafarov commented on IGNITE-12122: -- [~zstan], I'll take a look > Remove setIncludeEventTypes from GridAbstractTest. > -- > > Key: IGNITE-12122 > URL: https://issues.apache.org/jira/browse/IGNITE-12122 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7.5 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Attachments: 6825_res.ods, flamegraph-18988.svg > > Time Spent: 10m > Remaining Estimate: 0h > > Simple cache.put() hot threads measurements shows that > GridCacheEventManager::addEvent consumes about 7% of overall time, i suggest > to remove this events from GridAbstractTest::getConfiguration and stores only > for really requiring tests. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions
[ https://issues.apache.org/jira/browse/IGNITE-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12181: - Attachment: RebalanceInMemoryWithPersistence.java > Rebalance hangs on BLT change on cluster with in-memory regions > --- > > Key: IGNITE-12181 > URL: https://issues.apache.org/jira/browse/IGNITE-12181 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > Attachments: RebalanceInMemoryWithPersistence.java > > > # Configured BLT on the _node-1_ (cluster activated) > # Configured in-memory region with a single cache on the _node-1_ > # A new _node-2_ join to the cluster > # Set new BLT based on two nodes > # Rebalance hangs > Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions
[ https://issues.apache.org/jira/browse/IGNITE-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12181: - Attachment: (was: RebalanceInMemoryWithPersistence.java) > Rebalance hangs on BLT change on cluster with in-memory regions > --- > > Key: IGNITE-12181 > URL: https://issues.apache.org/jira/browse/IGNITE-12181 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > Attachments: RebalanceInMemoryWithPersistence.java > > > # Configured BLT on the _node-1_ (cluster activated) > # Configured in-memory region with a single cache on the _node-1_ > # A new _node-2_ join to the cluster > # Set new BLT based on two nodes > # Rebalance hangs > Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions
[ https://issues.apache.org/jira/browse/IGNITE-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12181: - Description: # Configured BLT on the _node-1_ (cluster activated) # Configured in-memory region with a single cache on the _node-1_ # A new _node-2_ join to the cluster # Set new BLT based on two nodes # Rebalance hangs Reproducer attached. was: # Configured BLT on the _node-1_ (cluster activated) # Configured in-memory region with a single cache on the _node-1_ # A new _node-2_ join to the cluster # Set new BLT based on two nodes # Rebalance hangs > Rebalance hangs on BLT change on cluster with in-memory regions > --- > > Key: IGNITE-12181 > URL: https://issues.apache.org/jira/browse/IGNITE-12181 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > Attachments: RebalanceInMemoryWithPersistence.java > > > # Configured BLT on the _node-1_ (cluster activated) > # Configured in-memory region with a single cache on the _node-1_ > # A new _node-2_ join to the cluster > # Set new BLT based on two nodes > # Rebalance hangs > Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions
Maxim Muzafarov created IGNITE-12181: Summary: Rebalance hangs on BLT change on cluster with in-memory regions Key: IGNITE-12181 URL: https://issues.apache.org/jira/browse/IGNITE-12181 Project: Ignite Issue Type: Bug Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 Attachments: RebalanceInMemoryWithPersistence.java # Configured BLT on the _node-1_ (cluster activated) # Configured in-memory region with a single cache on the _node-1_ # A new _node-2_ join to the cluster # Set new BLT based on two nodes # Rebalance hangs -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions
[ https://issues.apache.org/jira/browse/IGNITE-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12181: - Ignite Flags: (was: Docs Required,Release Notes Required) > Rebalance hangs on BLT change on cluster with in-memory regions > --- > > Key: IGNITE-12181 > URL: https://issues.apache.org/jira/browse/IGNITE-12181 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > Attachments: RebalanceInMemoryWithPersistence.java > > > # Configured BLT on the _node-1_ (cluster activated) > # Configured in-memory region with a single cache on the _node-1_ > # A new _node-2_ join to the cluster > # Set new BLT based on two nodes > # Rebalance hangs > Reproducer attached. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.
[
https://issues.apache.org/jira/browse/IGNITE-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931656#comment-16931656
]
Nikolay Izhikov commented on IGNITE-12027:
--
LGTM. Please, obtain a bot visa one more time.
> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
> at
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap =
> ctx.topology().partitionMap(false);}} is null.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-12180) [ML] Add support of the additional Imputing Strategies
[ https://issues.apache.org/jira/browse/IGNITE-12180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-12180: -- Description: Add support of the next Imputing Strategies: MIN, MAX, COUNT, LEAST_FREQUENT (was: Add support of the next Imputing Strategies: MIN, MAX) Summary: [ML] Add support of the additional Imputing Strategies (was: [ML] Add support of the next Imputing Strategies: MIN, MAX) > [ML] Add support of the additional Imputing Strategies > -- > > Key: IGNITE-12180 > URL: https://issues.apache.org/jira/browse/IGNITE-12180 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Add support of the next Imputing Strategies: MIN, MAX, COUNT, LEAST_FREQUENT -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12180) [ML] Add support of the next Imputing Strategies: MIN, MAX
Aleksey Zinoviev created IGNITE-12180: - Summary: [ML] Add support of the next Imputing Strategies: MIN, MAX Key: IGNITE-12180 URL: https://issues.apache.org/jira/browse/IGNITE-12180 Project: Ignite Issue Type: Sub-task Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Add support of the next Imputing Strategies: MIN, MAX -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931605#comment-16931605
]
Alexandr Shapkin commented on IGNITE-12176:
---
I think it's worth to mention explicitly, that this PR also fixes some test
related issues.
For example, a TC build may get failed due to jvmClasspath being too long error.
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
>
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
>
>
>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931599#comment-16931599
]
Alexandr Shapkin commented on IGNITE-12176:
---
[~ptupitsyn] looks good, thanks!
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
>
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
>
>
>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12179) Test and javadoc fixes
Anton Kalashnikov created IGNITE-12179: -- Summary: Test and javadoc fixes Key: IGNITE-12179 URL: https://issues.apache.org/jira/browse/IGNITE-12179 Project: Ignite Issue Type: Bug Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov Some javadoc package descriptions missed: * org.apache.ignite.spi.communication.tcp.internal * org.apache.ignite.spi.discovery.zk * org.apache.ignite.spi.discovery.zk.internal * org.apache.ignite.ml.structures.partition * org.gridgain.grid.persistentstore.snapshot.file.copy Unclear CLEANUP_RESTARTING_CACHES command in snapshot utility unclear error when connecting to secure cluster (SSL + Auth) Update log message to avoid confusion for an user *.testTtlNoTx flaky failed on TC TcpCommunicationSpiFreezingClientTest failed TcpCommunicationSpiFaultyClientSslTest.testNotAcceptedConnection failed testCacheIdleVerifyPrintLostPartitions failed -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (IGNITE-9071) Failed to reinitialize local partitions on client node
[
https://issues.apache.org/jira/browse/IGNITE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kcheng.mvp reassigned IGNITE-9071:
--
Assignee: kcheng.mvp
> Failed to reinitialize local partitions on client node
> --
>
> Key: IGNITE-9071
> URL: https://issues.apache.org/jira/browse/IGNITE-9071
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: kcheng.mvp
>Priority: Minor
> Labels: newbie
> Attachments: Reproducer.java
>
>
> "Failed to reinitialize local partitions" message can confuse users when it
> appears in the client node logs:
>
> {code}
> [2018-07-25
> 12:15:58,717][ERROR][exchange-worker-#80%client-node%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (rebalancing will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=aa407026-3050-4dac-899d-cec951b3c9e5, addrs=ArrayList [10.0.75.1,
> 10.8.10.46, 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=HashSet
> [/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0,
> /10.8.10.46:0], discPort=0, order=2, intOrder=0,
> lastExchangeTime=1532492155372, loc=true, ver=2.7.0#19700101-sha1:,
> isClient=true], topVer=2, nodeId8=aa407026, msg=null, type=NODE_JOINED,
> tstamp=1532492158693], nodeId=aa407026, evt=NODE_JOINED]
> java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1090)
> at
> org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:90)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager$2.nextRegion(IgniteCacheDatabaseSharedManager.java:1026)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:628)
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931539#comment-16931539
]
Ignite TC Bot commented on IGNITE-12176:
{panel:title=Branch: [pull/6872/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4605195buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
>
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
>
>
>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12178) DEBUG logging may throw exception from toString of tx objects
Ilya Kasnacheev created IGNITE-12178:
Summary: DEBUG logging may throw exception from toString of tx
objects
Key: IGNITE-12178
URL: https://issues.apache.org/jira/browse/IGNITE-12178
Project: Ignite
Issue Type: Improvement
Components: general
Reporter: Ilya Kasnacheev
See
https://stackoverflow.com/questions/57727242/apache-ignite-failed-to-create-string-representation-of-binary-object
{code:java}
0
I am getting below exception and not able to figure out what is wrong with the
code.
I have simplified my pojo classes which are to be persisted to ignite cache,
but still the complexity remains.
All my pojos are serializable but few of them have business logic code, dao,
application context object. These objects can't be removed. Removing these
things from the code will require whole code refractoring.
class org.apache.ignite.IgniteException: Failed to create string representation
of binary object.
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1022)
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:864)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearSingleGetResponse.toString(GridNearSingleGetResponse.java:317)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1162)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1209)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:1003)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:938)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetRequest(GridDhtCacheAdapter.java:938)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$300(GridDhtAtomicCache.java:135)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$4.apply(GridDhtAtomicCache.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$4.apply(GridDhtAtomicCache.java:252)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
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.IgniteException: Failed to create string
representation of binary object.
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:189)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.toString(BinaryObjectImpl.java:920)
at java.lang.String.valueOf(String.java:2994)
at
org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
at
org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
... 27 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to read
field: currentContacts
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.wrapFieldException(BinaryReaderExImpl.java:446)
at
[jira] [Created] (IGNITE-12177) CPP: Add Java compute support
Alexandr Shapkin created IGNITE-12177: - Summary: CPP: Add Java compute support Key: IGNITE-12177 URL: https://issues.apache.org/jira/browse/IGNITE-12177 Project: Ignite Issue Type: Improvement Components: platforms Affects Versions: 2.7.5 Reporter: Alexandr Shapkin Currently compute.h contains only platform-specific API declaration (C++). But Ignite does allow a native Java task execution. This feature already has been implemented for .NET platform. Lets port the same changes to C++ client (use PlatformCompute#OP_EXEC_NATIVE). This would help us to create a workaround for a mixed platform cluster that requires a compute calls. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931420#comment-16931420
]
Pavel Tupitsyn commented on IGNITE-12176:
-
[~ashapkin] PR ready, please have a look.
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
>
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
>
>
>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Issue Comment Deleted] (IGNITE-12166) .NET: ExecutableTest fails with PathTooLong error
[ https://issues.apache.org/jira/browse/IGNITE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12166: Comment: was deleted (was: [~ashapkin] PR ready, please have a look) > .NET: ExecutableTest fails with PathTooLong error > - > > Key: IGNITE-12166 > URL: https://issues.apache.org/jira/browse/IGNITE-12166 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > > When repo root path is long enough, it causes ExecutableTests to fail - > classpath exceeds Win32 limit of 32767 characters. If fact, we don't need to > pass classpath explicitly to IgniteProcess. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12166) .NET: ExecutableTest fails with PathTooLong error
[ https://issues.apache.org/jira/browse/IGNITE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931410#comment-16931410 ] Pavel Tupitsyn commented on IGNITE-12166: - [~ashapkin] PR ready, please have a look > .NET: ExecutableTest fails with PathTooLong error > - > > Key: IGNITE-12166 > URL: https://issues.apache.org/jira/browse/IGNITE-12166 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > > When repo root path is long enough, it causes ExecutableTests to fail - > classpath exceeds Win32 limit of 32767 characters. If fact, we don't need to > pass classpath explicitly to IgniteProcess. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12176:
Ignite Flags: (was: Docs Required,Release Notes Required)
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
>
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
>
>
>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12175) ODBC driver does not support WVARCHAR (typeId=-9) which breaks pyodbc
Ilya Kasnacheev created IGNITE-12175:
Summary: ODBC driver does not support WVARCHAR (typeId=-9) which
breaks pyodbc
Key: IGNITE-12175
URL: https://issues.apache.org/jira/browse/IGNITE-12175
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.7.5
Reporter: Ilya Kasnacheev
Subj:
pyodbc.Error: ('HYC00', '[HYC00] Data type is not supported. [typeId=-9] (0)
(SQLBindParameter)')
https://stackoverflow.com/questions/57971252/python-string-to-varchar-mapping-using-odbc-with-apache-ignite-not-supported/57973839#57973839
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins
Pavel Tupitsyn created IGNITE-12176:
---
Summary: .NET: Apache.Ignite.exe fails when config has custom
logger or plugins
Key: IGNITE-12176
URL: https://issues.apache.org/jira/browse/IGNITE-12176
Project: Ignite
Issue Type: Bug
Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Steps to reproduce:
* Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
* Create a config file with that logger:
{code}
http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
{code}
* Run Apache.Ignite.exe with that config file while CustomAsm is in a separate
dir:
{code}
Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-8098) Getting affinity for topology version earlier than affinity is calculated because of data race
[
https://issues.apache.org/jira/browse/IGNITE-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931277#comment-16931277
]
Ilya Kasnacheev commented on IGNITE-8098:
-
Possible duplicate of IGNITE-11465
> Getting affinity for topology version earlier than affinity is calculated
> because of data race
> --
>
> Key: IGNITE-8098
> URL: https://issues.apache.org/jira/browse/IGNITE-8098
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Andrey Aleksandrov
>Priority: Minor
> Fix For: 2.8
>
>
> From time to time the Ignite cluster with services throws next exception
> during restarting of some nodes:
> java.lang.IllegalStateException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=c770dbcf-2908-442d-8aa0-bf26a2aecfef, addrs=[10.44.162.169, 127.0.0.1],
> sockAddrs=[clrv041279.ic.ing.net/10.44.162.169:56500, /127.0.0.1:56500],
> discPort=56500, order=11, intOrder=8, lastExchangeTime=1520931375337,
> loc=true, ver=2.3.3#20180213-sha1:f446df34, isClient=false],
> grp=ignite-sys-cache, topVer=AffinityTopologyVersion [topVer=13,
> minorTopVer=0], head=AffinityTopologyVersion [topVer=15, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=11, minorTopVer=0],
> AffinityTopologyVersion [topVer=11, minorTopVer=1], AffinityTopologyVersion
> [topVer=12, minorTopVer=0], AffinityTopologyVersion [topVer=15,
> minorTopVer=0]]]
> Looks like the reason of this issue is the data race in GridServiceProcessor
> class.
> How to reproduce:
> 1)To simulate data race you should update next place in source code:
> Class: GridServiceProcessor
> Method: @Override public void onEvent(final DiscoveryEvent evt, final
> DiscoCache discoCache) {
> Place:
>
> try {
> svcName.set(dep.configuration().getName());
> ctx.cache().internalCache(UTILITY_CACHE_NAME).context().affinity().
> affinityReadyFuture(topVer).get();
> //HERE (between GET and REASSIGN) you should add Thread.sleep(100) for
> example.
> //try {
> //Thread.sleep(100);
> //}
> //catch (InterruptedException e1) {
> //e1.printStackTrace();
> //}
>
> reassign(dep, topVer);
> }
> catch (IgniteCheckedException ex) {
> if (!(e instanceof ClusterTopologyCheckedException))
> LT.error(log, ex, "Failed to do service reassignment (will retry): " +
> dep.configuration().getName());
> retries.add(dep);
> }
> ...
> 2)After that you should imitate start/shutdown iterations. For reproducing I
> used GridServiceProcessorBatchDeploySelfTest (but timeout on future.get
> should be increased to avoid timeout error)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-12014) Getting affinity for topology version earlier than affinity is calculated for system cache
[
https://issues.apache.org/jira/browse/IGNITE-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev resolved IGNITE-12014.
--
Fix Version/s: (was: 2.8)
Resolution: Duplicate
Seems to be identical to IGNITE-11465. Resolving.
> Getting affinity for topology version earlier than affinity is calculated
> for system cache
> ---
>
> Key: IGNITE-12014
> URL: https://issues.apache.org/jira/browse/IGNITE-12014
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.5
>Reporter: PetrovMikhail
>Priority: Major
> Attachments: JcacheExchangeAwaitTest.java
>
>
> The following exception was being caught occasionally on a big cluster (128
> nodes) after it's activation and concurrent Ignite#reentrantLock() method
> call from different nodes. (On 16 nodes cluster this exception was never
> detected with no code change).
> It's attached a presumptive reproducer of that problem which stable fails
> with the specified exception.
> {code:java}
> java.lang.IllegalStateException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=cf397493-7528-46dc-bc5a-444f9d51, consistentId=127.0.0.1:47501,
> addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501],
> discPort=47501, order=2, intOrder=2, lastExchangeTime=1564050248387,
> loc=true, ver=2.8.0#20190725-sha1:, isClient=false],
> grp=default-volatile-ds-group, topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=1], lastAffChangeTopVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=1], head=AffinityTopologyVersion [topVer=2, minorTopVer=2],
> history=[AffinityTopologyVersion [topVer=2, minorTopVer=2]]]
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:802)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:749)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:657)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:227)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:273)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:264)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:288)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.entryExx(GridDhtColocatedCache.java:161)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.entryEx(GridNearTxLocal.java:4470)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.enlistRead(GridNearTxLocal.java:2709)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.getAllAsync(GridNearTxLocal.java:2188)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$4.op(GridDhtColocatedCache.java:204)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5644)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4561)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:202)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4842)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4808)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1480)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:396)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:561)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:556)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1664)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:556)
> at
>
[jira] [Resolved] (IGNITE-10249) TcpDiscoveryMultiThreadedTest#testCustomEventNodeRestart: Getting affinity for topology version earlier than affinity is calculated
[
https://issues.apache.org/jira/browse/IGNITE-10249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev resolved IGNITE-10249.
--
Resolution: Duplicate
Seems to be same to previously fixed IGNITE-11465.
> TcpDiscoveryMultiThreadedTest#testCustomEventNodeRestart: Getting affinity
> for topology version earlier than affinity is calculated
> ---
>
> Key: IGNITE-10249
> URL: https://issues.apache.org/jira/browse/IGNITE-10249
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments:
> TcpDiscoveryMultiThreadedTest.testCustomEventNodeRestart.2.log,
> TcpDiscoveryMultiThreadedTest.testCustomEventNodeRestart.log
>
>
> TcpDiscoveryMultiThreadedTest#testCustomEventNodeRestart (in current codebase
> muted by renaming to {{_testCustomEventNodeRestart}}) fails on Teamcity with
> unexpected exception (could not reproduce locally): {noformat}
> org.apache.ignite.IgniteException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=ae293efb-8b41-4b86-b32b-74707081, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47502], discPort=47502, order=14, intOrder=10,
> lastExchangeTime=1542188985763, loc=true, ver=2.7.0#20181113-sha1:b186327e,
> isClient=false], grp=default, topVer=AffinityTopologyVersion [topVer=17,
> minorTopVer=0], head=AffinityTopologyVersion [topVer=18, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=14, minorTopVer=0],
> AffinityTopologyVersion [topVer=15, minorTopVer=0], AffinityTopologyVersion
> [topVer=18, minorTopVer=0]]]
> Caused by: javax.cache.CacheException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=ae293efb-8b41-4b86-b32b-74707081, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet
> {noformat}
> More detailed teamcity logs are attached:
> [^TcpDiscoveryMultiThreadedTest.testCustomEventNodeRestart.log] and
> [^TcpDiscoveryMultiThreadedTest.testCustomEventNodeRestart.2.log]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-10389) Getting affinity for topology version earlier than affinity is calculated
[
https://issues.apache.org/jira/browse/IGNITE-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-10389:
-
Ignite Flags: (was: Docs Required)
> Getting affinity for topology version earlier than affinity is calculated
> -
>
> Key: IGNITE-10389
> URL: https://issues.apache.org/jira/browse/IGNITE-10389
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Arnaud Rivero
>Priority: Major
>
> When we deploy a new Ignite cluster on YARN and we deploy an Ignite service
> at the same time (by configuring it in the xml configuration file et putting
> it in the IGNITE_USERS_LIBS path), we get the following exception (the
> service name was replaced by XX):
>
>
> {code:java}
> [14:48:42,004][SEVERE][srvc-deploy-#144][GridServiceProcessor] Error when
> executing service: XX
> java.lang.IllegalStateException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=fd770768-189d-4374-82af-2497eff173da, addrs=[],
> sockAddrs=[], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1542894520229, loc=true, ver=2.6.0#20180710-sha1:669feacc,
> isClient=false], grp=ignite-sys-cache, topVer=AffinityTopologyVersion
> [topVer=2, minorTopVer=0], head=AffinityTopologyVersion [topVer=4,
> minorTopVer=1], history=[AffinityTopologyVersion [topVer=1, minorTopVer=0],
> AffinityTopologyVersion [topVer=4, minorTopVer=0], AffinityTopologyVersion
> [topVer=4, minorTopVer=1]]]
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:632)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:532)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:225)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:261)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:252)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:276)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1828)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2015)
> 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)
> {code}
>
> We found this previous issue and we wondered if we didn't meet an edge case
> of it :
> IGNITE-1171
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-10389) Getting affinity for topology version earlier than affinity is calculated
[
https://issues.apache.org/jira/browse/IGNITE-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev resolved IGNITE-10389.
--
Resolution: Duplicate
There's no information to differentiate this issue from IGNITE-11465, which is
fixed. Resolving.
> Getting affinity for topology version earlier than affinity is calculated
> -
>
> Key: IGNITE-10389
> URL: https://issues.apache.org/jira/browse/IGNITE-10389
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Arnaud Rivero
>Priority: Major
>
> When we deploy a new Ignite cluster on YARN and we deploy an Ignite service
> at the same time (by configuring it in the xml configuration file et putting
> it in the IGNITE_USERS_LIBS path), we get the following exception (the
> service name was replaced by XX):
>
>
> {code:java}
> [14:48:42,004][SEVERE][srvc-deploy-#144][GridServiceProcessor] Error when
> executing service: XX
> java.lang.IllegalStateException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=fd770768-189d-4374-82af-2497eff173da, addrs=[],
> sockAddrs=[], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1542894520229, loc=true, ver=2.6.0#20180710-sha1:669feacc,
> isClient=false], grp=ignite-sys-cache, topVer=AffinityTopologyVersion
> [topVer=2, minorTopVer=0], head=AffinityTopologyVersion [topVer=4,
> minorTopVer=1], history=[AffinityTopologyVersion [topVer=1, minorTopVer=0],
> AffinityTopologyVersion [topVer=4, minorTopVer=0], AffinityTopologyVersion
> [topVer=4, minorTopVer=1]]]
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:632)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:532)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:225)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:261)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:252)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:276)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1828)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2015)
> 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)
> {code}
>
> We found this previous issue and we wondered if we didn't meet an edge case
> of it :
> IGNITE-1171
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12162) Add the cluster name to the promt message "--deactivate" the control.sh
[ https://issues.apache.org/jira/browse/IGNITE-12162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931263#comment-16931263 ] Kirill Tkalenko commented on IGNITE-12162: -- [~akalashnikov], please do a code review. > Add the cluster name to the promt message "--deactivate" the control.sh > --- > > Key: IGNITE-12162 > URL: https://issues.apache.org/jira/browse/IGNITE-12162 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.8 > > > Add the cluster name to the promt message "--deactivate" the control.sh -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12162) Add the cluster name to the promt message "--deactivate" the control.sh
[ https://issues.apache.org/jira/browse/IGNITE-12162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-12162: - Reviewer: Anton Kalashnikov (was: Sergey Antonov) > Add the cluster name to the promt message "--deactivate" the control.sh > --- > > Key: IGNITE-12162 > URL: https://issues.apache.org/jira/browse/IGNITE-12162 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.8 > > > Add the cluster name to the promt message "--deactivate" the control.sh -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12162) Add the cluster name to the promt message "--deactivate" the control.sh
[ https://issues.apache.org/jira/browse/IGNITE-12162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931258#comment-16931258 ] Sergey Antonov commented on IGNITE-12162: - [~ktkale...@gridgain.com] Changes looks good for me. > Add the cluster name to the promt message "--deactivate" the control.sh > --- > > Key: IGNITE-12162 > URL: https://issues.apache.org/jira/browse/IGNITE-12162 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.8 > > > Add the cluster name to the promt message "--deactivate" the control.sh -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12122) Remove setIncludeEventTypes from GridAbstractTest.
[ https://issues.apache.org/jira/browse/IGNITE-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931134#comment-16931134 ] Stanilovsky Evgeny commented on IGNITE-12122: - TC huge time consumer difference attached. I compare 2 last nightly TC runs. Results shows that TC time economy reached. [~Mmuzaf] could u check it ? > Remove setIncludeEventTypes from GridAbstractTest. > -- > > Key: IGNITE-12122 > URL: https://issues.apache.org/jira/browse/IGNITE-12122 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7.5 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Attachments: 6825_res.ods, flamegraph-18988.svg > > Time Spent: 10m > Remaining Estimate: 0h > > Simple cache.put() hot threads measurements shows that > GridCacheEventManager::addEvent consumes about 7% of overall time, i suggest > to remove this events from GridAbstractTest::getConfiguration and stores only > for really requiring tests. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12122) Remove setIncludeEventTypes from GridAbstractTest.
[ https://issues.apache.org/jira/browse/IGNITE-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-12122: Attachment: 6825_res.ods > Remove setIncludeEventTypes from GridAbstractTest. > -- > > Key: IGNITE-12122 > URL: https://issues.apache.org/jira/browse/IGNITE-12122 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7.5 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Attachments: 6825_res.ods, flamegraph-18988.svg > > Time Spent: 10m > Remaining Estimate: 0h > > Simple cache.put() hot threads measurements shows that > GridCacheEventManager::addEvent consumes about 7% of overall time, i suggest > to remove this events from GridAbstractTest::getConfiguration and stores only > for really requiring tests. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12147) Thin client: Partitions response doesn't contain caches for which affinity awareness is not applicable
[ https://issues.apache.org/jira/browse/IGNITE-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931126#comment-16931126 ] Aleksey Plekhanov commented on IGNITE-12147: [~ptupitsyn], [~isapego], thanks for review! Merged to master. > Thin client: Partitions response doesn't contain caches for which affinity > awareness is not applicable > -- > > Key: IGNITE-12147 > URL: https://issues.apache.org/jira/browse/IGNITE-12147 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-23 > Time Spent: 40m > Remaining Estimate: 0h > > Partitions response never contains caches for which affinity awareness is not > applicable (unlike specified by the protocol) even if information for these > caches was explicitly requested. > .NET thin client also fails while processing messages for caches without > partitions information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931117#comment-16931117
]
Lev Agafonov commented on IGNITE-12032:
---
[~isapego], [~dmagda]
Hello, Igor! Yep, I'm new to Ignite and started contribute recently.
Let me make summary, I've already investigated on this ticket:
# The root cause of this error is closing +network+ connection from user
application side, using thin client without notifying server about closing
+database+ connection itself. It's similar to finishing work with your personal
computer by immediate disconnecting plug from socket :). In this case server
doesn't expect that network connection is closed and we got WARN message from
Ignite on server side: "_Closing NIO session because of unhandled exception_"
and the IOException from Java itself.
# The right way of finishing work with database connection is:
resultset.close(); statement.close(), connection.close(). In case of this issue
- `connection.close()` from user application side is enough to get things good.
# As a solution I'd like to make WARN message (in class GridNioServer) more
user-friendly, giving a clue for the most often reason what goes wrong and how
it can be fixed, by changing current WARN message from "_Closing NIO session
because of unhandled exception_" to "Client connection lost, make sure
connection.close() called before closing database connection". If everything
clear, and you don't object - I'd like to make a PR.
Thank you!
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Assignee: Lev Agafonov
>Priority: Minor
> Labels: newbie, usability
> Fix For: 2.8
>
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
