[jira] [Commented] (IGNITE-9305) Wrong off-heap size is reported for a node
[
https://issues.apache.org/jira/browse/IGNITE-9305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599333#comment-16599333
]
Denis Magda commented on IGNITE-9305:
-
[~xtern],
The format looks good to me. Let's type "size=uknown" for "metastoreMemPlc"
persistence region and create a ticket to see how this can be fixed in the
future.
Btw, would there be any significant performance impact if we print out these
detailed metrics periodically? Did you need to enable resources intensive
metrics collection? In my understanding, there should be no impact.
> Wrong off-heap size is reported for a node
> --
>
> Key: IGNITE-9305
> URL: https://issues.apache.org/jira/browse/IGNITE-9305
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.6
>Reporter: Denis Magda
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.7
>
>
> Was troubleshooting an Ignite deployment today and couldn't find out from the
> logs what was the actual off-heap space used.
> Those were the given memory resoures (Ignite 2.6):
> {code}
> [2018-08-16 15:07:49,961][INFO ][main][GridDiscoveryManager] Topology
> snapshot [ver=1, servers=1, clients=0, CPUs=64, offheap=30.0GB, heap=24.0GB]
> {code}
> And that weird stuff was reported by the node (pay attention to the last
> line):
> {code}
> [2018-08-16 15:45:50,211][INFO
> ][grid-timeout-worker-#135%cluster_31-Dec-2017%][IgniteKernal%cluster_31-Dec-2017]
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c033026e, name=cluster_31-Dec-2017, uptime=00:38:00.257]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=64]
> ^-- CPU [cur=0.03%, avg=5.54%, GC=0%]
> ^-- PageMemory [pages=6997377]
> ^-- Heap [used=9706MB, free=61.18%, comm=22384MB]
> ^-- Non heap [used=144MB, free=-1%, comm=148MB] - this line is always the
> same!
> {code}
> Had to change the code by using
> {code}dataRegion.getPhysicalMemoryPages(){code} to find out that actual
> off-heap usage size was
> {code}
> >>> Physical Memory Size: 28651614208 => 27324 MB, 26 GB
> {code}
> The logs have to report the following instead:
> {code}
> ^-- Off-heap {Data Region 1} [used={dataRegion1.getPhysicalMemorySize()},
> free=X%, comm=dataRegion1.maxSize()]
> ^-- Off-heap {Data Region 2} [used={dataRegion2.getPhysicalMemorySize()},
> free=X%, comm=dataRegion2.maxSize()]
> {code}
> If Ignite persistence is enabled then the following extra lines have to be
> added to see the disk used space:
> {code}
> ^-- Ignite persistence {Data Region 1}:
> used={dataRegion1.getTotalAllocatedSize() -
> dataRegion1.getPhysicalMemorySize()}
> ^-- Ignite persistence {Data Region 2}
> [used={dataRegion2.getTotalAllocatedSize() -
> dataRegion2.getPhysicalMemorySize()}]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7782) Thin Client lib: Python
[ https://issues.apache.org/jira/browse/IGNITE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Melnichuk updated IGNITE-7782: - Description: Implement Thin (lightweight) Client lib in Python programming language for Ignite Binary Client Protocol [https://apacheignite.readme.io/v2.4/docs/binary-client-protocol] Prototype: [https://github.com/skozlov-gridgain/apache-ignite-python-thin-client] Example - NodeJS client - IGNITE- [https://github.com/nobitlost/ignite/tree/master/modules/platforms/nodejs] --- h5. Package name (for use with setuptools/PyPI): pyignite h5. Location of the lib in the repository: .../modules/platforms/python h5. Python version: 3.4+ (tested on 3.4 and 3.6) h5. Ignite version: 2.7. h5. Architecture: Syncronous (safe for use with threading/multiprocessing), object-oriented. h5. Documentation: Sphinx/autodoc + readme.md h5. Test framework: pytest, pytest-runner for setuptools pytest integration. h5. Usage examples included: - cache management (creating, configuring, deleting), - key-value operations, - cache scan, - basic SQL queries, - simple and advanced work with Complex objects, - fail-over connection. h5. Goal: Create a full-featured Ignite thin client library: - carefully implement, test, and document all the features of the binary protocol, that can be useful in Python programs, - implement and document features like type IDs or serialization hints, that are mostly useless in Python, for interoperability's sake, - skip features, that are not applicable to Python programs, like filter object in scan query. h5. Proposed scope of features: - basic and SSL-wrapped TCP connection, - authentication and authorization, - failover mechanism, - all datatypes, - all client operations (except Binary-Type operations with type names). was: Implement Thin (lightweight) Client lib in Python programming language for Ignite Binary Client Protocol [https://apacheignite.readme.io/v2.4/docs/binary-client-protocol] Prototype: [https://github.com/skozlov-gridgain/apache-ignite-python-thin-client] Example - NodeJS client - IGNITE- [https://github.com/nobitlost/ignite/tree/master/modules/platforms/nodejs] --- h5. Package name (for use with setuptools/PyPI): pyignite h5. Location of the lib in the repository: .../modules/platforms/python h5. Python version: 3.4+ (tested on 3.4 and 3.6) h5. Ignite version: 2.5. h5. Architecture: Syncronous (safe for use with threading/multiprocessing), procedural. Ignite operations are mapped to functions. h5. Documentation: Sphinx/autodoc + readme.md h5. Test framework: pytest, pytest-runner for setuptools pytest integration. h5. Usage examples included: - cache operations (creating, configuring, deleting), - key-value operations, - scan query, - basic SQL queries. h5. Goal: Create a full-featured Ignite thin client library: - carefully implement, test, and document all the features of the binary protocol, that can be useful in Python programs, - implement and document features like type IDs or serialization hints, that are mostly useless in Python, for interoperability's sake, - skip features, that are not applicable to Python programs, like filter object in scan query. h5. Proposed scope of features: - basic and SSL-wrapped TCP connection, - authentication and authorization, - failover mechanism, - all datatypes, - all client operations (except Binary-Type operations with type names). > Thin Client lib: Python > --- > > Key: IGNITE-7782 > URL: https://issues.apache.org/jira/browse/IGNITE-7782 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Dmitry Melnichuk >Priority: Major > Fix For: 2.7 > > > Implement Thin (lightweight) Client lib in Python programming language for > Ignite Binary Client Protocol > [https://apacheignite.readme.io/v2.4/docs/binary-client-protocol] > Prototype: > [https://github.com/skozlov-gridgain/apache-ignite-python-thin-client] > Example - NodeJS client - IGNITE- > [https://github.com/nobitlost/ignite/tree/master/modules/platforms/nodejs] > --- > h5. Package name (for use with setuptools/PyPI): > pyignite > h5. Location of the lib in the repository: > .../modules/platforms/python > h5. Python version: > 3.4+ (tested on 3.4 and 3.6) > h5. Ignite version: > 2.7. > h5. Architecture: > Syncronous (safe for use with threading/multiprocessing), object-oriented. > h5. Documentation: > Sphinx/autodoc + readme.md > h5. Test framework: > pytest, pytest-runner for setuptools pytest integration. > h5. Usage examples included: > - cache management (creating, configuring, deleting), > - key-value operations, > -
[jira] [Commented] (IGNITE-9440) control.sh --wal delete do not delete files
[ https://issues.apache.org/jira/browse/IGNITE-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599154#comment-16599154 ] Ivan Daschinskiy commented on IGNITE-9440: -- [~a-polyakov] Hi, have you looked at GridInternalTaskUnusedWalSegmentsTest? If no, please look at it. You can easily find, that not all WAL segments and CP markers is safe to delete, only before firstCheckpointPointer is. This test passes in TC, please see [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5309147371316808775=testDetails]. So I'm sure that all works ok, no patch is needed > control.sh --wal delete do not delete files > > > Key: IGNITE-9440 > URL: https://issues.apache.org/jira/browse/IGNITE-9440 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Attachments: TC.png > > > Do not delete the files by the utility on command "control.sh --wal delete". > Remain both checkpoints and wal in the archive. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml
[
https://issues.apache.org/jira/browse/IGNITE-9396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599100#comment-16599100
]
Oleg Ignatenko commented on IGNITE-9396:
[~chief] for this ticket I only performed license check (linked to ticket)
because it only adds a documentation file that isn't involved in code.
If you still prefer me to run all other Teamcity checks that we usually do for
changes that affect code, please let me know and I will do.
> ML Examples: can't run examples, not enough dependencies in pom.xml
> ---
>
> Key: IGNITE-9396
> URL: https://issues.apache.org/jira/browse/IGNITE-9396
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.7
>
>
> Trying to run ml-examples and can't compile example project because several
> dependencies didn't added in pom.xml
> Execution:
> Using JB IDEA Run->Run class to execute current class
> or
> `java -classpath [all classpaths which are listed in pom file] class name`
> or compile with maven also failed
> `mvn clean compile`
> Exception:
> Can't compile project. not enough dependencies
> Missing dependencies:
> {code:xml}
>
> com.github.fommil.netlib
> core
>
>
> org.springframework.data
> spring-data-commons
>
>
> org.springframework
> spring-beans
>
>
> org.springframework
> spring-context
>
>
> com.h2database
> h2
>
> {code}
> com.github.fommil.netlib, springframework.* and h2 need to run -
> org.apache.ignite.examples.ml.dataset.AlgorithmSpecificDatasetExample
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml
[
https://issues.apache.org/jira/browse/IGNITE-9396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599087#comment-16599087
]
ASF GitHub Bot commented on IGNITE-9396:
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4662
IGNITE-9396 ML Examples: can't run examples, not enough dependencies in
pom.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9396
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4662.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4662
commit 1eeca908a8076a8317947dac8a46845964d1d7ea
Author: Oleg Ignatenko
Date: 2018-08-23T13:13:28Z
IGNITE-9348 ML examples improvements
- wip (logging improved)
-- verified with diffs overview, executing the examples and studying
execution logs
commit e50b89c392568ba9b93935c4fa6c7f7f93f5ec6f
Author: Oleg Ignatenko
Date: 2018-08-23T14:45:57Z
Revert "IGNITE-9348 ML examples improvements"
This reverts commit 1eeca908a8076a8317947dac8a46845964d1d7ea.
commit 474024b4c5bbdb3c0a4ed2f0a66238c8054c6674
Author: Oleg Ignatenko
Date: 2018-08-23T14:57:34Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 9642b233b5701bdad47ebea163079160227c582a
Author: Oleg Ignatenko
Date: 2018-08-28T14:01:11Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 7fc16d013ab725d2ff2e1a1b042c983f11d0c4d4
Author: Oleg Ignatenko
Date: 2018-08-28T15:13:02Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit d2caba67b156674f051f50faebeafe0871bf0914
Author: Oleg Ignatenko
Date: 2018-08-29T13:14:07Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 16775dff51d71ea68b4a3dea98be552130c493ed
Author: Oleg Ignatenko
Date: 2018-08-30T09:00:56Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit aedb59929974fe205b949225c1a338c68c60cfc8
Author: Oleg Ignatenko
Date: 2018-08-30T09:42:38Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 39c6482fcdca506aa33011ed21c98060b4a8c68b
Author: Oleg Ignatenko
Date: 2018-08-30T11:28:05Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 33b32a2760a6559c78283b927e3191180d8ed9e1
Author: Oleg Ignatenko
Date: 2018-08-30T12:31:16Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 9531028ddd1aef9e95f7e8c8b528086739bbb1b0
Author: Oleg Ignatenko
Date: 2018-08-30T14:06:34Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 28f22c6e2fffcb82717ba5da7be2cfd39715c4e3
Author: Oleg Ignatenko
Date: 2018-08-30T16:41:51Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit aacac88db519187413b0fc5ff9d0e55b8f8cff22
Author: Oleg Ignatenko
Date: 2018-08-31T10:12:32Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 897f920dde46022849b13f9fb86dba8e54119a56
Author: Oleg Ignatenko
Date: 2018-08-31T13:57:14Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit 114c79e54c1b316006ccc3ff22d20d902f9313df
Author: Oleg Ignatenko
Date: 2018-08-31T17:39:16Z
Merge branch 'master' of https://github.com/apache/ignite into master-ml
commit edb68a4ae2ccd1e66d77aa3690d4e0c541cf78b4
Author: Oleg Ignatenko
Date: 2018-08-31T17:56:57Z
IGNITE-9396 ML Examples: can't run examples, not enough dependencies in
pom.xml
- documentation added as per discussion in JIRA ticket comments
-- verified with diffs overview and clean build of examples per added
instructions
> ML Examples: can't run examples, not enough dependencies in pom.xml
> ---
>
> Key: IGNITE-9396
> URL: https://issues.apache.org/jira/browse/IGNITE-9396
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.7
>
>
> Trying to run ml-examples and can't compile example project because several
> dependencies didn't added in pom.xml
> Execution:
> Using JB IDEA Run->Run class to execute current class
> or
> `java -classpath [all classpaths which are listed in pom file] class name`
> or compile with maven also failed
> `mvn clean compile`
> Exception:
> Can't compile project. not enough dependencies
> Missing dependencies:
> {code:xml}
>
> com.github.fommil.netlib
>
[jira] [Commented] (IGNITE-6346) Distributed set does not work in REPLICATED mode
[
https://issues.apache.org/jira/browse/IGNITE-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599006#comment-16599006
]
Pavel Pereslegin commented on IGNITE-6346:
--
Hello [~vk].
I've faced with the same problem and found that this bug also applies to server
nodes.
In collection configuration we can specify node filter which will exclude some
server nodes from affinity.
Reproducer for server node:
{code:java}
Ignite node = startGridsMultiThreaded(2);
ClusterNode locNode = node.cluster().localNode();
IgniteSet set = node.set("test",
new
CollectionConfiguration().setCacheMode(CacheMode.REPLICATED).setNodeFilter(n ->
!locNode.equals(n)));
set.add(1);
assertTrue(set.iterator().hasNext());
{code}
So I think that it would be better to check that the current node is an
affinity node.
{code:java}
if (ctx.isLocal() || (ctx.isReplicated() && ctx.affinityNode()))
{code}
What do you think?
> Distributed set does not work in REPLICATED mode
>
>
> Key: IGNITE-6346
> URL: https://issues.apache.org/jira/browse/IGNITE-6346
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.1
>Reporter: Valentin Kulichenko
>Assignee: vk
>Priority: Major
>
> When {{IgniteSet}} is created with {{REPLICATED}} cache mode, any attempt to
> read it fails with exception:
> {noformat}
> Exception in thread "main" class org.apache.ignite.IgniteException: Cluster
> group is empty.
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:48)
> at ReplicatedSet.main(ReplicatedSet.java:36)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: Cluster
> group is empty.
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.execute0(GridCacheQueryAdapter.java:481)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.execute(GridCacheQueryAdapter.java:442)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSetImpl.iterator0(GridCacheSetImpl.java:420)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSetImpl.iterator(GridCacheSetImpl.java:375)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSetProxy.iterator(GridCacheSetProxy.java:342)
> ... 6 more
> {noformat}
> To reproduce run the following code:
> {code}
> Ignition.start(new IgniteConfiguration().setIgniteInstanceName("server-1"));
> Ignition.start(new IgniteConfiguration().setIgniteInstanceName("server-2"));
> Ignition.setClientMode(true);
> Ignite ignite = Ignition.start();
> IgniteSet set = ignite.set("my-set", new
> CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
> for (String s : set) {
> System.out.println(s);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9373) MVCC tests fail
[ https://issues.apache.org/jira/browse/IGNITE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598971#comment-16598971 ] ASF GitHub Bot commented on IGNITE-9373: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4623 > MVCC tests fail > --- > > Key: IGNITE-9373 > URL: https://issues.apache.org/jira/browse/IGNITE-9373 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > Attachments: MvccTestResults.tar.gz > > > Number of tests in MVCC test suites fail. Most of the fails is a regression > introduces by new changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7900) Write Zookeeper Discovery documentation in readme.io
[ https://issues.apache.org/jira/browse/IGNITE-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-7900. --- Fixed. > Write Zookeeper Discovery documentation in readme.io > > > Key: IGNITE-7900 > URL: https://issues.apache.org/jira/browse/IGNITE-7900 > Project: Ignite > Issue Type: Task > Components: documentation, zookeeper >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > Attachments: zookeeper_discovery_diagrams.zip > > > Describe Zookeeper Discovery in readme.io. > The documentation will be based on the details presented in IEP-15: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-15%3A+Discovery+SPI+by+ZooKeeper > The following sections should present in the doc: > * Native discovery SPI vs Zookeeper SPI (pros and cons (aka. ring-based > communication vs. consensus-based Zookeeper Cluster; when to use the first > and the second) > * Configuration example > * Describe node join and disconnection process > * Describe split-brain handling/protection > * Review and clean IEP (will be used as an advanced doc) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9373) MVCC tests fail
[ https://issues.apache.org/jira/browse/IGNITE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598945#comment-16598945 ] Andrew Mashenkov commented on IGNITE-9373: -- TC looks good, can be merged. > MVCC tests fail > --- > > Key: IGNITE-9373 > URL: https://issues.apache.org/jira/browse/IGNITE-9373 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > Attachments: MvccTestResults.tar.gz > > > Number of tests in MVCC test suites fail. Most of the fails is a regression > introduces by new changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9305) Wrong off-heap size is reported for a node
[
https://issues.apache.org/jira/browse/IGNITE-9305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598940#comment-16598940
]
Pavel Pereslegin commented on IGNITE-9305:
--
Hello [~dmagda].
I changed format as you suggested, here an example of output:
{noformat}
^-- H/N/C [hosts=1, nodes=2, CPUs=8]
^-- CPU [cur=7.8%, avg=11.65%, GC=0%]
^-- PageMemory [pages=7447]
^-- Heap [used=114MB, free=96.78%, comm=242MB]
^-- Off-heap [used=29MB, free=87.2%, comm=230MB]
^-- sysMemPlc region [used=0MB, free=99.98%, comm=100MB]
^-- default region [used=29MB, free=2.1%, comm=30MB]
^-- metastoreMemPlc region [used=0MB, free=99.96%, comm=100MB]
^-- Ignite persistence [used=35MB]
^-- sysMemPlc region [used=0MB]
^-- default region [used=35MB]
^-- metastoreMemPlc region [used=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=6, qSize=0]
^-- System thread pool [active=0, idle=6, qSize=0]
^-- Custom executor 0 [active=0, idle=0, qSize=0]
^-- Custom executor 1 [active=0, idle=0, qSize=0]
{noformat}
But there is a problem with tracking allocated pages (disk usage) for
"metastoreMemPlc" persistence region (metastore).
Total allocated pages metric is always zero, because this region is recreated
after FilePageStore was created.
I see the following options:
# Output actual value of this metric (don't change anything here) and create
separate ticket for the problem.
# Exclude "metastoreMemPlc" region from persistence regions in log output.
# Output only those persistence regions for which metrics are enabled.
Any thoughts?
> Wrong off-heap size is reported for a node
> --
>
> Key: IGNITE-9305
> URL: https://issues.apache.org/jira/browse/IGNITE-9305
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.6
>Reporter: Denis Magda
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.7
>
>
> Was troubleshooting an Ignite deployment today and couldn't find out from the
> logs what was the actual off-heap space used.
> Those were the given memory resoures (Ignite 2.6):
> {code}
> [2018-08-16 15:07:49,961][INFO ][main][GridDiscoveryManager] Topology
> snapshot [ver=1, servers=1, clients=0, CPUs=64, offheap=30.0GB, heap=24.0GB]
> {code}
> And that weird stuff was reported by the node (pay attention to the last
> line):
> {code}
> [2018-08-16 15:45:50,211][INFO
> ][grid-timeout-worker-#135%cluster_31-Dec-2017%][IgniteKernal%cluster_31-Dec-2017]
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c033026e, name=cluster_31-Dec-2017, uptime=00:38:00.257]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=64]
> ^-- CPU [cur=0.03%, avg=5.54%, GC=0%]
> ^-- PageMemory [pages=6997377]
> ^-- Heap [used=9706MB, free=61.18%, comm=22384MB]
> ^-- Non heap [used=144MB, free=-1%, comm=148MB] - this line is always the
> same!
> {code}
> Had to change the code by using
> {code}dataRegion.getPhysicalMemoryPages(){code} to find out that actual
> off-heap usage size was
> {code}
> >>> Physical Memory Size: 28651614208 => 27324 MB, 26 GB
> {code}
> The logs have to report the following instead:
> {code}
> ^-- Off-heap {Data Region 1} [used={dataRegion1.getPhysicalMemorySize()},
> free=X%, comm=dataRegion1.maxSize()]
> ^-- Off-heap {Data Region 2} [used={dataRegion2.getPhysicalMemorySize()},
> free=X%, comm=dataRegion2.maxSize()]
> {code}
> If Ignite persistence is enabled then the following extra lines have to be
> added to see the disk used space:
> {code}
> ^-- Ignite persistence {Data Region 1}:
> used={dataRegion1.getTotalAllocatedSize() -
> dataRegion1.getPhysicalMemorySize()}
> ^-- Ignite persistence {Data Region 2}
> [used={dataRegion2.getTotalAllocatedSize() -
> dataRegion2.getPhysicalMemorySize()}]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9448) Change ZooKeeper version to 3.4.13
[ https://issues.apache.org/jira/browse/IGNITE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598925#comment-16598925 ] ASF GitHub Bot commented on IGNITE-9448: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4661 > Change ZooKeeper version to 3.4.13 > -- > > Key: IGNITE-9448 > URL: https://issues.apache.org/jira/browse/IGNITE-9448 > Project: Ignite > Issue Type: Test > Components: zookeeper >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > > Should to change ZooKeeper dependency to last release - just now it is 3.4.13. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9448) Change ZooKeeper version to 3.4.13
[ https://issues.apache.org/jira/browse/IGNITE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598921#comment-16598921 ] ASF GitHub Bot commented on IGNITE-9448: GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4661 IGNITE-9448 Change ZooKeeper version to 3.4.13 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9448 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4661.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4661 commit 33d7c41b45b422845314e0c2ccebfd36a706d243 Author: vd-pyatkov Date: 2018-08-31T15:39:58Z IGNITE-9448 Change ZooKeeper version to 3.4.13 > Change ZooKeeper version to 3.4.13 > -- > > Key: IGNITE-9448 > URL: https://issues.apache.org/jira/browse/IGNITE-9448 > Project: Ignite > Issue Type: Test > Components: zookeeper >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > > Should to change ZooKeeper dependency to last release - just now it is 3.4.13. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9448) Change ZooKeeper version to 3.4.13
Vladislav Pyatkov created IGNITE-9448: - Summary: Change ZooKeeper version to 3.4.13 Key: IGNITE-9448 URL: https://issues.apache.org/jira/browse/IGNITE-9448 Project: Ignite Issue Type: Test Components: zookeeper Reporter: Vladislav Pyatkov Should to change ZooKeeper dependency to last release - just now it is 3.4.13. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9448) Change ZooKeeper version to 3.4.13
[ https://issues.apache.org/jira/browse/IGNITE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-9448: - Assignee: Vladislav Pyatkov > Change ZooKeeper version to 3.4.13 > -- > > Key: IGNITE-9448 > URL: https://issues.apache.org/jira/browse/IGNITE-9448 > Project: Ignite > Issue Type: Test > Components: zookeeper >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > > Should to change ZooKeeper dependency to last release - just now it is 3.4.13. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9447) Benchmarks hangs intemittently due to distributed race condition.
[
https://issues.apache.org/jira/browse/IGNITE-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598835#comment-16598835
]
Pavel Kuznetsov commented on IGNITE-9447:
-
Please, take a look at fix in branch
https://github.com/gridgain/apache-ignite/tree/ignite-dss-benchmarks
> Benchmarks hangs intemittently due to distributed race condition.
> -
>
> Key: IGNITE-9447
> URL: https://issues.apache.org/jira/browse/IGNITE-9447
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Kuznetsov
>Assignee: Pavel Kuznetsov
>Priority: Minor
>
> If we run more than one yardstick driver, benchmark hangs intermittently.
> We've got yardstick's base driver class
> org.apache.ignite.yardstick.IgniteAbstractBenchmark it has logic to wait all
> the nodes in the cluster.
> {noformat}
> final CountDownLatch nodesStartedLatch = new CountDownLatch(1);
> ignite().events().localListen(new IgnitePredicate() {
> @Override public boolean apply(Event gridEvt) {
> if (nodesStarted())
> nodesStartedLatch.countDown();
> return true;
> }
> }, EVT_NODE_JOINED);
> if (!nodesStarted()) {
> println(cfg, "Waiting for " + (args.nodes() - 1) + " nodes to
> start...");
> nodesStartedLatch.await();
> }
> {noformat}
> This code is executed on every driver node.
> If we want to close local ignite instance just after cluster is ready
> (containing expected number of nodes), sometimes we'll have dead lock:
> 1) cluster contains N-1 nodes, all nodes are waiting for the Nth node.
> 2) Nth node is connected, cluster receives message, waitForNodes code of Nth
> node is not executed.
> 3) N-1 nodes got this message and stop waiting.
> 4) N-1 thinks that cluster is ready and call ignite.close() on their local
> instances
> 5) Nth node starts waiting for cluster to contain number of nodes, but N-1 of
> them closed their instances
> 6) Nth node is waiting infinitely.
> We can avoid this problem if we use distributed CountDownLatch
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9447) Benchmarks hangs intemittently due to distributed race condition.
Pavel Kuznetsov created IGNITE-9447:
---
Summary: Benchmarks hangs intemittently due to distributed race
condition.
Key: IGNITE-9447
URL: https://issues.apache.org/jira/browse/IGNITE-9447
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Pavel Kuznetsov
Assignee: Pavel Kuznetsov
If we run more than one yardstick driver, benchmark hangs intermittently.
We've got yardstick's base driver class
org.apache.ignite.yardstick.IgniteAbstractBenchmark it has logic to wait all
the nodes in the cluster.
{noformat}
final CountDownLatch nodesStartedLatch = new CountDownLatch(1);
ignite().events().localListen(new IgnitePredicate() {
@Override public boolean apply(Event gridEvt) {
if (nodesStarted())
nodesStartedLatch.countDown();
return true;
}
}, EVT_NODE_JOINED);
if (!nodesStarted()) {
println(cfg, "Waiting for " + (args.nodes() - 1) + " nodes to
start...");
nodesStartedLatch.await();
}
{noformat}
This code is executed on every driver node.
If we want to close local ignite instance just after cluster is ready
(containing expected number of nodes), sometimes we'll have dead lock:
1) cluster contains N-1 nodes, all nodes are waiting for the Nth node.
2) Nth node is connected, cluster receives message, waitForNodes code of Nth
node is not executed.
3) N-1 nodes got this message and stop waiting.
4) N-1 thinks that cluster is ready and call ignite.close() on their local
instances
5) Nth node starts waiting for cluster to contain number of nodes, but N-1 of
them closed their instances
6) Nth node is waiting infinitely.
We can avoid this problem if we use distributed CountDownLatch
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9428) MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
[
https://issues.apache.org/jira/browse/IGNITE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-9428:
-
Fix Version/s: 2.8
> MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
> --
>
> Key: IGNITE-9428
> URL: https://issues.apache.org/jira/browse/IGNITE-9428
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Due to IGNITE-9256 patch, multiple {{H2ResultSetIterator#onClose}} invocation
> becomes possible. This can be considered as a {{Closable}} contract violation
> and should be fixed.
> Also this case revealed a bug in {{MvccQueryTrackerImpl}} when multiple
> {{onDone()}} call leads to multiple query finished acks sent back to the
> {{MvccCoordinator}} which leads to the problems with the query tracking and
> assertion errors.
> Reproducer:
> {{CacheMvccSqlTxQueriesAbstractTest#testAccountsTxDmlSumSql_WithRemoves_SingleNode}}
>
>
> Upd: test was fixed in IGNITE-9373. But MvccQueryTrackerImpl.onDone() issue
> is still actual.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Description: For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure without no side effect (such as worker failure or any hanging). VacuumTask successfully catch and log the exception, but further check in afterTest() method reports vacuum failure. For now vacuum is disabled for this test. We should fix vacuum failure properly in that case and fix CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. was: For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure. VacuumTask successfully catch and log the exception, but further check in afterTest() method reports vacuum failure. For now vacuum is disabled for this test. We should fix vacuum failure properly in that case and fix CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > Fix For: 2.8 > > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure without no > side effect (such as worker failure or any hanging). > VacuumTask successfully catch and log the exception, but further check in > afterTest() method reports vacuum failure. > For now vacuum is disabled for this test. > We should fix vacuum failure properly in that case and fix > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Description: For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure without negative side effect (such as worker failure or any hanging). VacuumTask successfully catch and log the exception, but further check in afterTest() method reports vacuum failure. For now vacuum is disabled for this test. We should fix vacuum failure properly in that case and fix CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. was: For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure without no side effect (such as worker failure or any hanging). VacuumTask successfully catch and log the exception, but further check in afterTest() method reports vacuum failure. For now vacuum is disabled for this test. We should fix vacuum failure properly in that case and fix CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > Fix For: 2.8 > > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure without > negative side effect (such as worker failure or any hanging). > VacuumTask successfully catch and log the exception, but further check in > afterTest() method reports vacuum failure. > For now vacuum is disabled for this test. > We should fix vacuum failure properly in that case and fix > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Fix Version/s: 2.8 > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > Fix For: 2.8 > > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure. > VacuumTask successfully catch and log the exception, but further check in > afterTest() method reports vacuum failure. > For now vacuum is disabled for this test. > We should fix vacuum failure properly in that case and fix > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Description: For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure. VacuumTask successfully catch and log the exception, but further check in afterTest() method reports vacuum failure. For now vacuum is disabled for this test. We should fix vacuum failure properly in that case and fix CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. was: For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure. We should fix vacuum failure properly in that case. This should fix failed TC test CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > Fix For: 2.8 > > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure. > VacuumTask successfully catch and log the exception, but further check in > afterTest() method reports vacuum failure. > For now vacuum is disabled for this test. > We should fix vacuum failure properly in that case and fix > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Ignite Flags: (was: Docs Required) > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure. > We should fix vacuum failure properly in that case. > This should fix failed TC test > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Component/s: mvcc > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure. > We should fix vacuum failure properly in that case. > This should fix failed TC test > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
[ https://issues.apache.org/jira/browse/IGNITE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9446: - Priority: Minor (was: Major) > MVCC: Races in Vacuum worker on cache stop. > --- > > Key: IGNITE-9446 > URL: https://issues.apache.org/jira/browse/IGNITE-9446 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > > For now, partition store BTree can be destroyed while vacuum in progress > regardless partition reservations which causes VacuumTask failure. > We should fix vacuum failure properly in that case. > This should fix failed TC test > CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9320) MVCC: finalize configuration
[
https://issues.apache.org/jira/browse/IGNITE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598788#comment-16598788
]
ASF GitHub Bot commented on IGNITE-9320:
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/4660
IGNITE-9320: Mvcc cache configuration and cluster nodes validation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9320
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4660.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4660
commit b00fd2a7d315e194b630f4ac2ba09842e69de48d
Author: rkondakov
Date: 2018-08-30T09:09:59Z
IGNITE-9320: Mvcc configuration changed from global flag to per cache flag.
Tests fixed.
commit 1305e54d0afa046aa1100824b9c9a56bc5f84d7a
Author: rkondakov
Date: 2018-08-31T11:20:15Z
Start mvcc processor and cluster validation WIP
> MVCC: finalize configuration
>
>
> Key: IGNITE-9320
> URL: https://issues.apache.org/jira/browse/IGNITE-9320
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
>Priority: Major
> Fix For: 2.7
>
>
> We need to find a way to configure MVCC caches. Currently this is a global
> setting, which is not very convenient. Proposed solution:
> # Introduce new {{CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT}}
> # Do not allow to change cache this mode during restart (when persistence is
> enabled)
> # Do not allow transactions between {{TRANSACTIONAL}} and
> {{TRANSACTIONAL_SNAPSHOT}} caches
> # Add limitation to cache group - all caches within a group should have the
> same mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8886) Simultaneous using of BinaryWriter и BinaryRawWriter leads to BinaryObjectException and OOM
[
https://issues.apache.org/jira/browse/IGNITE-8886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598782#comment-16598782
]
Vladimir Ozerov commented on IGNITE-8886:
-
[~ilyak], [~ezhuravl], looks good to me.
> Simultaneous using of BinaryWriter и BinaryRawWriter leads to
> BinaryObjectException and OOM
> ---
>
> Key: IGNITE-8886
> URL: https://issues.apache.org/jira/browse/IGNITE-8886
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.5
>Reporter: Roman Guseinov
>Assignee: Ilya Kasnacheev
>Priority: Major
> Labels: binary
> Attachments: BinarylizableInvalidFlag.java, BinarylizableOOM.java,
> Screenshot_20180830_142433.png
>
>
> When we use BinaryWriter and BinaryRawWriter simultaneously inside
> writeBinary method we can get the following exceptions in the process of
> deserializing objects:
> 1. class org.apache.ignite.binary.BinaryObjectException: Invalid flag value:
> 115
> {code:java}
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to deserialize object
> [typeName=org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag$TestBean]
>at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1302)
>at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1732)
>at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:910)
>at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:608)
>at
> org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag.main(BinarylizableInvalidFlag.java:33)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> deserialize object
> [typeName=org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag$TestBean]
>at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7322)
>at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
>at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
>at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
>at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4563)
>at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4537)
>at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1350)
>at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:907)
>... 2 more
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> deserialize object
> [typeName=org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag$TestBean]
>at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:909)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:798)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
>at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1764)
>at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1752)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:679)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:461)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:342)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:216)
>at
>
[jira] [Commented] (IGNITE-8189) Improve ZkDistributedCollectDataFuture#deleteFutureData implementation
[ https://issues.apache.org/jira/browse/IGNITE-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598775#comment-16598775 ] ASF GitHub Bot commented on IGNITE-8189: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4537 > Improve ZkDistributedCollectDataFuture#deleteFutureData implementation > -- > > Key: IGNITE-8189 > URL: https://issues.apache.org/jira/browse/IGNITE-8189 > Project: Ignite > Issue Type: Improvement > Components: zookeeper >Reporter: Sergey Chugunov >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.7 > > > Three issues need to be improved in implementation: > * two more deleteIfExists methods within the *deleteFutureData* to be > included in batching *deleteAll* operation; > * if request exceeds ZooKeeper max size limit fallback to one-by-one deletion > should be used (related ticket IGNITE-8188); > * ZookeeperClient#deleteAll implementation may throw NoNodeException is case > of concurrent operation removing the same nodes, in this case fallback to > one-by-one deletion should be used too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8286) ScanQuery ignore setLocal with non local partition
[ https://issues.apache.org/jira/browse/IGNITE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598765#comment-16598765 ] Alexey Goncharuk commented on IGNITE-8286: -- [~roman_s], please move the ticket to Patch Available once the PR is ready, I will merge the change to master. > ScanQuery ignore setLocal with non local partition > -- > > Key: IGNITE-8286 > URL: https://issues.apache.org/jira/browse/IGNITE-8286 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Alexander Belyak >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > 1) Create partitioned cache on 2+ nodes cluster > 2) Select some partition N, local node should not be OWNER of partition N > 3) execute: cache.query(new ScanQuery<>().setLocal(true).setPartition(N)) > Expected result: > empty result (probaply with logging smth like "Trying to execute local query > with non local partition N") or even throw exception > Actual result: > executing (with ScanQueryFallbackClosableIterator) query on remote node. > Problem is that we execute local query on remote node. > Same behaviour can be achieved if we get empty node list from > GridCacheQueryAdapter.node() by any reasons, for example - if we run "local" > query from non data node from given cache (see > GridDiscoveryNamager.cacheAffinityNode(ClusterNode node, String cacheName) in > GridcacheQueryAdapter.executeScanQuery() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6601) Describe walMode on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-6601: -- Assignee: (was: Artem Budnikov) > Describe walMode on readme.io > - > > Key: IGNITE-6601 > URL: https://issues.apache.org/jira/browse/IGNITE-6601 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.2 >Reporter: Ilya Kasnacheev >Priority: Major > > walMode setting is essential to Persistence performance tuning: > default mode is defensive and switching to appropriate walMode easily gives > 3x performance boost on real loads. > However, walMode is not described on readme.io, and Ignite users has no way > of figuring why their persistence performance is unsatisfactory and what > compromises they can make to improve it. > We should have a section on WAL modes on readme.io on topic of > persistence/performance tuning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6601) Describe walMode on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-6601: -- Assignee: Artem Budnikov > Describe walMode on readme.io > - > > Key: IGNITE-6601 > URL: https://issues.apache.org/jira/browse/IGNITE-6601 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.2 >Reporter: Ilya Kasnacheev >Assignee: Artem Budnikov >Priority: Major > > walMode setting is essential to Persistence performance tuning: > default mode is defensive and switching to appropriate walMode easily gives > 3x performance boost on real loads. > However, walMode is not described on readme.io, and Ignite users has no way > of figuring why their persistence performance is unsatisfactory and what > compromises they can make to improve it. > We should have a section on WAL modes on readme.io on topic of > persistence/performance tuning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-4416) Document logging capabilities of Ignite
[ https://issues.apache.org/jira/browse/IGNITE-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-4416. Resolution: Fixed > Document logging capabilities of Ignite > --- > > Key: IGNITE-4416 > URL: https://issues.apache.org/jira/browse/IGNITE-4416 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Major > > Ignite supports a variety of logging provides but neither of them is > documented on readme.io. We have to fill this gap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4416) Document logging capabilities of Ignite
[ https://issues.apache.org/jira/browse/IGNITE-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598760#comment-16598760 ] Artem Budnikov commented on IGNITE-4416: Logging capabilities were documented some time ago. Closing this issue. > Document logging capabilities of Ignite > --- > > Key: IGNITE-4416 > URL: https://issues.apache.org/jira/browse/IGNITE-4416 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Major > > Ignite supports a variety of logging provides but neither of them is > documented on readme.io. We have to fill this gap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4416) Document logging capabilities of Ignite
[ https://issues.apache.org/jira/browse/IGNITE-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-4416: -- Assignee: Artem Budnikov > Document logging capabilities of Ignite > --- > > Key: IGNITE-4416 > URL: https://issues.apache.org/jira/browse/IGNITE-4416 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Major > > Ignite supports a variety of logging provides but neither of them is > documented on readme.io. We have to fill this gap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9395) Incorrect link to javadoc
[ https://issues.apache.org/jira/browse/IGNITE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-9395. Resolution: Fixed > Incorrect link to javadoc > - > > Key: IGNITE-9395 > URL: https://issues.apache.org/jira/browse/IGNITE-9395 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5, 2.6 >Reporter: Yury Gerzhedovich >Assignee: Artem Budnikov >Priority: Minor > > Javadoc's links refer to 1.0.0 version of Ignite instead of latest one. > For example at page [https://apacheignite.readme.io/docs/events] there is > link javadoc to [https://ignite.apache.org/releases/1.0.0/javadoc/] > need to fix it to latest version of javadoc - > [https://ignite.apache.org/releases/latest/javadoc/] > Seems it issue for all other pages - need to recheck and fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9395) Incorrect link to javadoc
[ https://issues.apache.org/jira/browse/IGNITE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9395: -- Assignee: Artem Budnikov > Incorrect link to javadoc > - > > Key: IGNITE-9395 > URL: https://issues.apache.org/jira/browse/IGNITE-9395 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5, 2.6 >Reporter: Yury Gerzhedovich >Assignee: Artem Budnikov >Priority: Minor > > Javadoc's links refer to 1.0.0 version of Ignite instead of latest one. > For example at page [https://apacheignite.readme.io/docs/events] there is > link javadoc to [https://ignite.apache.org/releases/1.0.0/javadoc/] > need to fix it to latest version of javadoc - > [https://ignite.apache.org/releases/latest/javadoc/] > Seems it issue for all other pages - need to recheck and fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8286) ScanQuery ignore setLocal with non local partition
[ https://issues.apache.org/jira/browse/IGNITE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598756#comment-16598756 ] Ilya Lantukh commented on IGNITE-8286: -- [~agoncharuk], I think we can merge it into master and include into 2.7 now. > ScanQuery ignore setLocal with non local partition > -- > > Key: IGNITE-8286 > URL: https://issues.apache.org/jira/browse/IGNITE-8286 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Alexander Belyak >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > 1) Create partitioned cache on 2+ nodes cluster > 2) Select some partition N, local node should not be OWNER of partition N > 3) execute: cache.query(new ScanQuery<>().setLocal(true).setPartition(N)) > Expected result: > empty result (probaply with logging smth like "Trying to execute local query > with non local partition N") or even throw exception > Actual result: > executing (with ScanQueryFallbackClosableIterator) query on remote node. > Problem is that we execute local query on remote node. > Same behaviour can be achieved if we get empty node list from > GridCacheQueryAdapter.node() by any reasons, for example - if we run "local" > query from non data node from given cache (see > GridDiscoveryNamager.cacheAffinityNode(ClusterNode node, String cacheName) in > GridcacheQueryAdapter.executeScanQuery() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9446) MVCC: Races in Vacuum worker on cache stop.
Andrew Mashenkov created IGNITE-9446: Summary: MVCC: Races in Vacuum worker on cache stop. Key: IGNITE-9446 URL: https://issues.apache.org/jira/browse/IGNITE-9446 Project: Ignite Issue Type: Bug Reporter: Andrew Mashenkov For now, partition store BTree can be destroyed while vacuum in progress regardless partition reservations which causes VacuumTask failure. We should fix vacuum failure properly in that case. This should fix failed TC test CacheMvccPartitionedSqlQueriesTest.testDistributedJoinSimple() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4150) B-Tree index cannot be used efficiently with IN clause.
[
https://issues.apache.org/jira/browse/IGNITE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4150:
Ignite Flags: Docs Required
> B-Tree index cannot be used efficiently with IN clause.
> ---
>
> Key: IGNITE-4150
> URL: https://issues.apache.org/jira/browse/IGNITE-4150
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: performance
> Fix For: 2.7
>
>
> Consider the following query:
> {code}
> SELECT * FROM table
> WHERE a = ? AND b IN (?, ?)
> {code}
> If there is an index {{(a, b)}}, it will not be used properly: only column
> {{a}} will be used. This will leads to multiple unnecessary comparisons.
> Most obvious way to fix that - use temporary table and {{JOIN}}. However,
> this approach doesn't work well when there are multiple {{IN}}'s.
> Proper solution would be to hack deeper into H2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9387) [ML] Model updating
[ https://issues.apache.org/jira/browse/IGNITE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598716#comment-16598716 ] ASF GitHub Bot commented on IGNITE-9387: GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/4659 IGNITE-9387: update interface for trainers You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9387 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4659.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4659 commit 7633191513acacf689002584a7cbaf77e88beb13 Author: Alexey Platonov Date: 2018-08-27T11:18:17Z initial commit commit 3f2d5a4fd1c40ac243dcef30e062c69425ef1dec Author: Alexey Platonov Date: 2018-08-28T13:12:56Z update DatasetTrainer interface commit 8be18d70db897583c031cb890a1f5e204e909752 Author: Alexey Platonov Date: 2018-08-28T15:01:09Z SVM update interface implementation commit 783a14efed7a526dcad667475d1b3ace4817321b Author: Alexey Platonov Date: 2018-08-28T15:34:59Z MLP update interface realization commit 3b4eb27f049031f41985e9cafdebf6f6b660a9fe Author: Alexey Platonov Date: 2018-08-29T09:00:32Z LSQR update interface impl commit 6ebe65517b29e8a5cbd248f9fcf88bc5f5751073 Author: Alexey Platonov Date: 2018-08-29T09:47:11Z Logistic regression model update interface impl commit 8a65426175283234df2b40379a4c7838a665ca38 Author: Alexey Platonov Date: 2018-08-29T09:57:44Z Linear regression update interface impl commit 346fff9117ad039e9ae6b54d783f8b3d442ba461 Author: Alexey Platonov Date: 2018-08-29T11:22:48Z fix performance degradation due to Optional.orElse commit 1bff50603daa762213ff85f035c4c788e3206229 Author: Alexey Platonov Date: 2018-08-29T11:46:11Z kmeans update iface impl commit 1c509094330870dc6e7de9a1b6054218d02b51c5 Author: Alexey Platonov Date: 2018-08-29T12:30:58Z KNN update iface impl commit a360ad417d8c9a9a0d367e216a744e2c345335ce Author: Alexey Platonov Date: 2018-08-29T13:05:25Z Bagging model update iface impl commit cd66719ad0f1c8e537905ac3197d0b509e139fe7 Author: Alexey Platonov Date: 2018-08-29T15:58:29Z ANN update iface impl commit 267ab3f09266a97520eb3c8f1a023f310d1b564c Author: Alexey Platonov Date: 2018-08-30T08:33:26Z DT update iface support commit 96411664f1701075d9074f51bdd994ddf527fb67 Author: Alexey Platonov Date: 2018-08-30T08:54:49Z little refactoring commit c9d1563c4691a72ac1e1d7722db29609243ea511 Author: Alexey Platonov Date: 2018-08-30T09:15:59Z Impl of Exportable iface for ModelsComposition commit e5f2c63a2f9b7d30aeb5c5a169e52042f37279ce Author: Alexey Platonov Date: 2018-08-30T10:03:33Z add checkState iface commit 5bbac78355b7bc7ece578cac9ffb87d1bd7b2e0f Author: Alexey Platonov Date: 2018-08-30T10:26:22Z implement simple checkState for models commit c2e3dfec9b5dd4968cba5f678d09a265a3d5183c Author: Alexey Platonov Date: 2018-08-30T12:33:30Z add simple test to update for KMeans and KNN/ANN commit 9e740f590316dea69091132a11dad9c168a65be5 Author: Alexey Platonov Date: 2018-08-31T09:03:37Z merge with master commit 17070a8738c594fdf3616b2101342d62d94f291c Author: Alexey Platonov Date: 2018-08-31T09:04:12Z merge with master commit 635be783c1622657d68cfdcb46a23c917db3678e Author: Alexey Platonov Date: 2018-08-31T12:09:22Z add tests for corner cases for updating and shade NPE when dataset is empty while first learning commit 669e5adf70c75e6e8eefd74f4f158292eec81c22 Author: Alexey Platonov Date: 2018-08-31T13:04:05Z pre review check commit 9299c47bb71196daca06fe3fec703c62eef865f1 Author: Alexey Platonov Date: 2018-08-31T13:13:36Z pre review check > [ML] Model updating > --- > > Key: IGNITE-9387 > URL: https://issues.apache.org/jira/browse/IGNITE-9387 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > Fix For: 2.7 > > > In trainer interface we need to support model updating by batches after first > training -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9445) Use valid tag for page write unlock while reading cold page from disk.
Alexei Scherbakov created IGNITE-9445: - Summary: Use valid tag for page write unlock while reading cold page from disk. Key: IGNITE-9445 URL: https://issues.apache.org/jira/browse/IGNITE-9445 Project: Ignite Issue Type: Bug Reporter: Alexei Scherbakov Assignee: Alexei Scherbakov The problem arises when passing pageId with not actual page rotation tag to org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#acquirePage(int, long, boolean). It's not possible in advance to know the actual value without reading stored page. Such scenario may lead to locked forever page if passed and persisted tags are different. Solution - unlock page using actual(persisted) tag value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9445) Use valid tag for page write unlock while reading cold page from disk.
[ https://issues.apache.org/jira/browse/IGNITE-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-9445: -- Description: The problem arises when passing pageId with not actual page rotation tag to org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#acquirePage(int, long, boolean). It's not possible in advance to know the actual value without reading stored page. Such scenario may lead to locked forever page if passed and persisted tags are different. Solution - unlock the page using actual(persisted) tag value. was: The problem arises when passing pageId with not actual page rotation tag to org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#acquirePage(int, long, boolean). It's not possible in advance to know the actual value without reading stored page. Such scenario may lead to locked forever page if passed and persisted tags are different. Solution - unlock page using actual(persisted) tag value. > Use valid tag for page write unlock while reading cold page from disk. > -- > > Key: IGNITE-9445 > URL: https://issues.apache.org/jira/browse/IGNITE-9445 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > > The problem arises when passing pageId with not actual page rotation tag to > org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#acquirePage(int, > long, boolean). > It's not possible in advance to know the actual value without reading stored > page. > Such scenario may lead to locked forever page if passed and persisted tags > are different. > Solution - unlock the page using actual(persisted) tag value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9438) StandaloneWalRecordsIterator file descriptors leak
[
https://issues.apache.org/jira/browse/IGNITE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598651#comment-16598651
]
ASF GitHub Bot commented on IGNITE-9438:
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/4658
IGNITE-9438 fix standaloneWalRecordsIterator file descriptors leak.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-9438
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4658.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4658
commit 0f61bec40c021e3ac0aa0a62d401d6b0cbaed819
Author: Sergey Antonov
Date: 2018-08-31T12:01:21Z
IGNITE-9438 fix standaloneWalRecordsIterator file descriptors leak.
> StandaloneWalRecordsIterator file descriptors leak
> --
>
> Key: IGNITE-9438
> URL: https://issues.apache.org/jira/browse/IGNITE-9438
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.7
>
>
> In {{StandaloneWalRecordsIterator#initReadHandle()}} method are opens file
> descriptor.
> {code:java}
> FileIO fileIO = fd.isCompressed() ? new UnzipFileIO(fd.file()) :
> ioFactory.create(fd.file());
> {code}
> It not used after attempt to read segment header and it don't closed.
> Second time same file descriptor are opens in super method
> {{AbstractWalRecordsIterator#initReadHandle()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9442) Collocated IgniteSet#close is not working on non-affinity node.
[
https://issues.apache.org/jira/browse/IGNITE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-9442:
-
Description:
Simple reproducer:
{code:java}
public void testSetBlockOnCloseFromNonAffinityNode() throws Exception {
Ignite node = startGridsMultiThreaded(2);
ClusterNode locNode = node.cluster().localNode();
IgniteSet set = node.set("test",
new CollectionConfiguration().setCollocated(true).setNodeFilter(n
-> !locNode.equals(n)));
set.close();
GridTestUtils.assertThrows(log, new Callable() {
@Override public Void call() throws Exception {
set.add(1);
return null;
}
}, IllegalStateException.class, null);
}
{code}
IgniteSet should be blocked on all nodes before cleanup data.
was:
Simple reproducer:
{code:java}
public void testSetBlockOnCloseFromNonAffinityNode() throws Exception {
Ignite node = startGridsMultiThreaded(2);
ClusterNode locNode = node.cluster().localNode();
IgniteSet set = node.set("test",
new CollectionConfiguration().setCollocated(true).setNodeFilter(n
-> !F.eqNodes(locNode, n)));
set.close();
GridTestUtils.assertThrows(log, new Callable() {
@Override public Void call() throws Exception {
set.add(1);
return null;
}
}, IllegalStateException.class, null);
}
{code}
IgniteSet should be blocked on all nodes before cleanup data.
> Collocated IgniteSet#close is not working on non-affinity node.
> ---
>
> Key: IGNITE-9442
> URL: https://issues.apache.org/jira/browse/IGNITE-9442
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
> Simple reproducer:
> {code:java}
> public void testSetBlockOnCloseFromNonAffinityNode() throws Exception {
> Ignite node = startGridsMultiThreaded(2);
> ClusterNode locNode = node.cluster().localNode();
> IgniteSet set = node.set("test",
> new CollectionConfiguration().setCollocated(true).setNodeFilter(n
> -> !locNode.equals(n)));
> set.close();
> GridTestUtils.assertThrows(log, new Callable() {
> @Override public Void call() throws Exception {
> set.add(1);
> return null;
> }
> }, IllegalStateException.class, null);
> }
> {code}
> IgniteSet should be blocked on all nodes before cleanup data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8331) SQL: Add Decimal precision and scale constraint
[ https://issues.apache.org/jira/browse/IGNITE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetrovMikhail reassigned IGNITE-8331: - Assignee: PetrovMikhail > SQL: Add Decimal precision and scale constraint > --- > > Key: IGNITE-8331 > URL: https://issues.apache.org/jira/browse/IGNITE-8331 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: PetrovMikhail >Priority: Major > Labels: sql-engine > > We should support DECIMAL(X, Y) syntax. > Currently, we ignore it. > It affects semantics. > E.g., one can insert a DECIMAL with greater precision into a cache/table > without any problems. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8149) MVCC TX: Size method should use tx snapshot
[ https://issues.apache.org/jira/browse/IGNITE-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598492#comment-16598492 ] Igor Seliverstov commented on IGNITE-8149: -- [~vozerov], could you look at? > MVCC TX: Size method should use tx snapshot > --- > > Key: IGNITE-8149 > URL: https://issues.apache.org/jira/browse/IGNITE-8149 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > Currently cache.size() returns number of entries in cache trees while there > can be several versions of one key-value pairs. > We should use tx snapshot and count all passed mvcc filter entries instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9444) TcpDiscoveryCloudIpFinderSelfTest.testRackspace fails in master
[
https://issues.apache.org/jira/browse/IGNITE-9444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9444:
-
Fix Version/s: 2.7
> TcpDiscoveryCloudIpFinderSelfTest.testRackspace fails in master
> ---
>
> Key: IGNITE-9444
> URL: https://issues.apache.org/jira/browse/IGNITE-9444
> Project: Ignite
> Issue Type: Test
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7
>
>
> Looks like something changed in the rackspace infrastructure, the test
> started to fail with {{java.util.NoSuchElementException: apiType compute not
> found in catalog []}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9444) TcpDiscoveryCloudIpFinderSelfTest.testRackspace fails in master
[
https://issues.apache.org/jira/browse/IGNITE-9444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9444:
-
Description: Looks like something changed in the rackspace infrastructure,
the test started to fail with {{java.util.NoSuchElementException: apiType
compute not found in catalog []}}.
> TcpDiscoveryCloudIpFinderSelfTest.testRackspace fails in master
> ---
>
> Key: IGNITE-9444
> URL: https://issues.apache.org/jira/browse/IGNITE-9444
> Project: Ignite
> Issue Type: Test
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7
>
>
> Looks like something changed in the rackspace infrastructure, the test
> started to fail with {{java.util.NoSuchElementException: apiType compute not
> found in catalog []}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9444) TcpDiscoveryCloudIpFinderSelfTest.testRackspace fails in master
Alexey Goncharuk created IGNITE-9444: Summary: TcpDiscoveryCloudIpFinderSelfTest.testRackspace fails in master Key: IGNITE-9444 URL: https://issues.apache.org/jira/browse/IGNITE-9444 Project: Ignite Issue Type: Test Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9424) Partition equal to -1 during insert to atomic cache
[
https://issues.apache.org/jira/browse/IGNITE-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598477#comment-16598477
]
ASF GitHub Bot commented on IGNITE-9424:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4645
> Partition equal to -1 during insert to atomic cache
> ---
>
> Key: IGNITE-9424
> URL: https://issues.apache.org/jira/browse/IGNITE-9424
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Reproduced by IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite
> {noformat}
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1261)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1740)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1090)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.file.IgnitePdsThreadInterruptionTest$3.run(IgnitePdsThreadInterruptionTest.java:208)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:394)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1664)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:611)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2430)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2407)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1087)
> ... 3 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> update keys.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKey(UpdateErrors.java:108)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:329)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2623)
> at
>
[jira] [Updated] (IGNITE-9424) Partition equal to -1 during insert to atomic cache
[
https://issues.apache.org/jira/browse/IGNITE-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9424:
-
Labels: MakeTeamcityGreenAgain (was: )
> Partition equal to -1 during insert to atomic cache
> ---
>
> Key: IGNITE-9424
> URL: https://issues.apache.org/jira/browse/IGNITE-9424
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Reproduced by IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite
> {noformat}
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1261)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1740)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1090)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.file.IgnitePdsThreadInterruptionTest$3.run(IgnitePdsThreadInterruptionTest.java:208)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:394)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1664)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:611)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2430)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2407)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1087)
> ... 3 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> update keys.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKey(UpdateErrors.java:108)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:329)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2623)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1942)
> at
>
[jira] [Updated] (IGNITE-9424) Partition equal to -1 during insert to atomic cache
[
https://issues.apache.org/jira/browse/IGNITE-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9424:
-
Fix Version/s: 2.7
> Partition equal to -1 during insert to atomic cache
> ---
>
> Key: IGNITE-9424
> URL: https://issues.apache.org/jira/browse/IGNITE-9424
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Reproduced by IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite
> {noformat}
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1261)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1740)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1090)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.file.IgnitePdsThreadInterruptionTest$3.run(IgnitePdsThreadInterruptionTest.java:208)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:394)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1664)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:611)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2430)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2407)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1087)
> ... 3 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> update keys.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKey(UpdateErrors.java:108)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:329)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2623)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1942)
> at
>
[jira] [Updated] (IGNITE-9424) Partition equal to -1 during insert to atomic cache
[
https://issues.apache.org/jira/browse/IGNITE-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9424:
-
Ignite Flags: (was: Docs Required)
> Partition equal to -1 during insert to atomic cache
> ---
>
> Key: IGNITE-9424
> URL: https://issues.apache.org/jira/browse/IGNITE-9424
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Reproduced by IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite
> {noformat}
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1261)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1740)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1090)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.file.IgnitePdsThreadInterruptionTest$3.run(IgnitePdsThreadInterruptionTest.java:208)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [31108]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:394)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1664)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:611)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2430)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2407)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1087)
> ... 3 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> update keys.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKey(UpdateErrors.java:108)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:329)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2623)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1942)
> at
>
[jira] [Resolved] (IGNITE-9443) IgniteSet iterator created on client node is not working with the replicated cache.
[
https://issues.apache.org/jira/browse/IGNITE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin resolved IGNITE-9443.
--
Resolution: Duplicate
> IgniteSet iterator created on client node is not working with the replicated
> cache.
> ---
>
> Key: IGNITE-9443
> URL: https://issues.apache.org/jira/browse/IGNITE-9443
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
> IgniteSet iterator created on client node is not working with the replicated
> cache.
> Reproducer:
> {code:java}
> public void testClientIteratorOnReplicatedCache() throws Exception {
> startGrid(0);
> Ignition.setClientMode(true);
> Ignite client = startGrid(1);
> Ignition.setClientMode(false);
> IgniteSet set = client.set("test", new
> CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
> set.add(1);
> assertTrue(set.iterator().hasNext());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9443) IgniteSet iterator created on client node is not working with the replicated cache.
[
https://issues.apache.org/jira/browse/IGNITE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-9443:
-
Description:
IgniteSet iterator created on client node is not working with the replicated
cache.
Reproducer:
{code:java}
public void testClientIteratorOnReplicatedCache() throws Exception {
startGrid(0);
Ignition.setClientMode(true);
Ignite client = startGrid(1);
Ignition.setClientMode(false);
IgniteSet set = client.set("test", new
CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
set.add(1);
assertTrue(set.iterator().hasNext());
}
{code}
was:
IgniteSet iterator created on the client node is not working with the
replicated cache.
Reproducer:
{code:java}
public void testClientIteratorOnReplicatedCache() throws Exception {
startGrid(0);
Ignition.setClientMode(true);
Ignite client = startGrid(1);
Ignition.setClientMode(false);
IgniteSet set = client.set("test", new
CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
set.add(1);
assertTrue(set.iterator().hasNext());
}
{code}
> IgniteSet iterator created on client node is not working with the replicated
> cache.
> ---
>
> Key: IGNITE-9443
> URL: https://issues.apache.org/jira/browse/IGNITE-9443
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
> IgniteSet iterator created on client node is not working with the replicated
> cache.
> Reproducer:
> {code:java}
> public void testClientIteratorOnReplicatedCache() throws Exception {
> startGrid(0);
> Ignition.setClientMode(true);
> Ignite client = startGrid(1);
> Ignition.setClientMode(false);
> IgniteSet set = client.set("test", new
> CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
> set.add(1);
> assertTrue(set.iterator().hasNext());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9443) IgniteSet iterator created on the client node is not working with the replicated cache.
Pavel Pereslegin created IGNITE-9443:
Summary: IgniteSet iterator created on the client node is not
working with the replicated cache.
Key: IGNITE-9443
URL: https://issues.apache.org/jira/browse/IGNITE-9443
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.6
Reporter: Pavel Pereslegin
Assignee: Pavel Pereslegin
IgniteSet iterator created on the client node is not working with the
replicated cache.
Reproducer:
{code:java}
public void testClientIteratorOnReplicatedCache() throws Exception {
startGrid(0);
Ignition.setClientMode(true);
Ignite client = startGrid(1);
Ignition.setClientMode(false);
IgniteSet set = client.set("test", new
CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
set.add(1);
assertTrue(set.iterator().hasNext());
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9443) IgniteSet iterator created on client node is not working with the replicated cache.
[
https://issues.apache.org/jira/browse/IGNITE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-9443:
-
Summary: IgniteSet iterator created on client node is not working with the
replicated cache. (was: IgniteSet iterator created on the client node is not
working with the replicated cache.)
> IgniteSet iterator created on client node is not working with the replicated
> cache.
> ---
>
> Key: IGNITE-9443
> URL: https://issues.apache.org/jira/browse/IGNITE-9443
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
> IgniteSet iterator created on the client node is not working with the
> replicated cache.
> Reproducer:
> {code:java}
> public void testClientIteratorOnReplicatedCache() throws Exception {
> startGrid(0);
> Ignition.setClientMode(true);
> Ignite client = startGrid(1);
> Ignition.setClientMode(false);
> IgniteSet set = client.set("test", new
> CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
> set.add(1);
> assertTrue(set.iterator().hasNext());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9442) Collocated IgniteSet#close is not working on non-affinity node.
Pavel Pereslegin created IGNITE-9442:
Summary: Collocated IgniteSet#close is not working on non-affinity
node.
Key: IGNITE-9442
URL: https://issues.apache.org/jira/browse/IGNITE-9442
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.6
Reporter: Pavel Pereslegin
Assignee: Pavel Pereslegin
Simple reproducer:
{code:java}
public void testSetBlockOnCloseFromNonAffinityNode() throws Exception {
Ignite node = startGridsMultiThreaded(2);
ClusterNode locNode = node.cluster().localNode();
IgniteSet set = node.set("test",
new CollectionConfiguration().setCollocated(true).setNodeFilter(n
-> !F.eqNodes(locNode, n)));
set.close();
GridTestUtils.assertThrows(log, new Callable() {
@Override public Void call() throws Exception {
set.add(1);
return null;
}
}, IllegalStateException.class, null);
}
{code}
IgniteSet should be blocked on all nodes before cleanup data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9348) ML examples improvements, follow-up to IGNITE-9297
[ https://issues.apache.org/jira/browse/IGNITE-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598435#comment-16598435 ] ASF GitHub Bot commented on IGNITE-9348: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4641 > ML examples improvements, follow-up to IGNITE-9297 > -- > > Key: IGNITE-9348 > URL: https://issues.apache.org/jira/browse/IGNITE-9348 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Labels: examples > Fix For: 2.7 > > > After IGNITE-9297 was resolved, ML examples were discussed with some folks > ([~skozlov], [~avolkov], [~chief]) in order to check if some other > improvements may be desired. This ticket is to address obtained feedback. > List of points that look worth taking care of includes (but is not limited > to): > * some examples javadocs still looks like missing details (eg random forest) > * some mentions of algorithms (eg kNN, gradient boosting etc) are better to > be linked to respective introductory articles in order to help less > experienced users easier grasp the examples > * presence of some examples doesn't look justified (eg LocalDatasetExample) > * logging in some examples looks sub-optimal, either too brief or too lengthy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9348) ML examples improvements, follow-up to IGNITE-9297
[ https://issues.apache.org/jira/browse/IGNITE-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-9348: --- Labels: examples (was: ) > ML examples improvements, follow-up to IGNITE-9297 > -- > > Key: IGNITE-9348 > URL: https://issues.apache.org/jira/browse/IGNITE-9348 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Labels: examples > Fix For: 2.7 > > > After IGNITE-9297 was resolved, ML examples were discussed with some folks > ([~skozlov], [~avolkov], [~chief]) in order to check if some other > improvements may be desired. This ticket is to address obtained feedback. > List of points that look worth taking care of includes (but is not limited > to): > * some examples javadocs still looks like missing details (eg random forest) > * some mentions of algorithms (eg kNN, gradient boosting etc) are better to > be linked to respective introductory articles in order to help less > experienced users easier grasp the examples > * presence of some examples doesn't look justified (eg LocalDatasetExample) > * logging in some examples looks sub-optimal, either too brief or too lengthy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9033) .NET: specify expiry policy when creating cache using thin client
[ https://issues.apache.org/jira/browse/IGNITE-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598404#comment-16598404 ] Francisco Pareja edited comment on IGNITE-9033 at 8/31/18 8:14 AM: --- Hi, we are really interested in this feature as well. This also applies to the thin Java client. Thin clients can OPEN caches but they can also CREATE caches (_*igniteClient.getOrCreateCache(cacheName)*_). You can even pass a configuration to the created cache (*_ClientCacheConfiguration_*) but this configuration does not include Expiry policies. It is obviously missing. Can we change the name of this ticket to include Thin Clients from all platforms? was (Author: fpareja): Hi, we are really interested in this feature as well. This also applies to the thin Java client. Thin clients can OPEN caches but they can also CREATE caches (_*igniteClient.getOrCreateCache(cacheName)*_). You can even pass a configuration to the created cache (*_ClientCacheConfiguration_*) but this configuration does not include Expiry policies. It is obviously missing. Can we change the name of this tickets to include Thin Clients of all platforms? > .NET: specify expiry policy when creating cache using thin client > - > > Key: IGNITE-9033 > URL: https://issues.apache.org/jira/browse/IGNITE-9033 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Igor Sapego >Priority: Major > > Need to add ability to create dynamic caches specifying expiry policy with > thin client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9033) .NET: specify expiry policy when creating cache using thin client
[ https://issues.apache.org/jira/browse/IGNITE-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598404#comment-16598404 ] Francisco Pareja commented on IGNITE-9033: -- Hi, we are really interested in this feature as well. This also applies to the thin Java client. Thin clients can OPEN caches but they can also CREATE caches (_*igniteClient.getOrCreateCache(cacheName)*_). You can even pass a configuration to the created cache (*_ClientCacheConfiguration_*) but this configuration does not include Expiry policies. It is obviously missing. Can we change the name of this tickets to include Thin Clients of all platforms? > .NET: specify expiry policy when creating cache using thin client > - > > Key: IGNITE-9033 > URL: https://issues.apache.org/jira/browse/IGNITE-9033 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Igor Sapego >Priority: Major > > Need to add ability to create dynamic caches specifying expiry policy with > thin client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9433) Refactoring to improve constant usage for file suffixes
[ https://issues.apache.org/jira/browse/IGNITE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin reassigned IGNITE-9433: -- Assignee: Pavel Voronkin > Refactoring to improve constant usage for file suffixes > --- > > Key: IGNITE-9433 > URL: https://issues.apache.org/jira/browse/IGNITE-9433 > Project: Ignite > Issue Type: Task >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.7 > > > We need extract file suffix constants to avoid duplication of string > constants for zip files, like ".zip" and ".tmp" across the project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9441) Failed to read WAL record at position
[ https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598392#comment-16598392 ] ASF GitHub Bot commented on IGNITE-9441: GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/4657 IGNITE-9441 check crc only if record read correct You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9441 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4657.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4657 commit 337bfe6c0b728e94f00c8552ca001a438338e40e Author: Anton Kalashnikov Date: 2018-08-31T07:58:04Z IGNITE-9441 check crc only if record read correct > Failed to read WAL record at position > - > > Key: IGNITE-9441 > URL: https://issues.apache.org/jira/browse/IGNITE-9441 > Project: Ignite > Issue Type: Test >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > > IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology > IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad > IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9441) Failed to read WAL record at position
Anton Kalashnikov created IGNITE-9441: - Summary: Failed to read WAL record at position Key: IGNITE-9441 URL: https://issues.apache.org/jira/browse/IGNITE-9441 Project: Ignite Issue Type: Test Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9309) LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate
[
https://issues.apache.org/jira/browse/IGNITE-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ostanin reassigned IGNITE-9309:
Assignee: Oleg Ostanin
> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to
> processFullPartitionUpdate
> -
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Assignee: Oleg Ostanin
>Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java,
> node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics
> calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount
> (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of
> [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
