[jira] [Created] (IGNITE-12372) Thin Jdbc driver with collocated=true return per node results
Sergey Kozlov created IGNITE-12372:
--
Summary: Thin Jdbc driver with collocated=true return per node
results
Key: IGNITE-12372
URL: https://issues.apache.org/jira/browse/IGNITE-12372
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7.6
Reporter: Sergey Kozlov
# Start two nodes (in-memory)
# Run sqlline \{{>bin\sqlline.bat -d org.apache.ignite.IgniteJdbcThinDriver -u
jdbc:ignite:thin://127.0.0.1/?collocated=true}}
# Create a table and select aggregation functions:
{noformat}
: jdbc:ignite:thin://127.0.0.1/> create table t1 (a int not null primary key, b
varchar) with "template=partitioned";
No rows affected (0,15 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1, 'a'), (2, 'b'), (3,
'c'), (4, 'd');
4 rows affected (0,091 seconds)
0: jdbc:ignite:thin://127.0.0.1/> select * from t1;
+++
| A | B |
+++
| 1 | a |
| 2 | b |
| 4 | d |
| 3 | c |
+++
4 rows selected (0,074 seconds)
0: jdbc:ignite:thin://127.0.0.1/> select count(*) from t1;
++
| COUNT(*) |
++
| 3 |
| 1 |
++
2 rows selected (0,011 seconds)
0: jdbc:ignite:thin://127.0.0.1/> select min(a), max(b) from t1;
+++
| MIN(A) | MAX(B) |
+++
| 1 | d |
| 3 | c |
+++
2 rows selected (0,012 seconds)
0: jdbc:ignite:thin://127.0.0.1/> select min(a), max(a) from t1;
+++
| MIN(A) | MAX(A) |
+++
| 1 | 4 |
| 3 | 3 |
+++
2 rows selected (0,01 seconds)
0: jdbc:ignite:thin://127.0.0.1/>
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-11835) Support JMX/control.sh API for page lock dump
[
https://issues.apache.org/jira/browse/IGNITE-11835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854537#comment-16854537
]
Sergey Kozlov edited comment on IGNITE-11835 at 6/3/19 12:30 PM:
-
[~DmitriyGovorukhin]
I would like to suggest to improve new commands for {{control.sh}}:
{noformat}
--diagnostic pageLocks dump [--path path_to_file] [--all|--nodes
nodeId1,nodeId2,..|--nodes consistentId1,consistentId2,..]
--diagnostic pageLocks dump_log [--all|--nodes nodeId1,nodeId2,..|--nodes
consistentId1,consistentId2,..]
{noformat}
was (Author: skozlov):
[~DmitriyGovorukhin]
I would like to suggest to improve new commands for {{control.sh}}:
{noformat}
--diagnostic pageLocks dump [--path {path_to_file}] [--all|--nodes
nodeId1,nodeId2,..|--nodes consistentId1,consistentId2,..]
--diagnostic pageLocks dump_log [--all|--nodes nodeId1,nodeId2,..|--nodes
consistentId1,consistentId2,..]
{noformat}
> Support JMX/control.sh API for page lock dump
> -
>
> Key: IGNITE-11835
> URL: https://issues.apache.org/jira/browse/IGNITE-11835
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> Support JMX/control.sh API for page lock dump
> JMX
> {code}
> public interface PageLockMXBean {
> String dumpLocks();
> void dumpLocksToLog();
> String dumpLocksToFile();
> String dumpLocksToFile(String path);
> }
> {code}
> control.sh
> {code}
> --diagnostic pageLocks dump // Save dump to file generated in
> IGNITE_HOME/work dir.
> --diagnostic pageLocks dump log // Print dump to console on node.
> --diagnostic pageLocks dump {path} // Save dump to specific path.
> --diagnostic pageLocks dump -a or --all // Dump on all nodes.
> --diagnostic pageLocks dump {UUID} {UUID} or {constId} {constId} // Dump
> on subset nodes.
> {code}
> HeapArrayLockStack and HeapArrayLockStack output:
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.PageLockStackTest#testThreeReadPageLock_3
> {code}
> Locked pages = []
> Locked pages stack: main time=(1559050284306, 2019-05-28 16:31:24.306)
> -> Try Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284393, 2019-05-28 16:31:24.393)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> -> Try Read lock structureId=123 pageId=11 [pageIdHex=000b,
> partId=11, pageIdx=11, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [11(r=1|w=0),1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=11 [pageIdHex=000b,
> partId=11, pageIdx=11, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> -> Try Read lock structureId=123 pageId=111
> [pageIdHex=006f, partId=111, pageIdx=111, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [111(r=1|w=0),1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=111 [pageIdHex=006f,
> partId=111, pageIdx=111, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = []
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> {code}
> HeapArrayLockLog and OffHeapLockLog
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.PageLockLogTest#testThreeReadPageLock_3
> {code}
> Locked pages = []
> Locked pages log: main time=(1559049634782, 2019-05-28 16:20:34.782)
> -> Try Read lock nextOpPageId=1, nextOpStructureId=123
> [pageIdHex=0001, partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked
[jira] [Comment Edited] (IGNITE-11835) Support JMX/control.sh API for page lock dump
[
https://issues.apache.org/jira/browse/IGNITE-11835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854537#comment-16854537
]
Sergey Kozlov edited comment on IGNITE-11835 at 6/3/19 12:28 PM:
-
[~DmitriyGovorukhin]
I would like to suggest to improve new commands for {{control.sh}}:
{noformat}
--diagnostic pageLocks dump [--path {path_to_file}] [--all|--nodes
nodeId1,nodeId2,..|--nodes consistentId1,consistentId2,..]
--diagnostic pageLocks dump_log [--all|--nodes nodeId1,nodeId2,..|--nodes
consistentId1,consistentId2,..]
{noformat}
was (Author: skozlov):
[~DmitriyGovorukhin]
I would like to suggest to improve new commands for {{control.sh}}:
{noformat}
--diagnostic pageLocks dump [--path {path_to_file}]
[--all|nodeId1,nodeId2,..|consistentId1,consistentId2,..]
--diagnostic pageLocks dump_log
[--all|nodeId1,nodeId2,..|consistentId1,consistentId2,..]
{noformat}
> Support JMX/control.sh API for page lock dump
> -
>
> Key: IGNITE-11835
> URL: https://issues.apache.org/jira/browse/IGNITE-11835
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> Support JMX/control.sh API for page lock dump
> JMX
> {code}
> public interface PageLockMXBean {
> String dumpLocks();
> void dumpLocksToLog();
> String dumpLocksToFile();
> String dumpLocksToFile(String path);
> }
> {code}
> control.sh
> {code}
> --diagnostic pageLocks dump // Save dump to file generated in
> IGNITE_HOME/work dir.
> --diagnostic pageLocks dump log // Print dump to console on node.
> --diagnostic pageLocks dump {path} // Save dump to specific path.
> --diagnostic pageLocks dump -a or --all // Dump on all nodes.
> --diagnostic pageLocks dump {UUID} {UUID} or {constId} {constId} // Dump
> on subset nodes.
> {code}
> HeapArrayLockStack and HeapArrayLockStack output:
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.PageLockStackTest#testThreeReadPageLock_3
> {code}
> Locked pages = []
> Locked pages stack: main time=(1559050284306, 2019-05-28 16:31:24.306)
> -> Try Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284393, 2019-05-28 16:31:24.393)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> -> Try Read lock structureId=123 pageId=11 [pageIdHex=000b,
> partId=11, pageIdx=11, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [11(r=1|w=0),1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=11 [pageIdHex=000b,
> partId=11, pageIdx=11, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> -> Try Read lock structureId=123 pageId=111
> [pageIdHex=006f, partId=111, pageIdx=111, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [111(r=1|w=0),1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=111 [pageIdHex=006f,
> partId=111, pageIdx=111, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = []
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> {code}
> HeapArrayLockLog and OffHeapLockLog
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.PageLockLogTest#testThreeReadPageLock_3
> {code}
> Locked pages = []
> Locked pages log: main time=(1559049634782, 2019-05-28 16:20:34.782)
> -> Try Read lock nextOpPageId=1, nextOpStructureId=123
> [pageIdHex=0001, partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages log: main
[jira] [Commented] (IGNITE-11835) Support JMX/control.sh API for page lock dump
[
https://issues.apache.org/jira/browse/IGNITE-11835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854537#comment-16854537
]
Sergey Kozlov commented on IGNITE-11835:
[~DmitriyGovorukhin]
I would like to suggest to improve new commands for {{control.sh}}:
{noformat}
--diagnostic pageLocks dump [--path {path_to_file}]
[--all|nodeId1,nodeId2,..|consistentId1,consistentId2,..]
--diagnostic pageLocks dump_log
[--all|nodeId1,nodeId2,..|consistentId1,consistentId2,..]
{noformat}
> Support JMX/control.sh API for page lock dump
> -
>
> Key: IGNITE-11835
> URL: https://issues.apache.org/jira/browse/IGNITE-11835
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> Support JMX/control.sh API for page lock dump
> JMX
> {code}
> public interface PageLockMXBean {
> String dumpLocks();
> void dumpLocksToLog();
> String dumpLocksToFile();
> String dumpLocksToFile(String path);
> }
> {code}
> control.sh
> {code}
> --diagnostic pageLocks dump // Save dump to file generated in
> IGNITE_HOME/work dir.
> --diagnostic pageLocks dump log // Print dump to console on node.
> --diagnostic pageLocks dump {path} // Save dump to specific path.
> --diagnostic pageLocks dump -a or --all // Dump on all nodes.
> --diagnostic pageLocks dump {UUID} {UUID} or {constId} {constId} // Dump
> on subset nodes.
> {code}
> HeapArrayLockStack and HeapArrayLockStack output:
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.PageLockStackTest#testThreeReadPageLock_3
> {code}
> Locked pages = []
> Locked pages stack: main time=(1559050284306, 2019-05-28 16:31:24.306)
> -> Try Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284393, 2019-05-28 16:31:24.393)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> -> Try Read lock structureId=123 pageId=11 [pageIdHex=000b,
> partId=11, pageIdx=11, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [11(r=1|w=0),1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=11 [pageIdHex=000b,
> partId=11, pageIdx=11, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> -> Try Read lock structureId=123 pageId=111
> [pageIdHex=006f, partId=111, pageIdx=111, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [111(r=1|w=0),1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=111 [pageIdHex=006f,
> partId=111, pageIdx=111, flags=]
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> Read lock structureId=123 pageId=1 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = []
> Locked pages stack: main time=(1559050284394, 2019-05-28 16:31:24.394)
> {code}
> HeapArrayLockLog and OffHeapLockLog
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.PageLockLogTest#testThreeReadPageLock_3
> {code}
> Locked pages = []
> Locked pages log: main time=(1559049634782, 2019-05-28 16:20:34.782)
> -> Try Read lock nextOpPageId=1, nextOpStructureId=123
> [pageIdHex=0001, partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages log: main time=(1559049634782, 2019-05-28 16:20:34.782)
> L=1 -> Read lock pageId=1, structureId=123 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> Locked pages = [1(r=1|w=0)]
> Locked pages log: main time=(1559049634782, 2019-05-28 16:20:34.782)
> L=1 -> Read lock pageId=1, structureId=123 [pageIdHex=0001,
> partId=1, pageIdx=1, flags=]
> -> Try Read lock nextOpPageId=11, nextOpStructureId=123
>
[jira] [Closed] (IGNITE-2256) Stopped cache with enabled metrics causes java.lang.IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov closed IGNITE-2256.
-
> Stopped cache with enabled metrics causes java.lang.IllegalArgumentException
>
>
> Key: IGNITE-2256
> URL: https://issues.apache.org/jira/browse/IGNITE-2256
> Project: Ignite
> Issue Type: Bug
> Components: cache, UI
>Affects Versions: 1.5.0.final
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
>Priority: Major
>
> Sometimes stop of a cache with enabled metrics causes
> java.lang.IllegalArgumentException
> {noformat}
> [01:56:25,226][SEVERE][mgmt-#59%null%][GridJobWorker] Failed to execute job
> due to unexpected runtime exception
> [jobId=704ce01d151-07c43726-096b-4931-94b4-8e744c2330d3,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.v.cache.VisorCacheMetricsCollectorTask, dep=LocalDeployment
> [super=GridDeployment [ts=1450911364031, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
> clsLdrId=fb37e01d151-07c43726-096b-4931-94b4-8e744c2330d3, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.v.cache.VisorCacheMetricsCollectorTask,
> sesId=504ce01d151-23bcc212-8c7d-4aeb-b7ec-1959089e5376,
> startTime=1450911385197, endTime=9223372036854775807,
> taskNodeId=23bcc212-8c7d-4aeb-b7ec-1959089e5376,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
> failSpi=null, loadSpi=null, usage=1, fullSup=false,
> subjId=23bcc212-8c7d-4aeb-b7ec-1959089e5376, mapFut=IgniteFuture
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1450911385217,
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]],
> jobId=704ce01d151-07c43726-096b-4931-94b4-8e744c2330d3]]
> java.lang.IllegalArgumentException: Cache is not configured:
> replicated_cache_for_clear_and_stop
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3135)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetrics.from(VisorCacheMetrics.java:178)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetricsCollectorTask$VisorCacheMetricsCollectorJob.run(VisorCacheMetricsCollectorTask.java:117)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetricsCollectorTask$VisorCacheMetricsCollectorJob.run(VisorCacheMetricsCollectorTask.java:78)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-2256) Stopped cache with enabled metrics causes java.lang.IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov resolved IGNITE-2256.
---
Resolution: Cannot Reproduce
> Stopped cache with enabled metrics causes java.lang.IllegalArgumentException
>
>
> Key: IGNITE-2256
> URL: https://issues.apache.org/jira/browse/IGNITE-2256
> Project: Ignite
> Issue Type: Bug
> Components: cache, UI
>Affects Versions: 1.5.0.final
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
>Priority: Major
>
> Sometimes stop of a cache with enabled metrics causes
> java.lang.IllegalArgumentException
> {noformat}
> [01:56:25,226][SEVERE][mgmt-#59%null%][GridJobWorker] Failed to execute job
> due to unexpected runtime exception
> [jobId=704ce01d151-07c43726-096b-4931-94b4-8e744c2330d3,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.v.cache.VisorCacheMetricsCollectorTask, dep=LocalDeployment
> [super=GridDeployment [ts=1450911364031, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
> clsLdrId=fb37e01d151-07c43726-096b-4931-94b4-8e744c2330d3, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.v.cache.VisorCacheMetricsCollectorTask,
> sesId=504ce01d151-23bcc212-8c7d-4aeb-b7ec-1959089e5376,
> startTime=1450911385197, endTime=9223372036854775807,
> taskNodeId=23bcc212-8c7d-4aeb-b7ec-1959089e5376,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
> failSpi=null, loadSpi=null, usage=1, fullSup=false,
> subjId=23bcc212-8c7d-4aeb-b7ec-1959089e5376, mapFut=IgniteFuture
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1450911385217,
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]],
> jobId=704ce01d151-07c43726-096b-4931-94b4-8e744c2330d3]]
> java.lang.IllegalArgumentException: Cache is not configured:
> replicated_cache_for_clear_and_stop
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3135)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetrics.from(VisorCacheMetrics.java:178)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetricsCollectorTask$VisorCacheMetricsCollectorJob.run(VisorCacheMetricsCollectorTask.java:117)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetricsCollectorTask$VisorCacheMetricsCollectorJob.run(VisorCacheMetricsCollectorTask.java:78)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-2256) Stopped cache with enabled metrics causes java.lang.IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov reassigned IGNITE-2256:
-
Assignee: Sergey Kozlov (was: Yakov Zhdanov)
> Stopped cache with enabled metrics causes java.lang.IllegalArgumentException
>
>
> Key: IGNITE-2256
> URL: https://issues.apache.org/jira/browse/IGNITE-2256
> Project: Ignite
> Issue Type: Bug
> Components: cache, UI
>Affects Versions: 1.5.0.final
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Major
>
> Sometimes stop of a cache with enabled metrics causes
> java.lang.IllegalArgumentException
> {noformat}
> [01:56:25,226][SEVERE][mgmt-#59%null%][GridJobWorker] Failed to execute job
> due to unexpected runtime exception
> [jobId=704ce01d151-07c43726-096b-4931-94b4-8e744c2330d3,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.v.cache.VisorCacheMetricsCollectorTask, dep=LocalDeployment
> [super=GridDeployment [ts=1450911364031, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
> clsLdrId=fb37e01d151-07c43726-096b-4931-94b4-8e744c2330d3, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.v.cache.VisorCacheMetricsCollectorTask,
> sesId=504ce01d151-23bcc212-8c7d-4aeb-b7ec-1959089e5376,
> startTime=1450911385197, endTime=9223372036854775807,
> taskNodeId=23bcc212-8c7d-4aeb-b7ec-1959089e5376,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
> failSpi=null, loadSpi=null, usage=1, fullSup=false,
> subjId=23bcc212-8c7d-4aeb-b7ec-1959089e5376, mapFut=IgniteFuture
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1450911385217,
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]],
> jobId=704ce01d151-07c43726-096b-4931-94b4-8e744c2330d3]]
> java.lang.IllegalArgumentException: Cache is not configured:
> replicated_cache_for_clear_and_stop
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3135)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetrics.from(VisorCacheMetrics.java:178)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetricsCollectorTask$VisorCacheMetricsCollectorJob.run(VisorCacheMetricsCollectorTask.java:117)
> at
> org.apache.ignite.internal.visor.cache.VisorCacheMetricsCollectorTask$VisorCacheMetricsCollectorJob.run(VisorCacheMetricsCollectorTask.java:78)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798831#comment-16798831
]
Sergey Kozlov commented on IGNITE-11588:
probably the linked isssues will be fixed as well
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11588:
---
Ignite Flags: (was: Docs Required)
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11588:
---
Attachment: query-example-fix.xml
query_example.cpp
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11588:
---
Description:
I use modified C++ Query Example (see attached files) that verify the received
result against expected one and print out message if they're different.
Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and build
example project
1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
2. Run query-example.exe:
{noformat}
[13:35:48] Ignite node started OK (id=1e2c0f81)
[13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
>>> Cache query example started.
Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
[13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
>>> Example finished, press 'Enter' to exit ...
{noformat}
3. All next runs have no failures
was:
I use modified C++ Query Example (see attached files) that verify the received
result against expected one and print out message if they're different.
Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and build
example project
1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
2. Run query-example.exe:
{noformat}
[13:35:48] Ignite node started OK (id=1e2c0f81)
[13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
>>> Cache query example started.
Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
[13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
>>> Example finished, press 'Enter' to exit ...
{noformat}
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Priority: Major
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees,
[jira] [Created] (IGNITE-11588) The wrong result for Query
Sergey Kozlov created IGNITE-11588:
--
Summary: The wrong result for Query
Key: IGNITE-11588
URL: https://issues.apache.org/jira/browse/IGNITE-11588
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.7
Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
Reporter: Sergey Kozlov
I use modified C++ Query Example (see attached files) that verify the received
result against expected one and print out message if they're different.
Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and build
example project
1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
2. Run query-example.exe:
{noformat}
[13:35:48] Ignite node started OK (id=1e2c0f81)
[13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
>>> Cache query example started.
Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
found: 2000
[13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
>>> Example finished, press 'Enter' to exit ...
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11586) Update platforms/cpp/DEVNOTES.txt: OpenSSL
[
https://issues.apache.org/jira/browse/IGNITE-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11586:
---
Summary: Update platforms/cpp/DEVNOTES.txt: OpenSSL (was: Update
platforms/cpp/DEVNOTES.txt)
> Update platforms/cpp/DEVNOTES.txt: OpenSSL
> ---
>
> Key: IGNITE-11586
> URL: https://issues.apache.org/jira/browse/IGNITE-11586
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10 Pro, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.8
>
>
> ODBC compilation required OpenSSL headers and the project compilation fails
> due to unable to open {{include/openssl/ssl.h}}. I suggest to add the
> requirement to install OpenSSL and set the corresponding environment variable:
> {noformat}
> Building on Windows with Visual Studio (tm)
> --
> Common Requirements:
> ...
> * OPENSSL_HOME environment variable must be set pointing to OpenSSL
> installation directory.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11586) Update platforms/cpp/DEVNOTES.txt
Sergey Kozlov created IGNITE-11586:
--
Summary: Update platforms/cpp/DEVNOTES.txt
Key: IGNITE-11586
URL: https://issues.apache.org/jira/browse/IGNITE-11586
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.7
Environment: Windows 10 Pro, Visual Studio 2010 Pro, Oracle JDK 8
Reporter: Sergey Kozlov
Fix For: 2.8
ODBC compilation required OpenSSL headers and the project compilation fails due
to unable to open {{include/openssl/ssl.h}}. I suggest to add the requirement
to install OpenSSL and set the corresponding environment variable:
{noformat}
Building on Windows with Visual Studio (tm)
--
Common Requirements:
...
* OPENSSL_HOME environment variable must be set pointing to OpenSSL
installation directory.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA {{examples/pom.xml}} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA examples}/pom.xml with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO]
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA examples}/pom.xml with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA {{ examples}/pom.xml }} with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA {{ examples}/pom.xml }} with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA {{examples}/pom.xml}} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA {{examples}/pom.xml}} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA {{examples}/pom.xml} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[jira] [Created] (IGNITE-11501) Build examples failed with Scala profile and Java11
Sergey Kozlov created IGNITE-11501:
--
Summary: Build examples failed with Scala profile and Java11
Key: IGNITE-11501
URL: https://issues.apache.org/jira/browse/IGNITE-11501
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 2.7
Environment: Open JDK 11.0.1, Windows 10 64bit
Reporter: Sergey Kozlov
Import in IDEA {{examples}/pom.xml} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11421) There's no AI version in ODBC driver available for the connected client
[
https://issues.apache.org/jira/browse/IGNITE-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11421:
---
Summary: There's no AI version in ODBC driver available for the connected
client (was: There's no AI version in ODBC driver available for a connection)
> There's no AI version in ODBC driver available for the connected client
> ---
>
> Key: IGNITE-11421
> URL: https://issues.apache.org/jira/browse/IGNITE-11421
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
>
> I use {{pyodbc}} and successfuly connected to AI cluster
> But all connections attributes have no AI version:
> {noformat}
> conn = drv.connect('odbc', '127.0.0.1', 10800)
> print(conn.getinfo(SQL_DRIVER_NAME))
> Apache Ignite
> print(conn.getinfo(SQL_DRIVER_ODBC_VER))
> 03.00
> print(conn.getinfo(SQL_DRIVER_VER))
> 02.04.
> print(conn.getinfo(SQL_DBMS_VER))
> 02.04.
> print(conn.getinfo(SQL_ODBC_VER ))
> 03.80.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11421) There's no AI version in ODBC driver available for a connection
[
https://issues.apache.org/jira/browse/IGNITE-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11421:
---
Description:
I use {{pyodbc}} and successfuly connected to AI cluster
But all connections attributes have no AI version:
{noformat}
conn = drv.connect('odbc', '127.0.0.1', 10800)
print(conn.getinfo(SQL_DRIVER_NAME))
Apache Ignite
print(conn.getinfo(SQL_DRIVER_ODBC_VER))
03.00
print(conn.getinfo(SQL_DRIVER_VER))
02.04.
print(conn.getinfo(SQL_DBMS_VER))
02.04.
print(conn.getinfo(SQL_ODBC_VER ))
03.80.
{noformat}
was:
I use {{pyodbc}} and successfuly connected to AI cluster
But all connections attributes have no AI version:
{noformat}
print(conn.getinfo(SQL_DRIVER_NAME))
Apache Ignite
print(conn.getinfo(SQL_DRIVER_ODBC_VER))
03.00
print(conn.getinfo(SQL_DRIVER_VER))
02.04.
print(conn.getinfo(SQL_DBMS_VER))
02.04.
print(conn.getinfo(SQL_ODBC_VER ))
03.80.
{noformat}
> There's no AI version in ODBC driver available for a connection
> ---
>
> Key: IGNITE-11421
> URL: https://issues.apache.org/jira/browse/IGNITE-11421
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
>
> I use {{pyodbc}} and successfuly connected to AI cluster
> But all connections attributes have no AI version:
> {noformat}
> conn = drv.connect('odbc', '127.0.0.1', 10800)
> print(conn.getinfo(SQL_DRIVER_NAME))
> Apache Ignite
> print(conn.getinfo(SQL_DRIVER_ODBC_VER))
> 03.00
> print(conn.getinfo(SQL_DRIVER_VER))
> 02.04.
> print(conn.getinfo(SQL_DBMS_VER))
> 02.04.
> print(conn.getinfo(SQL_ODBC_VER ))
> 03.80.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11421) There's no AI version in ODBC driver available for a connection
Sergey Kozlov created IGNITE-11421:
--
Summary: There's no AI version in ODBC driver available for a
connection
Key: IGNITE-11421
URL: https://issues.apache.org/jira/browse/IGNITE-11421
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.7
Reporter: Sergey Kozlov
I use {{pyodbc}} and successfuly connected to AI cluster
But all connections attributes have no AI version:
{noformat}
print(conn.getinfo(SQL_DRIVER_NAME))
Apache Ignite
print(conn.getinfo(SQL_DRIVER_ODBC_VER))
03.00
print(conn.getinfo(SQL_DRIVER_VER))
02.04.
print(conn.getinfo(SQL_DBMS_VER))
02.04.
print(conn.getinfo(SQL_ODBC_VER ))
03.80.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11363) Document replicated cache performance degradation.
[ https://issues.apache.org/jira/browse/IGNITE-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov updated IGNITE-11363: --- Description: The perfomance degradation for REPLICATED caches should be properly docemented > Document replicated cache performance degradation. > -- > > Key: IGNITE-11363 > URL: https://issues.apache.org/jira/browse/IGNITE-11363 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Kozlov >Priority: Major > Fix For: 2.8 > > > The perfomance degradation for REPLICATED caches should be properly docemented -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11363) Document replicated cache performance degradation.
[ https://issues.apache.org/jira/browse/IGNITE-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov updated IGNITE-11363: --- Component/s: documentation > Document replicated cache performance degradation. > -- > > Key: IGNITE-11363 > URL: https://issues.apache.org/jira/browse/IGNITE-11363 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Kozlov >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11363) Document replicated cache performance degradation.
Sergey Kozlov created IGNITE-11363: -- Summary: Document replicated cache performance degradation. Key: IGNITE-11363 URL: https://issues.apache.org/jira/browse/IGNITE-11363 Project: Ignite Issue Type: Task Reporter: Sergey Kozlov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5293) Replicated cache performance degradation.
[
https://issues.apache.org/jira/browse/IGNITE-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-5293:
--
Ignite Flags: Docs Required
> Replicated cache performance degradation.
> -
>
> Key: IGNITE-5293
> URL: https://issues.apache.org/jira/browse/IGNITE-5293
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Semen Boikov
>Priority: Major
>
> With increase in number of nodes puts to replicated cache are slowed down
> almost in the same proportion.
> Unit test reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.internal.processors.cache.distributed.replicated;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> /**
> * Tests replicated cache performance .
> */
> public class GridCacheReplicatedTransactionalDegradationTest extends
> GridCommonAbstractTest {
> /** Keys. */
> private static final int KEYS = 100_000;
> @Override protected IgniteConfiguration getConfiguration(String gridName)
> throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(gridName);
> cfg.setClientMode(gridName.startsWith("client"));
> CacheConfiguration ccfg = new CacheConfiguration();
> ccfg.setCacheMode(CacheMode.REPLICATED);
> ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
>
> ccfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> ccfg.setName("test");
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> /** */
> public void testThroughput() throws Exception {
> try {
> IgniteEx grid0 = startGrid(0);
> Ignite client = startGrid("client");
> IgniteCache cache =
> client.getOrCreateCache("test");
> doTest(client, cache);
> startGrid(1);
> doTest(client, cache);
> startGrid(2);
> doTest(client, cache);
> } finally {
> stopAllGrids();
> }
> }
> /**
> * @param client
> * @param cache Cache.
> */
> private void doTest(Ignite client, IgniteCache cache) {
> long t1 = System.currentTimeMillis();
> for (int i = 0; i < KEYS; i++) {
> try (Transaction tx =
> client.transactions().txStart(TransactionConcurrency.PESSIMISTIC,
> TransactionIsolation.REPEATABLE_READ)) {
> cache.put(i, i);
> tx.commit();
> }
> }
> log.info("TPS: " + Math.round(KEYS /
> (float)(System.currentTimeMillis() - t1) * 1000));
> }
> }
> {noformat}
> My test results are:
> 1. transactional cache, explicit transaction.
> TPS: 2507
> TPS: 1660
> TPS: 1148
> 2. atomic cache
> TPS: 6416
> TPS: 5177
> TPS: 4403
> 3. transactional cache, no explicit transaction
> TPS: 4485
> TPS: 2289
> TPS: 1439
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11328) Ignite binary build is too big
Sergey Kozlov created IGNITE-11328:
--
Summary: Ignite binary build is too big
Key: IGNITE-11328
URL: https://issues.apache.org/jira/browse/IGNITE-11328
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8
Reporter: Sergey Kozlov
Fix For: 2.8
I built Apache Ignite and get zip file is ~ 800MB.
+400MB added by 4 ML modules in {{libs/optional}}
Looks like it should be redesigned (join in a single module and at least it
will remove same deps)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11249) Client failed to putAll/removeAll into mvcc cache during server node restarts
Sergey Kozlov created IGNITE-11249:
--
Summary: Client failed to putAll/removeAll into mvcc cache during
server node restarts
Key: IGNITE-11249
URL: https://issues.apache.org/jira/browse/IGNITE-11249
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Sergey Kozlov
Attachments: CachePutAllGetAllExample.java,
ExampleNodeStartupRestart.java
Use IDEa and ignite-example project
1. Run {{ExampleNodeStartup}}
2. Run {{ExampleNodeStartupRestart}}
3. Run {{CachePutAllGetAllExample}} and it fails atfter a few iterations:
{noformat}
[2019-02-07 18:39:00,110][INFO ][sys-#40][GridDhtPartitionsExchangeFuture]
Finish exchange future [startVer=AffinityTopologyVersion [topVer=5,
minorTopVer=1], resVer=AffinityTopologyVersion [topVer=5, minorTopVer=1],
err=null]
[2019-02-07 18:39:00,116][INFO ][sys-#40][GridDhtPartitionsExchangeFuture]
Completed partition exchange [localNode=f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8,
exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion
[topVer=5, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT, evtNode=TcpDiscoveryNode
[id=9f903121-c4d6-433f-ba62-6f864d967de9, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.25.4.52], sockAddrs=[work-pc.gridgain.local/172.25.4.52:47500,
/0:0:0:0:0:0:0:1:47500, /127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1549553936989, loc=false, ver=2.7.2#20190205-sha1:43e3211d,
isClient=false], done=true], topVer=AffinityTopologyVersion [topVer=5,
minorTopVer=1]]
[2019-02-07 18:39:00,116][INFO ][sys-#40][GridDhtPartitionsExchangeFuture]
Exchange timings [startVer=AffinityTopologyVersion [topVer=5, minorTopVer=1],
resVer=AffinityTopologyVersion [topVer=5, minorTopVer=1], stage="Waiting in
exchange queue" (0 ms), stage="Exchange parameters initialization" (0 ms),
stage="Determine exchange type" (5 ms), stage="Waiting for Full message" (176
ms), stage="Affinity recalculation" (0 ms), stage="Full map updating" (3 ms),
stage="Exchange done" (5 ms), stage="Total time" (189 ms)]
[2019-02-07 18:39:00,116][INFO ][sys-#40][GridDhtPartitionsExchangeFuture]
Exchange longest local stages [startVer=AffinityTopologyVersion [topVer=5,
minorTopVer=1], resVer=AffinityTopologyVersion [topVer=5, minorTopVer=1],
stage="Affinity change by custom message [grp=CachePutAllGetAllExample]" (5 ms)
(parent=Determine exchange type), stage="Affinity change by custom message
[grp=ignite-sys-cache]" (2 ms) (parent=Determine exchange type)]
[2019-02-07 18:39:00,118][INFO
][exchange-worker-#38][GridCachePartitionExchangeManager] Skipping rebalancing
(no affinity changes) [top=AffinityTopologyVersion [topVer=5, minorTopVer=1],
rebTopVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0],
evt=DISCOVERY_CUSTOM_EVT, evtNode=9f903121-c4d6-433f-ba62-6f864d967de9,
client=true]
[2019-02-07 18:39:00,612][ERROR][mgmt-#50][GridTaskWorker] Failed to obtain
remote job result policy for result from ComputeTask.result(..) method (will
fail the whole task): GridJobResultImpl
[job=o.a.i.i.processors.cache.distributed.GridDistributedCacheAdapter$GlobalRemoveAllJob@13006998,
sib=GridJobSiblingImpl
[sesId=f949c98c861-f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8,
jobId=1a49c98c861-f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8,
nodeId=200134a1-d732-4831-85c2-9185f65428ff, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=1a49c98c861-f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode [id=200134a1-d732-4831-85c2-9185f65428ff,
addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.4.52],
sockAddrs=[work-pc.gridgain.local/172.25.4.52:47501, /0:0:0:0:0:0:0:1:47501,
/127.0.0.1:47501], discPort=47501, order=5, intOrder=4,
lastExchangeTime=1549553938177, loc=false, ver=2.7.2#20190205-sha1:43e3211d,
isClient=false], ex=class o.a.i.compute.ComputeUserUndeclaredException: Failed
to execute job due to unexpected runtime exception
[jobId=1a49c98c861-f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=o.a.i.i.processors.cache.distributed.GridDistributedCacheAdapter$RemoveAllTask,
dep=GridDeployment [ts=1549553938287, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
clsLdrId=cae5c98c861-200134a1-d732-4831-85c2-9185f65428ff, userVer=0, loc=true,
sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
pendingUndeploy=false, undeployed=false, usage=1],
taskClsName=o.a.i.i.processors.cache.distributed.GridDistributedCacheAdapter$RemoveAllTask,
sesId=f949c98c861-f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8,
startTime=1549553940190, endTime=9223372036854775807,
taskNodeId=f5f98ea6-3a7b-4e7e-bf9a-dc731f13a1e8,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=true,
topPred=null,
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Description:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
TX, PRIMARY_SYNC, readFromBackup=false_, inserts 500 rows and executes _SELECT
COUNT(*)_
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
was:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
COUNT(*)_
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, readFromBackup=false_, inserts 500 rows and executes
> _SELECT COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11237) GetAll may return less data during server node restart
Sergey Kozlov created IGNITE-11237:
--
Summary: GetAll may return less data during server node restart
Key: IGNITE-11237
URL: https://issues.apache.org/jira/browse/IGNITE-11237
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
Attachments: CachePutAllGetAllExample.java,
ExampleNodeStartupRestart.java
0. Use ignite-examples project and Idea
1. Run {{ExampleNodeStartup}}
2. Run {{ExampleNodeStartupRestart}}
3. Run {{CachePutAllGetAllExample}}
Sometimes the received entries number less than expected:
{noformat}
[17:37:25] Ignite node started OK (id=3497ca71)
[17:37:25] Topology snapshot [ver=4, locNode=3497ca71, servers=1, clients=1,
state=ACTIVE, CPUs=8, offheap=3.2GB, heap=7.1GB]
Iteration: 10
[17:37:26] Topology snapshot [ver=5, locNode=3497ca71, servers=2, clients=1,
state=ACTIVE, CPUs=8, offheap=6.4GB, heap=11.0GB]
Iteration: 20
Iteration: 30
Iteration: 40
Iteration: 50
Iteration: 60
Iteration: 70
Iteration: 80
Iteration: 90
Iteration: 100
Iteration: 110
[17:37:31] Topology snapshot [ver=6, locNode=3497ca71, servers=1, clients=1,
state=ACTIVE, CPUs=8, offheap=3.2GB, heap=7.1GB]
[2019-02-06 17:37:31,924][ERROR][main][TcpCommunicationSpi] Failed to send
message to remote node [node=TcpDiscoveryNode
[id=75d87e82-b466-47c0-8043-d9f7b2c22a60, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.25.4.52], sockAddrs=[work-pc.gridgain.local/172.25.4.52:47501,
/0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501], discPort=47501, order=5, intOrder=4,
lastExchangeTime=1549463846635, loc=false, ver=2.7.2#20190205-sha1:43e3211d,
isClient=false], msg=GridIoMessage [plc=2, topic=TOPIC_CACHE, topicOrd=8,
ordered=false, timeout=0, skipOnTimeout=false, msg=GridNearGetRequest
[futId=584ed33c861-8714c669-3f45-45c3-ab40-622a61666c43,
miniId=784ed33c861-8714c669-3f45-45c3-ab40-622a61666c43, ver=null, keyMap=null,
flags=1, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=1],
subjId=3497ca71-1ded-4e60-9396-5a32a0340977, taskNameHash=0, createTtl=-1,
accessTtl=-1, mvccSnapshot=null]]]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
Failed to send message (node left topology): TcpDiscoveryNode
[id=75d87e82-b466-47c0-8043-d9f7b2c22a60, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.25.4.52], sockAddrs=[work-pc.gridgain.local/172.25.4.52:47501,
/0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501], discPort=47501, order=5, intOrder=4,
lastExchangeTime=1549463846635, loc=false, ver=2.7.2#20190205-sha1:43e3211d,
isClient=false]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3281)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2992)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2873)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2716)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2675)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1656)
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1731)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1245)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.map(GridPartitionedGetFuture.java:334)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.initialMap(GridPartitionedGetFuture.java:176)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.init(GridPartitionedGetFuture.java:162)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync0(GridDhtAtomicCache.java:1640)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsyncInternal(GridDhtAtomicCache.java:589)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAll0(GridDhtAtomicCache.java:498)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAll(GridCacheAdapter.java:1587)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.getAll(IgniteCacheProxyImpl.java:1130)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.getAll(GatewayProtectedCacheProxy.java:686)
at
org.apache.ignite.examples.datagrid.CachePutAllGetAllExample.putAllGetAll(CachePutAllGetAllExample.java:94)
at
org.apache.ignite.examples.datagrid.CachePutAllGetAllExample.main(CachePutAllGetAllExample.java:66)
ERROR GetAll size: 1048
Iteration: 120
[jira] [Commented] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761737#comment-16761737
]
Sergey Kozlov commented on IGNITE-11218:
Added {{readFromBackup=false}}, but the lost data is still found
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
> COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761737#comment-16761737
]
Sergey Kozlov edited comment on IGNITE-11218 at 2/6/19 1:33 PM:
Added {{readFromBackup=false}} for template, but the lost data is still found
was (Author: skozlov):
Added {{readFromBackup=false}}, but the lost data is still found
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
> COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Attachment: count.zip
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
> COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Attachment: (was: count.zip)
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
> COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Attachment: count.zip
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}}
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Component/s: persistence
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
> COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Description:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
TX, PRIMARY_SYNC, copyOnRead=false_, insert 500 rows and execute SELECT COUNT(*)
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
was:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
Tx, copyOnRead=false_, insert 500 rows and execute SELECT COUNT(*)
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, insert 500 rows and execute SELECT
> COUNT(*)
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Description:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
COUNT(*)_
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
was:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
TX, PRIMARY_SYNC, copyOnRead=false_, insert 500 rows and execute SELECT COUNT(*)
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, copyOnRead=false_, inserts 500 rows and executes _SELECT
> COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11218:
---
Description:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
Tx, copyOnRead=false_, insert 500 rows and execute SELECT COUNT(*)
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
was:
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}}
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> Tx, copyOnRead=false_, insert 500 rows and execute SELECT COUNT(*)
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11218) COUNT(*) may return wrong value with PDS
Sergey Kozlov created IGNITE-11218:
--
Summary: COUNT(*) may return wrong value with PDS
Key: IGNITE-11218
URL: https://issues.apache.org/jira/browse/IGNITE-11218
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Sergey Kozlov
Attachments: count.zip
1. Unzip attached file into {{examples}} directory
2. Open {{ignite-examples}} project in IDEA.
3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
4. Run {{SqlJdbcCountExample}}
{noformat}
[23:54:44] Ignite node started OK (id=97f4654e)
[23:54:44] >>> Ignite cluster is not active (limited functionality available).
Use control.(sh|bat) script or IgniteCluster interface to activate.
[23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
[23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
>>> Connected to server.
>>> Attempt 1
>>> ERROR! Expected 500 entries for table t1 but got 498 entries
>>> Attempt 2
>>> ERROR! Expected 500 entries for table t2 but got 476 entries
>>> Attempt 3
>>> ERROR! Expected 500 entries for table t3 but got 477 entries
>>> Attempt 4
>>> ERROR! Expected 500 entries for table t4 but got 430 entries
>>> Attempt 5
>>> Attempt 6
>>> ERROR! Expected 500 entries for table t6 but got 486 entries
>>> Attempt 7
>>> Attempt 8
>>> ERROR! Expected 500 entries for table t8 but got 463 entries
>>> Attempt 9
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11094) Add SSL support for ignite zookeeper SPI
[ https://issues.apache.org/jira/browse/IGNITE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov updated IGNITE-11094: --- Description: ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK server connections if Zookeeper SPI used. 1. https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide was:ZK 3.5.4-beta is already supporting SSL. We should add SSL support to ZK server connections if Zookeeper SPI used > Add SSL support for ignite zookeeper SPI > > > Key: IGNITE-11094 > URL: https://issues.apache.org/jira/browse/IGNITE-11094 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Priority: Major > Fix For: 2.8 > > > ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK > server connections if Zookeeper SPI used. > 1. > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11094) Add SSL support for ignite zookeeper SPI
Sergey Kozlov created IGNITE-11094: -- Summary: Add SSL support for ignite zookeeper SPI Key: IGNITE-11094 URL: https://issues.apache.org/jira/browse/IGNITE-11094 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: Sergey Kozlov Fix For: 2.8 ZK 3.5.4-beta is already supporting SSL. We should add SSL support to ZK server connections if Zookeeper SPI used -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11048) Start node with TTL caches causes failure handler activity
[
https://issues.apache.org/jira/browse/IGNITE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11048:
---
Description:
1. Start 1 node with attached config (1.xml)
2. Look at node log:
{noformat}
[17:04:51,386][INFO][main][GridCacheProcessor] Finished restoring partition
state for local groups [groupsProcessed=11, partitionsProcessed=0, time=6135ms]
[17:04:51,387][INFO][main][GridCacheDatabaseSharedManager] Partition states
information after LOGICAL RECOVERY phase:
[17:04:54,847][SEVERE][nio-acceptor-tcp-comm-#28][G] Blocked system-critical
thread has been detected. This can lead to cluster-wide undefined behaviour
[threadName=ttl-cleanup-worker, blockedFor=16s]
[17:04:54,848][WARNING][nio-acceptor-tcp-comm-#28][G] Thread
[name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0, waitCnt=1]
[17:04:54,849][SEVERE][nio-acceptor-tcp-comm-#28][] Critical system error
detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker
[name=ttl-cleanup-worker, igniteInstanceName=null, finished=false,
heartbeatTs=1548252278711]]]
class org.apache.ignite.IgniteException: GridWorker [name=ttl-cleanup-worker,
igniteInstanceName=null, finished=false, heartbeatTs=1548252278711]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1833)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1828)
at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
at
org.apache.ignite.internal.util.nio.GridNioServer$GridNioAcceptWorker.accept(GridNioServer.java:2938)
at
org.apache.ignite.internal.util.nio.GridNioServer$GridNioAcceptWorker.body(GridNioServer.java:2877)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
[17:04:54,849][WARNING][nio-acceptor-tcp-comm-#28][FailureProcessor] No
deadlocked threads detected.
[17:04:55,030][WARNING][nio-acceptor-tcp-comm-#28][FailureProcessor] Thread
dump at 2019/01/23 17:04:55 MSK
Thread [name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0,
waitCnt=1]
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
o.a.i.i.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2205)
at
o.a.i.i.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:133)
{noformat}
Note: there's no similar issues for AI 2.5
was:
1. Start 1 node with attache config
2. Look at node log:
{noformat}
[17:04:51,386][INFO][main][GridCacheProcessor] Finished restoring partition
state for local groups [groupsProcessed=11, partitionsProcessed=0, time=6135ms]
[17:04:51,387][INFO][main][GridCacheDatabaseSharedManager] Partition states
information after LOGICAL RECOVERY phase:
[17:04:54,847][SEVERE][nio-acceptor-tcp-comm-#28][G] Blocked system-critical
thread has been detected. This can lead to cluster-wide undefined behaviour
[threadName=ttl-cleanup-worker, blockedFor=16s]
[17:04:54,848][WARNING][nio-acceptor-tcp-comm-#28][G] Thread
[name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0, waitCnt=1]
[17:04:54,849][SEVERE][nio-acceptor-tcp-comm-#28][] Critical system error
detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker
[name=ttl-cleanup-worker, igniteInstanceName=null, finished=false,
heartbeatTs=1548252278711]]]
class org.apache.ignite.IgniteException: GridWorker [name=ttl-cleanup-worker,
igniteInstanceName=null, finished=false, heartbeatTs=1548252278711]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1833)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1828)
at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
at
[jira] [Created] (IGNITE-11048) Start node with TTL caches causes failure handler activity
Sergey Kozlov created IGNITE-11048:
--
Summary: Start node with TTL caches causes failure handler activity
Key: IGNITE-11048
URL: https://issues.apache.org/jira/browse/IGNITE-11048
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
Attachments: 1.xml, ignite-1cecc333.0.log
1. Start 1 node with attache config
2. Look at node log:
{noformat}
[17:04:51,386][INFO][main][GridCacheProcessor] Finished restoring partition
state for local groups [groupsProcessed=11, partitionsProcessed=0, time=6135ms]
[17:04:51,387][INFO][main][GridCacheDatabaseSharedManager] Partition states
information after LOGICAL RECOVERY phase:
[17:04:54,847][SEVERE][nio-acceptor-tcp-comm-#28][G] Blocked system-critical
thread has been detected. This can lead to cluster-wide undefined behaviour
[threadName=ttl-cleanup-worker, blockedFor=16s]
[17:04:54,848][WARNING][nio-acceptor-tcp-comm-#28][G] Thread
[name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0, waitCnt=1]
[17:04:54,849][SEVERE][nio-acceptor-tcp-comm-#28][] Critical system error
detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker
[name=ttl-cleanup-worker, igniteInstanceName=null, finished=false,
heartbeatTs=1548252278711]]]
class org.apache.ignite.IgniteException: GridWorker [name=ttl-cleanup-worker,
igniteInstanceName=null, finished=false, heartbeatTs=1548252278711]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1833)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1828)
at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
at
org.apache.ignite.internal.util.nio.GridNioServer$GridNioAcceptWorker.accept(GridNioServer.java:2938)
at
org.apache.ignite.internal.util.nio.GridNioServer$GridNioAcceptWorker.body(GridNioServer.java:2877)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
[17:04:54,849][WARNING][nio-acceptor-tcp-comm-#28][FailureProcessor] No
deadlocked threads detected.
[17:04:55,030][WARNING][nio-acceptor-tcp-comm-#28][FailureProcessor] Thread
dump at 2019/01/23 17:04:55 MSK
Thread [name="ttl-cleanup-worker-#45", id=74, state=WAITING, blockCnt=0,
waitCnt=1]
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
o.a.i.i.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2205)
at
o.a.i.i.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:133)
{noformat}
Note: there's no similar issues for AI 2.5
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10977) Document unsupported clean() call for MVCC caches
Sergey Kozlov created IGNITE-10977:
--
Summary: Document unsupported clean() call for MVCC caches
Key: IGNITE-10977
URL: https://issues.apache.org/jira/browse/IGNITE-10977
Project: Ignite
Issue Type: Task
Components: documentation
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.8
Now MVCC caches don't support {{cache.clean()}} by design. So let's document it
as a known limitations (I suppose we should have such page on readme.io)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-10892) Add support JDK 10/11 for ignite.sh(.bat)
[
https://issues.apache.org/jira/browse/IGNITE-10892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov closed IGNITE-10892.
--
Ignite Flags: (was: Docs Required)
> Add support JDK 10/11 for ignite.sh(.bat)
> -
>
> Key: IGNITE-10892
> URL: https://issues.apache.org/jira/browse/IGNITE-10892
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4, 2.5
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
>
> Start ignite.sh(.bat) shows following:
> {noformat}
> The version of JAVA installed in JAVA_HOME=/usr/lib/jvm/java-10-oracle is
> incorrect.
> Please point JAVA_HOME variable to installation of JDK 1.8 or JDK 9.
> You can also download latest JDK at http://java.com/download
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10892) Add support JDK 10/11 for ignite.sh(.bat)
[
https://issues.apache.org/jira/browse/IGNITE-10892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742038#comment-16742038
]
Sergey Kozlov commented on IGNITE-10892:
It's fixed for master so I suppose the issue can be closed
> Add support JDK 10/11 for ignite.sh(.bat)
> -
>
> Key: IGNITE-10892
> URL: https://issues.apache.org/jira/browse/IGNITE-10892
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4, 2.5
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
>
> Start ignite.sh(.bat) shows following:
> {noformat}
> The version of JAVA installed in JAVA_HOME=/usr/lib/jvm/java-10-oracle is
> incorrect.
> Please point JAVA_HOME variable to installation of JDK 1.8 or JDK 9.
> You can also download latest JDK at http://java.com/download
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10892) Add support JDK 10/11 for ignite.sh(.bat)
[
https://issues.apache.org/jira/browse/IGNITE-10892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov resolved IGNITE-10892.
Resolution: Won't Fix
> Add support JDK 10/11 for ignite.sh(.bat)
> -
>
> Key: IGNITE-10892
> URL: https://issues.apache.org/jira/browse/IGNITE-10892
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4, 2.5
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
>
> Start ignite.sh(.bat) shows following:
> {noformat}
> The version of JAVA installed in JAVA_HOME=/usr/lib/jvm/java-10-oracle is
> incorrect.
> Please point JAVA_HOME variable to installation of JDK 1.8 or JDK 9.
> You can also download latest JDK at http://java.com/download
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10892) Add support JDK 10/11 for ignite.sh(.bat)
Sergey Kozlov created IGNITE-10892:
--
Summary: Add support JDK 10/11 for ignite.sh(.bat)
Key: IGNITE-10892
URL: https://issues.apache.org/jira/browse/IGNITE-10892
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.5, 2.4
Reporter: Sergey Kozlov
Start ignite.sh(.bat) shows following:
{noformat}
The version of JAVA installed in JAVA_HOME=/usr/lib/jvm/java-10-oracle is
incorrect.
Please point JAVA_HOME variable to installation of JDK 1.8 or JDK 9.
You can also download latest JDK at http://java.com/download
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10331) Document Disk page compression
[ https://issues.apache.org/jira/browse/IGNITE-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov reassigned IGNITE-10331: -- Assignee: (was: Sergey Kozlov) > Document Disk page compression > -- > > Key: IGNITE-10331 > URL: https://issues.apache.org/jira/browse/IGNITE-10331 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Sergi Vladykin >Priority: Major > > There is an email thread titled "Disk page compression for Ignite persistent > store" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3269) Benchmark driver stops working when one of servers left grid and backupcount 0
[
https://issues.apache.org/jira/browse/IGNITE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725850#comment-16725850
]
Sergey Kozlov commented on IGNITE-3269:
---
[~agura] The lost partiton logic should be covered by the policy and on the
user side. For some test cases the lost data is an expected behavior (and data
can be restored from an external source)
> Benchmark driver stops working when one of servers left grid and backupcount 0
> --
>
> Key: IGNITE-3269
> URL: https://issues.apache.org/jira/browse/IGNITE-3269
> Project: Ignite
> Issue Type: Bug
> Components: yardstick
>Affects Versions: 1.7
>Reporter: Ksenia Rybakova
>Assignee: Oleg Ostanin
>Priority: Critical
> Attachments: failed_client_log.zip
>
>
> Test config: 4 hosts with 4 clients and 1 server each, backup count = 0.
> During the test one of the servers was killed. After that one of the clients
> stopped working:
> {noformat}
> [15:31:45,248][WARN ][sys-#27%null%][TcpCommunicationSpi] Connect timed out
> (consider increasing 'failureDetectionTimeout' configuration property)
> [addr=fosters-216/10.20.0.216:47100, failureDetectionTimeout=1]
> [15:31:45,256][WARN ][sys-#27%null%][TcpCommunicationSpi] Failed to connect
> to a remote node (make sure that destination node is alive and operating
> system firewall is disabled on local and remote hosts)
> [addrs=[fosters-216/10.20.0.216:4
> [15:31:45,276][WARN ][disco-event-worker-#52%null%][GridDiscoveryManager]
> Node FAILED: TcpDiscoveryNode [id=f5bcc4d3-aa56-4e51-8672-e799a42990a6,
> addrs=[10.20.0.216, 127.0.0.1], sockAddrs=[fosters-216/10.20.0.216:47500,
> /10.20.0.216:4750
> [15:31:45,324][INFO ][disco-event-worker-#52%null%][GridDiscoveryManager]
> Topology snapshot [ver=22, servers=3, clients=16, CPUs=64, heap=150.0GB]
> ERROR: The benchmark of random operation failed.
> Type '--help' for usage.
> Finishing main test [ts=1465252305413, date=Mon Jun 06 15:31:45 PDT 2016]
> [15:31:45] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=9c7413d2551-758034b3-0248-4d62-b901-be86d119183c, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, colocatedLocallyMa
> Type '--help' for usage.
> [15:31:45] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=6f7413d2551-758034b3-0248-4d62-b901-be86d119183c, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, colocatedLocallyMa
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:700)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:644)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:607)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:135)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:133)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> [15:31:45] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=ff7413d2551-758034b3-0248-4d62-b901-be86d119183c, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, colocatedLocallyMa
> at
>
[jira] [Resolved] (IGNITE-6205) Stability testing on CI server
[ https://issues.apache.org/jira/browse/IGNITE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov resolved IGNITE-6205. --- Resolution: Won't Fix > Stability testing on CI server > -- > > Key: IGNITE-6205 > URL: https://issues.apache.org/jira/browse/IGNITE-6205 > Project: Ignite > Issue Type: Task >Affects Versions: 2.1 >Reporter: Sergey Kozlov >Assignee: Peter Ivanov >Priority: Major > > CI server shows many sporadic failures and the communty spend significant > efforts to fix them. > We should to avoid such cases by adding the task on teamcity where new or > modified tests wil run 100 times. Once it will be done the "100 times run" > can become the part/requirement of review procedure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-6205) Stability testing on CI server
[ https://issues.apache.org/jira/browse/IGNITE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov closed IGNITE-6205. - Assignee: Sergey Kozlov (was: Peter Ivanov) > Stability testing on CI server > -- > > Key: IGNITE-6205 > URL: https://issues.apache.org/jira/browse/IGNITE-6205 > Project: Ignite > Issue Type: Task >Affects Versions: 2.1 >Reporter: Sergey Kozlov >Assignee: Sergey Kozlov >Priority: Major > > CI server shows many sporadic failures and the communty spend significant > efforts to fix them. > We should to avoid such cases by adding the task on teamcity where new or > modified tests wil run 100 times. Once it will be done the "100 times run" > can become the part/requirement of review procedure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6205) Stability testing on CI server
[ https://issues.apache.org/jira/browse/IGNITE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721063#comment-16721063 ] Sergey Kozlov commented on IGNITE-6205: --- I suppose now it makes no sense. > Stability testing on CI server > -- > > Key: IGNITE-6205 > URL: https://issues.apache.org/jira/browse/IGNITE-6205 > Project: Ignite > Issue Type: Task >Affects Versions: 2.1 >Reporter: Sergey Kozlov >Assignee: Peter Ivanov >Priority: Major > > CI server shows many sporadic failures and the communty spend significant > efforts to fix them. > We should to avoid such cases by adding the task on teamcity where new or > modified tests wil run 100 times. Once it will be done the "100 times run" > can become the part/requirement of review procedure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10678) Shell script unification
Sergey Kozlov created IGNITE-10678:
--
Summary: Shell script unification
Key: IGNITE-10678
URL: https://issues.apache.org/jira/browse/IGNITE-10678
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 3.0
Ignite distriburion package includes following scripts:
{noformat}
bin/control.sh
bin/ignite.sh
bin/ignite-rf.sh
bin/igniterouter.sh
bin/ignitevisorcmd.sh
bin/sqlline.sh
{noformat}
and same set with {{.bat}} extension
The scripts has own logic for java version detecting, set ignite home, class
path and so on. Also similar commands for different scripts designed
differently (like argument naming).
I suppose the scripts should be redesigned by following rules:
- the script code should contain one line - just call a proper java class and
pass all command-line arguments
- use common argument parser for all scripts
Optional:
- make interactive controls.sh
- deprecate ignitevisorcmd and move the commands into control.sh (also it will
allow to remove demo node mode)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10631) examples/sql/world.sql doesn't work for IgniteJdbcDriver
[
https://issues.apache.org/jira/browse/IGNITE-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10631:
---
Description:
{noformat}
['/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/art-gg-pro/bin/sqlline.sh',
'-d', 'org.apache.ignite.IgniteJdbcDriver', '--verbose=true', '--force=true',
'--showWarnings=true', '--showNestedErrs=true', '-u',
'jdbc:ignite:cfg://cache=default:transactionsAllowed=true@/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/client.xml',
'-f',
'/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/sqlline_output.1.batch.txt']
...
9/5330 CREATE TABLE City (
ID INT,
Name VARCHAR,
CountryCode CHAR(3),
District VARCHAR,
Population INT,
PRIMARY KEY (ID, CountryCode)
) WITH "template=partitioned, backups=1, affinityKey=CountryCode,
CACHE_NAME=City, KEY_TYPE=demo.model.CityKey, VALUE_TYPE=demo.model.City";
No rows affected (0.118 seconds)
10/5330
11/5330 CREATE INDEX idx_country_code ON city (CountryCode);
Error: Table doesn't exist: CITY (state=42000,code=3001)
java.sql.SQLException: Table doesn't exist: CITY
at
org.apache.ignite.internal.processors.query.IgniteSQLException.toJdbcException(IgniteSQLException.java:143)
at
org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:179)
at
org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:158)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.executeSingle(JdbcStatement.java:181)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.execute0(JdbcStatement.java:195)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.execute(JdbcStatement.java:303)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.runCommands(SqlLine.java:1706)
at sqlline.Commands.run(Commands.java:1317)
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
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.initArgs(SqlLine.java:595)
at sqlline.SqlLine.begin(SqlLine.java:643)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
> examples/sql/world.sql doesn't work for IgniteJdbcDriver
>
>
> Key: IGNITE-10631
> URL: https://issues.apache.org/jira/browse/IGNITE-10631
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
>
> {noformat}
> ['/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/art-gg-pro/bin/sqlline.sh',
> '-d', 'org.apache.ignite.IgniteJdbcDriver', '--verbose=true',
> '--force=true', '--showWarnings=true', '--showNestedErrs=true', '-u',
> 'jdbc:ignite:cfg://cache=default:transactionsAllowed=true@/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/client.xml',
> '-f',
> '/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/sqlline_output.1.batch.txt']
> ...
> 9/5330 CREATE TABLE City (
> ID INT,
> Name VARCHAR,
> CountryCode CHAR(3),
> District VARCHAR,
> Population INT,
> PRIMARY KEY (ID, CountryCode)
> ) WITH "template=partitioned, backups=1, affinityKey=CountryCode,
> CACHE_NAME=City, KEY_TYPE=demo.model.CityKey, VALUE_TYPE=demo.model.City";
> No rows affected (0.118 seconds)
> 10/5330
> 11/5330 CREATE INDEX idx_country_code ON city (CountryCode);
> Error: Table doesn't exist: CITY (state=42000,code=3001)
> java.sql.SQLException: Table doesn't exist: CITY
> at
> org.apache.ignite.internal.processors.query.IgniteSQLException.toJdbcException(IgniteSQLException.java:143)
> at
> org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:179)
> at
> org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:158)
> at
> org.apache.ignite.internal.jdbc2.JdbcStatement.executeSingle(JdbcStatement.java:181)
> at
> org.apache.ignite.internal.jdbc2.JdbcStatement.execute0(JdbcStatement.java:195)
> at
>
[jira] [Created] (IGNITE-10631) examples/sql/world.sql doesn't work for IgniteJdbcDriver
Sergey Kozlov created IGNITE-10631: -- Summary: examples/sql/world.sql doesn't work for IgniteJdbcDriver Key: IGNITE-10631 URL: https://issues.apache.org/jira/browse/IGNITE-10631 Project: Ignite Issue Type: Bug Components: examples Affects Versions: 2.7 Reporter: Sergey Kozlov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10630) Missed descriptions for ML packages
Sergey Kozlov created IGNITE-10630:
--
Summary: Missed descriptions for ML packages
Key: IGNITE-10630
URL: https://issues.apache.org/jira/browse/IGNITE-10630
Project: Ignite
Issue Type: Bug
Components: build
Affects Versions: 2.7
Reporter: Sergey Kozlov
There're two modules in JavaDoc with missed descriptions:
{noformat}
org.apache.ignite.ml.math.exceptions.preprocessing
org.apache.ignite.ml.selection.scoring.evaluator
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
[
https://issues.apache.org/jira/browse/IGNITE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714653#comment-16714653
]
Sergey Kozlov edited comment on IGNITE-10222 at 12/10/18 1:25 PM:
--
Attached file has 3 examples covering the following functionality of thin C++
client:
* putall and getall operations in {{thin-client-put-get-all-caches-example}}
* create dynamic cache, put, get in
{{thin-client-put-get-dynamic-caches-example}}
* put, get single type/different types in {{thin-client-put-get-extend-example}}
Fill free to change the code.
was (Author: skozlov):
Attached file has 3 examples covering the following functionality of thin C++
client:
* putall and getall operations in {{thin-client-put-get-all-caches-example}}
* create dynamic cache, put, get in
{{thin-client-put-get-dynamic-caches-example}}
* put, get single type/different types in {{thin-client-put-get-extend-example}}
Fill free to change the code and it doesn't fit Apache Ignite requirements.
> CPP Thin: Examples for operations with multiple keys and values
> ---
>
> Key: IGNITE-10222
> URL: https://issues.apache.org/jira/browse/IGNITE-10222
> Project: Ignite
> Issue Type: New Feature
> Components: examples, platforms, thin client
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: custom_examples.zip
>
>
> Add examples for new API calls for putall, getall, removeall
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
[
https://issues.apache.org/jira/browse/IGNITE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714653#comment-16714653
]
Sergey Kozlov edited comment on IGNITE-10222 at 12/10/18 12:26 PM:
---
Attached file has 3 examples covering the following functionality of thin C++
client:
* putall and getall operations in {{thin-client-put-get-all-caches-example}}
* create dynamic cache, put, get in
{{thin-client-put-get-dynamic-caches-example}}
* put, get single type/different types in {{thin-client-put-get-extend-example}}
Fill free to change the code and it doesn't fit Apache Ignite requirements.
was (Author: skozlov):
Attached file has 3 examples covering the following functionality of thin C++
client:
* putall and getall operations in {{thin-client-put-get-all-caches-example}}
* create dynamic cache, put, get in
{{thin-client-put-get-dynamic-caches-example}}
* put, get single type/different types in {{thin-client-put-get-extend-example}}
> CPP Thin: Examples for operations with multiple keys and values
> ---
>
> Key: IGNITE-10222
> URL: https://issues.apache.org/jira/browse/IGNITE-10222
> Project: Ignite
> Issue Type: New Feature
> Components: examples, platforms, thin client
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: custom_examples.zip
>
>
> Add examples for new API calls for putall, getall, removeall
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
[
https://issues.apache.org/jira/browse/IGNITE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714653#comment-16714653
]
Sergey Kozlov commented on IGNITE-10222:
Attached file has 3 examples covering the following functionality of thin C++
client:
* putall and getall operations in {{thin-client-put-get-all-caches-example}}
* create dynamic cache, put, get in
{{thin-client-put-get-dynamic-caches-example}}
* put, get single type/different types in {{thin-client-put-get-extend-example}}
> CPP Thin: Examples for operations with multiple keys and values
> ---
>
> Key: IGNITE-10222
> URL: https://issues.apache.org/jira/browse/IGNITE-10222
> Project: Ignite
> Issue Type: New Feature
> Components: examples, platforms, thin client
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: custom_examples.zip
>
>
> Add examples for new API calls for putall, getall, removeall
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
[ https://issues.apache.org/jira/browse/IGNITE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov updated IGNITE-10222: --- Component/s: thin client platforms > CPP Thin: Examples for operations with multiple keys and values > --- > > Key: IGNITE-10222 > URL: https://issues.apache.org/jira/browse/IGNITE-10222 > Project: Ignite > Issue Type: New Feature > Components: examples, platforms, thin client >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Priority: Major > Fix For: 2.8 > > > Add examples for new API calls for putall, getall, removeall -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
[ https://issues.apache.org/jira/browse/IGNITE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov updated IGNITE-10222: --- Attachment: custom_examples.zip > CPP Thin: Examples for operations with multiple keys and values > --- > > Key: IGNITE-10222 > URL: https://issues.apache.org/jira/browse/IGNITE-10222 > Project: Ignite > Issue Type: New Feature > Components: examples, platforms, thin client >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Priority: Major > Fix For: 2.8 > > Attachments: custom_examples.zip > > > Add examples for new API calls for putall, getall, removeall -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
[ https://issues.apache.org/jira/browse/IGNITE-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kozlov updated IGNITE-10222: --- Component/s: examples > CPP Thin: Examples for operations with multiple keys and values > --- > > Key: IGNITE-10222 > URL: https://issues.apache.org/jira/browse/IGNITE-10222 > Project: Ignite > Issue Type: New Feature > Components: examples, platforms, thin client >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Priority: Major > Fix For: 2.8 > > > Add examples for new API calls for putall, getall, removeall -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10608) SpringDataExample fails with java.lang.AbstractMethodError
[
https://issues.apache.org/jira/browse/IGNITE-10608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10608:
---
Description:
Open example project in IDEA, compile and run {{SpringDataExample}}:
{noformat}
[23:18:34] Topology snapshot [ver=1, locNode=d4e3a93b, servers=1, clients=0,
state=ACTIVE, CPUs=4, offheap=4.8GB, heap=5.3GB]
[23:18:34] Ignite node stopped OK [name=springDataNode, uptime=00:00:00.120]
Exception in thread "main"
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'personRepository': Initialization of bean failed; nested exception
is java.lang.AbstractMethodError
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:564)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:742)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at
org.apache.ignite.examples.springdata.SpringDataExample.igniteSpringDataInit(SpringDataExample.java:79)
at
org.apache.ignite.examples.springdata.SpringDataExample.main(SpringDataExample.java:52)
Caused by: java.lang.AbstractMethodError
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:99)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:302)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1537)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1284)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
... 10 more
{noformat}
was:
Open example prject in IDEA compile and run {{SpringDataExample}}:
{noformat}
[23:18:34] Topology snapshot [ver=1, locNode=d4e3a93b, servers=1, clients=0,
state=ACTIVE, CPUs=4, offheap=4.8GB, heap=5.3GB]
[23:18:34] Ignite node stopped OK [name=springDataNode, uptime=00:00:00.120]
Exception in thread "main"
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'personRepository': Initialization of bean failed; nested exception
is java.lang.AbstractMethodError
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:564)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:742)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at
org.apache.ignite.examples.springdata.SpringDataExample.igniteSpringDataInit(SpringDataExample.java:79)
at
org.apache.ignite.examples.springdata.SpringDataExample.main(SpringDataExample.java:52)
Caused by:
[jira] [Updated] (IGNITE-10608) SpringDataExample fails with java.lang.AbstractMethodError
[
https://issues.apache.org/jira/browse/IGNITE-10608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10608:
---
Ignite Flags: (was: Docs Required)
> SpringDataExample fails with java.lang.AbstractMethodError
> --
>
> Key: IGNITE-10608
> URL: https://issues.apache.org/jira/browse/IGNITE-10608
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Sergey Kozlov
>Priority: Major
>
> Open example prject in IDEA compile and run {{SpringDataExample}}:
> {noformat}
> [23:18:34] Topology snapshot [ver=1, locNode=d4e3a93b, servers=1, clients=0,
> state=ACTIVE, CPUs=4, offheap=4.8GB, heap=5.3GB]
> [23:18:34] Ignite node stopped OK [name=springDataNode, uptime=00:00:00.120]
> Exception in thread "main"
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'personRepository': Initialization of bean failed; nested exception
> is java.lang.AbstractMethodError
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:564)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:742)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
> at
> org.apache.ignite.examples.springdata.SpringDataExample.igniteSpringDataInit(SpringDataExample.java:79)
> at
> org.apache.ignite.examples.springdata.SpringDataExample.main(SpringDataExample.java:52)
> Caused by: java.lang.AbstractMethodError
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:99)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:302)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1537)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1284)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> ... 10 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10608) SpringDataExample fails with java.lang.AbstractMethodError
Sergey Kozlov created IGNITE-10608:
--
Summary: SpringDataExample fails with java.lang.AbstractMethodError
Key: IGNITE-10608
URL: https://issues.apache.org/jira/browse/IGNITE-10608
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Sergey Kozlov
Open example prject in IDEA compile and run {{SpringDataExample}}:
{noformat}
[23:18:34] Topology snapshot [ver=1, locNode=d4e3a93b, servers=1, clients=0,
state=ACTIVE, CPUs=4, offheap=4.8GB, heap=5.3GB]
[23:18:34] Ignite node stopped OK [name=springDataNode, uptime=00:00:00.120]
Exception in thread "main"
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'personRepository': Initialization of bean failed; nested exception
is java.lang.AbstractMethodError
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:564)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:742)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at
org.apache.ignite.examples.springdata.SpringDataExample.igniteSpringDataInit(SpringDataExample.java:79)
at
org.apache.ignite.examples.springdata.SpringDataExample.main(SpringDataExample.java:52)
Caused by: java.lang.AbstractMethodError
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:99)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:302)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1537)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1284)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
... 10 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10521) Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on server node
Sergey Kozlov created IGNITE-10521:
--
Summary: Creating table with datetime for PK leads to
j.l.IndexOutOfBoundsException on server node
Key: IGNITE-10521
URL: https://issues.apache.org/jira/browse/IGNITE-10521
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5, 2.7
Reporter: Sergey Kozlov
Fix For: 2.8
1. Start serve node with PDS
2. Run sqlline via thin driver
3. Execute
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE t308 ( id DATE NOT NULL, col1
INT NOT NULL, col2 VARCHAR, PRIMARY KEY (id
)) ;
Error: class org.apache.ignite.IgniteCheckedException: Failed to find value
class in the node classpath (use default mar
shaller to enable binary objects) :
SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706 (state=5,code=0)
java.sql.SQLException: class org.apache.ignite.IgniteCheckedException: Failed
to find value class in the node classpath
(use default marshaller to enable binary objects) :
SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:753)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:210)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:473)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
We do not support datetime for PK but server node stopped:
{noformat}
[14:26:32,882][INFO][exchange-worker-#43][CacheAffinitySharedManager] Updating
caches registry performed in 3 ms.
[14:26:32,963][SEVERE][exchange-worker-#43][CacheAffinitySharedManager] Failed
to initialize cache. Will try to rollback cache start routine.
[cacheName=SQL_PUBLIC_T2]
class org.apache.ignite.IgniteCheckedException: Failed to find value class in
the node classpath (use default marshaller to enable binary objects) :
SQL_PUBLIC_T2_7080b5da_4dde_4491_b596_4a085313a98d
at
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:451)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:700)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:860)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1212)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1972)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:880)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:780)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1065)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:696)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2582)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2462)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
[14:26:32,964][INFO][exchange-worker-#43][CacheAffinitySharedManager] Caches
starting performed in 82 ms.
[14:26:32,966][INFO][exchange-worker-#43][CacheAffinitySharedManager] Affinity
initialization for started caches performed in 2 ms.
[14:26:32,968][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
Finished waiting for partition release future [topVer=AffinityTopologyVersion
[topVer=4, minorTopVer=4], waitTime=0ms, futInfo=NA, mode=DISTRIBUTED]
[14:26:32,973][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
Finished waiting for partitions release latch: ClientLatch
[coordinator=TcpDiscoveryNode [id=904904a6-d889-4265-8866-dba136019718,
addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1543922782601, loc=false,
ver=2.5.3#20181026-sha1:6261c02a, isClient=false], ackSent=true,
super=CompletableLatch [id=exchange, topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=4]]]
[jira] [Updated] (IGNITE-10393) DataStreamer failed with NPE for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10393:
---
Ignite Flags: (was: Docs Required)
> DataStreamer failed with NPE for MVCC caches
>
>
> Key: IGNITE-10393
> URL: https://issues.apache.org/jira/browse/IGNITE-10393
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 2.7
>
>
> 1. Start node with configured MVCC cache and PDS
> 2. Try to load data into cache by data streamer running on client node
> {noformat}
> OUT >>> datastreamer into cache 'cache_121', key=java.lang.Long,
> value=org.apache.ignite.testtools.model.AllTypes, range=21..51
> [14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> true]][14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, true, false,
> true]][14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> true]]class org.apache.ignite.IgniteCheckedException: DataStreamer request
> failed [node=5fae5c99-716e-441a-99d5-194de6ba61a6]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:2055)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:356)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Failed to write record:
> MvccDataRecord [super=DataRecord [writeEntries=SingletonList [MvccDataEntry
> [mvccVer=null]], super=TimeStampRecord [timestamp=1542974116042]]]
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.fillBuffer(FileWriteAheadLogManager.java:2634)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:2563)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$1600(FileWriteAheadLogManager.java:2451)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:823)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3414)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEntryEx.initialValue(GridCacheEntryEx.java:766)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2265)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:400)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:60)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:90)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.putMvccVersion(TxRecordSerializer.java:66)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putMvccDataEntry(RecordDataV2Serializer.java:298)
> at
>
[jira] [Created] (IGNITE-10393) DataStreamer failed with NPE for MVCC caches
Sergey Kozlov created IGNITE-10393:
--
Summary: DataStreamer failed with NPE for MVCC caches
Key: IGNITE-10393
URL: https://issues.apache.org/jira/browse/IGNITE-10393
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start node with configured MVCC cache and PDS
2. Try to load data into cache by data streamer running on client node
{noformat}
OUT >>> datastreamer into cache 'cache_121', key=java.lang.Long,
value=org.apache.ignite.testtools.model.AllTypes, range=21..51
[14:55:16] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true, false, false, true]][14:55:16] (err) Failed
to execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true, true, false, true]][14:55:16] (err) Failed
to execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true, false, false, true]]class
org.apache.ignite.IgniteCheckedException: DataStreamer request failed
[node=5fae5c99-716e-441a-99d5-194de6ba61a6]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:2055)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:356)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Failed to write record:
MvccDataRecord [super=DataRecord [writeEntries=SingletonList [MvccDataEntry
[mvccVer=null]], super=TimeStampRecord [timestamp=1542974116042]]]
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.fillBuffer(FileWriteAheadLogManager.java:2634)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:2563)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$1600(FileWriteAheadLogManager.java:2451)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:823)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3414)
at
org.apache.ignite.internal.processors.cache.GridCacheEntryEx.initialValue(GridCacheEntryEx.java:766)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2265)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:400)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:60)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:90)
... 7 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.putMvccVersion(TxRecordSerializer.java:66)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putMvccDataEntry(RecordDataV2Serializer.java:298)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putPlainDataEntry(RecordDataV2Serializer.java:286)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.writePlainRecord(RecordDataV2Serializer.java:246)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.writeRecord(RecordDataV1Serializer.java:222)
[jira] [Created] (IGNITE-10312) Data streamer fails with CCE: o.a.i.i.util.future.GridFinishedFuture cannot be cast to o.a.i.i.p.cache.distributed.dht.GridDhtTopologyFuture
Sergey Kozlov created IGNITE-10312:
--
Summary: Data streamer fails with CCE:
o.a.i.i.util.future.GridFinishedFuture cannot be cast to
o.a.i.i.p.cache.distributed.dht.GridDhtTopologyFuture
Key: IGNITE-10312
URL: https://issues.apache.org/jira/browse/IGNITE-10312
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Sergey Kozlov
Use data streamer by client node fails:
{noformat}
[17:08:50] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=3, done=true, cancelled=false, err=class
o.a.i.IgniteCheckedException: DataStreamer request failed
[node=6423a8f7-3607-4192-bbf8-13f859e77abd], futs=[true, true, true,
true]]class org.apache.ignite.IgniteCheckedException: DataStreamer request
failed [node=6423a8f7-3607-4192-bbf8-13f859e77abd]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1894)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassCastException:
org.apache.ignite.internal.util.future.GridFinishedFuture cannot be cast to
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFuture
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2051)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
... 6 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10222) CPP Thin: Examples for operations with multiple keys and values
Sergey Kozlov created IGNITE-10222: -- Summary: CPP Thin: Examples for operations with multiple keys and values Key: IGNITE-10222 URL: https://issues.apache.org/jira/browse/IGNITE-10222 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Sergey Kozlov Fix For: 2.8 Add examples for new API calls for putall, getall, removeall -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10196) Remove kafka-clients-*-test dependency
Sergey Kozlov created IGNITE-10196: -- Summary: Remove kafka-clients-*-test dependency Key: IGNITE-10196 URL: https://issues.apache.org/jira/browse/IGNITE-10196 Project: Ignite Issue Type: Bug Components: build Affects Versions: 2.7 Reporter: Sergey Kozlov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10136) NPE in PartitionUpdateCountersMessage
[
https://issues.apache.org/jira/browse/IGNITE-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10136:
---
Fix Version/s: (was: 2.7)
2.8
> NPE in PartitionUpdateCountersMessage
> -
>
> Key: IGNITE-10136
> URL: https://issues.apache.org/jira/browse/IGNITE-10136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 2.8
>
>
> {noformat}
> [14:00:55,950][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=9d5398bc-896a-469c-8686-38e2afd517c1,
> startPtr=FileWALPointer [idx=0, fileOff=17828636, len=210609],
> checkpointLockWait=0ms, checkpointLockHoldTime=11ms,
> walCpRecordFsyncDuration=12ms, pages=636, reason='timeout']
> [14:00:56,029][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
> Checkpoint finished [cpId=9d5398bc-896a-469c-8686-38e2afd517c1, pages=636,
> markPos=FileWALPointer [idx=0, fileOff=17828636, len=210609],
> walSegmentsCleared=0, walSegmentsCovered=[], markDuration=26ms,
> pagesWrite=21ms, fsync=58ms, total=105ms]
> [14:00:56,940][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=5f46c89e-ead8-4c87-adad-72a50c26bd7c,
> startPtr=FileWALPointer [idx=0, fileOff=20005440, len=210609],
> checkpointLockWait=0ms, checkpointLockHoldTime=8ms,
> walCpRecordFsyncDuration=5ms, pages=474, reason='timeout']
> [14:00:57,003][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
> Checkpoint finished [cpId=5f46c89e-ead8-4c87-adad-72a50c26bd7c, pages=474,
> markPos=FileWALPointer [idx=0, fileOff=20005440, len=210609],
> walSegmentsCleared=0, walSegmentsCovered=[], markDuration=15ms,
> pagesWrite=10ms, fsync=53ms, total=78ms]
> [14:00:57,065][SEVERE][grid-nio-worker-tcp-comm-2-#42][GridDirectParser]
> Failed to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1,
> ordered=false, timeout=0, skipOnTimeout=false, msg=null],
> buf=java.nio.DirectByteBuffer[pos=792 lim=885 cap=32768],
> reader=RollingUpgradeMessageReader [state=StateItem
> [stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1,
> tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true,
> msg=GridCacheIdMessage [cacheId=0]GridDistributedBaseMessage
> [ver=GridCacheVersion [topVer=152301622, order=1540821647376, nodeOrder=4],
> committedVers=null, rolledbackVers=null, cnt=0,
> super=]GridDistributedTxPrepareRequest [threadId=236,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, writeVer=GridCacheVersion
> [topVer=152301622, order=1540821647377, nodeOrder=4], timeout=0, reads=null,
> writes=ArrayList [], dhtVers=null, txSize=-1, plc=2, txState=null,
> flags=last, super=]GridDhtTxPrepareRequest
> [nearNodeId=3800f476-beb1-46b0-8a39-faa51c91831d,
> futId=f794020c661-cc8749ef-caa5-4f1e-9d89-4a9beff59798, miniId=1,
> topVer=AffinityTopologyVersion [topVer=5, minorTopVer=8],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=152301622, order=1540821647374,
> nodeOrder=5], subjId=3800f476-beb1-46b0-8a39-faa51c91831d, taskNameHash=0,
> preloadKeys=null, mvccSnapshot=MvccSnapshotResponse [futId=1,
> crdVer=1540821617885, cntr=16, opCntr=1, txs=null, cleanupVer=15,
> tracking=0], skipCompletedVers=false, super=], mapIt=null, it=null,
> arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0, fieldCnt=7, readFieldCnt=0, curName=msg, typeRead=true,
> itemTypeRead=false, keyTypeRead=false, valTypeRead=false, curType=21,
> curItemType=null, curKeyType=null, curValType=null, readMsgCls=class
> o.a.i.i.managers.communication.GridIoMessage]StateItem
> [stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1,
> tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true,
> msg=PartitionUpdateCountersMessage{cacheId=-553317389, size=0, cntrs=},
> mapIt=null, it=null, arrPos=-1, keyDone=false, readSize=1, readItems=0,
> prim=0, primShift=0, uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0,
> lastFinished=true], state=0, fieldCnt=-1, readFieldCnt=0, curName=null,
> typeRead=false, itemTypeRead=false, keyTypeRead=false, valTypeRead=false,
> curType=0, curItemType=null, curKeyType=null, curValType=null,
> readMsgCls=null]StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=140703933959040, arrOff=-1, tmpArrOff=0, valReadBytes=0,
> tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1,
> keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0,
> uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0,
[jira] [Created] (IGNITE-10136) NPE in PartitionUpdateCountersMessage
Sergey Kozlov created IGNITE-10136:
--
Summary: NPE in PartitionUpdateCountersMessage
Key: IGNITE-10136
URL: https://issues.apache.org/jira/browse/IGNITE-10136
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
{noformat}
[14:00:55,950][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
Checkpoint started [checkpointId=9d5398bc-896a-469c-8686-38e2afd517c1,
startPtr=FileWALPointer [idx=0, fileOff=17828636, len=210609],
checkpointLockWait=0ms, checkpointLockHoldTime=11ms,
walCpRecordFsyncDuration=12ms, pages=636, reason='timeout']
[14:00:56,029][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
Checkpoint finished [cpId=9d5398bc-896a-469c-8686-38e2afd517c1, pages=636,
markPos=FileWALPointer [idx=0, fileOff=17828636, len=210609],
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=26ms,
pagesWrite=21ms, fsync=58ms, total=105ms]
[14:00:56,940][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
Checkpoint started [checkpointId=5f46c89e-ead8-4c87-adad-72a50c26bd7c,
startPtr=FileWALPointer [idx=0, fileOff=20005440, len=210609],
checkpointLockWait=0ms, checkpointLockHoldTime=8ms,
walCpRecordFsyncDuration=5ms, pages=474, reason='timeout']
[14:00:57,003][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager]
Checkpoint finished [cpId=5f46c89e-ead8-4c87-adad-72a50c26bd7c, pages=474,
markPos=FileWALPointer [idx=0, fileOff=20005440, len=210609],
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=15ms,
pagesWrite=10ms, fsync=53ms, total=78ms]
[14:00:57,065][SEVERE][grid-nio-worker-tcp-comm-2-#42][GridDirectParser] Failed
to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1,
ordered=false, timeout=0, skipOnTimeout=false, msg=null],
buf=java.nio.DirectByteBuffer[pos=792 lim=885 cap=32768],
reader=RollingUpgradeMessageReader [state=StateItem
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1,
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true,
msg=GridCacheIdMessage [cacheId=0]GridDistributedBaseMessage
[ver=GridCacheVersion [topVer=152301622, order=1540821647376, nodeOrder=4],
committedVers=null, rolledbackVers=null, cnt=0,
super=]GridDistributedTxPrepareRequest [threadId=236, concurrency=PESSIMISTIC,
isolation=REPEATABLE_READ, writeVer=GridCacheVersion [topVer=152301622,
order=1540821647377, nodeOrder=4], timeout=0, reads=null, writes=ArrayList [],
dhtVers=null, txSize=-1, plc=2, txState=null, flags=last,
super=]GridDhtTxPrepareRequest
[nearNodeId=3800f476-beb1-46b0-8a39-faa51c91831d,
futId=f794020c661-cc8749ef-caa5-4f1e-9d89-4a9beff59798, miniId=1,
topVer=AffinityTopologyVersion [topVer=5, minorTopVer=8],
invalidateNearEntries={}, nearWrites=null, owned=null,
nearXidVer=GridCacheVersion [topVer=152301622, order=1540821647374,
nodeOrder=5], subjId=3800f476-beb1-46b0-8a39-faa51c91831d, taskNameHash=0,
preloadKeys=null, mvccSnapshot=MvccSnapshotResponse [futId=1,
crdVer=1540821617885, cntr=16, opCntr=1, txs=null, cleanupVer=15, tracking=0],
skipCompletedVers=false, super=], mapIt=null, it=null, arrPos=-1,
keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0,
uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0, fieldCnt=7,
readFieldCnt=0, curName=msg, typeRead=true, itemTypeRead=false,
keyTypeRead=false, valTypeRead=false, curType=21, curItemType=null,
curKeyType=null, curValType=null, readMsgCls=class
o.a.i.i.managers.communication.GridIoMessage]StateItem
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1,
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true,
msg=PartitionUpdateCountersMessage{cacheId=-553317389, size=0, cntrs=},
mapIt=null, it=null, arrPos=-1, keyDone=false, readSize=1, readItems=0, prim=0,
primShift=0, uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0,
lastFinished=true], state=0, fieldCnt=-1, readFieldCnt=0, curName=null,
typeRead=false, itemTypeRead=false, keyTypeRead=false, valTypeRead=false,
curType=0, curItemType=null, curKeyType=null, curValType=null,
readMsgCls=null]StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=140703933959040, arrOff=-1, tmpArrOff=0, valReadBytes=0,
tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1,
keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0,
uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0, fieldCnt=-1,
readFieldCnt=0, curName=null, typeRead=false, itemTypeRead=false,
keyTypeRead=false, valTypeRead=false, curType=0, curItemType=null,
curKeyType=null, curValType=null, readMsgCls=null]StateItem
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1,
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=false, msg=null,
mapIt=null, it=null, arrPos=-1, keyDone=false,
[jira] [Created] (IGNITE-10064) Build examples project failed
Sergey Kozlov created IGNITE-10064:
--
Summary: Build examples project failed
Key: IGNITE-10064
URL: https://issues.apache.org/jira/browse/IGNITE-10064
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Import {{examples/pom.xml}} in IDEA and compile
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on
project ignite-examples: Compilation failure: Compilation failure:
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[25,49]
package org.apache.ignite.springdata20.repository does not exist
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[26,56]
package org.apache.ignite.springdata20.repository.config does not exist
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[27,57]
package org.apache.ignite.springdata20.repository.support does not exist
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[43,2]
cannot find symbol
[ERROR] symbol: class EnableIgniteRepositories
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[23,49]
package org.apache.ignite.springdata20.repository does not exist
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[24,56]
package org.apache.ignite.springdata20.repository.config does not exist
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[25,56]
package org.apache.ignite.springdata20.repository.config does not exist
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[34,43]
cannot find symbol
[ERROR] symbol: class IgniteRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[33,2]
cannot find symbol
[ERROR] symbol: class RepositoryConfig
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[56,6]
cannot find symbol
[ERROR] symbol: class Query
[ERROR] location: interface
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[62,13]
cannot find symbol
[ERROR] symbol: method deleteAll()
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[64,60]
cannot find symbol
[ERROR] symbol: method count()
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[101,13]
cannot find symbol
[ERROR] symbol: method
save(java.util.TreeMap)
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[103,49]
cannot find symbol
[ERROR] symbol: method count()
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[111,29]
cannot find symbol
[ERROR] symbol: method findById(long)
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR]
/C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[122,40]
cannot find symbol
[ERROR] symbol: method findAllById(java.util.ArrayList)
[ERROR] location: variable repo of type
org.apache.ignite.examples.springdata.PersonRepository
[ERROR] -> [Help 1]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10015) Sporadic JVM crash due to restart nodes
[
https://issues.apache.org/jira/browse/IGNITE-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668357#comment-16668357
]
Sergey Kozlov commented on IGNITE-10015:
Looks like the classpath is corrupted, I'll provide more details
> Sporadic JVM crash due to restart nodes
>
>
> Key: IGNITE-10015
> URL: https://issues.apache.org/jira/browse/IGNITE-10015
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 2.7
>
> Attachments: hs_err_pid9126.log
>
>
> 1. Start 4 node cluster with pre-configured TTL caches.
> 2. Some 4 node may crash:
> {noformat}
> [22:43:01,485][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_002,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_013,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_001,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_012,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_004,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_015,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_003,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,006][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_014,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=ignite-sys-cache,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_011,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_010,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_009,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_006,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_005,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_016,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_008,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_007,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,012][INFO][db-checkpoint-thread-#68][GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=214d43f2-6096-4b42-ab0f-52b7f98078f4,
> startPtr=FileWALPointer [idx=0, fileOff=513096, len=16483],
> checkpointLockWait=0ms, checkpointLockHoldTime=23ms,
> walCpRecordFsyncDuration=880ms, pages=238, reason='timeout']
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0x7) at pc=0x7f0aa29d8522, pid=12344, tid=0x7f08b15f5700
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build
> 1.8.0_161-b12)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [libzip.so+0x12522] newEntry+0x62
> #
> # Core dump written. Default location:
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/core or core.12344
> #
> # An error report file with more information is saved as:
> #
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/hs_err_pid12344.log
> Compiled method (nm)7845 558 n 0
> java.util.zip.ZipFile::getEntry (native)
> total in heap [0x7f0a8d3d1850,0x7f0a8d3d1bc0] = 880
> relocation [0x7f0a8d3d1978,0x7f0a8d3d19c0] = 72
> main code [0x7f0a8d3d19c0,0x7f0a8d3d1bc0] = 512
> [thread 139675315439360 also had an error]
> #
> # If you would like to submit a bug report, please
[jira] [Assigned] (IGNITE-10015) Sporadic JVM crash due to restart nodes
[
https://issues.apache.org/jira/browse/IGNITE-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov reassigned IGNITE-10015:
--
Assignee: Sergey Kozlov (was: Alexey Goncharuk)
> Sporadic JVM crash due to restart nodes
>
>
> Key: IGNITE-10015
> URL: https://issues.apache.org/jira/browse/IGNITE-10015
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 2.7
>
> Attachments: hs_err_pid9126.log
>
>
> 1. Start 4 node cluster with pre-configured TTL caches.
> 2. Some 4 node may crash:
> {noformat}
> [22:43:01,485][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_002,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_013,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_001,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_012,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_004,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_015,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_003,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,006][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_014,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=ignite-sys-cache,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_011,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_010,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_009,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_006,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_005,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_016,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_008,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_007,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,012][INFO][db-checkpoint-thread-#68][GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=214d43f2-6096-4b42-ab0f-52b7f98078f4,
> startPtr=FileWALPointer [idx=0, fileOff=513096, len=16483],
> checkpointLockWait=0ms, checkpointLockHoldTime=23ms,
> walCpRecordFsyncDuration=880ms, pages=238, reason='timeout']
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0x7) at pc=0x7f0aa29d8522, pid=12344, tid=0x7f08b15f5700
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build
> 1.8.0_161-b12)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [libzip.so+0x12522] newEntry+0x62
> #
> # Core dump written. Default location:
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/core or core.12344
> #
> # An error report file with more information is saved as:
> #
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/hs_err_pid12344.log
> Compiled method (nm)7845 558 n 0
> java.util.zip.ZipFile::getEntry (native)
> total in heap [0x7f0a8d3d1850,0x7f0a8d3d1bc0] = 880
> relocation [0x7f0a8d3d1978,0x7f0a8d3d19c0] = 72
> main code [0x7f0a8d3d19c0,0x7f0a8d3d1bc0] = 512
> [thread 139675315439360 also had an error]
> #
> # If you would like to submit a bug report, please visit:
> #
[jira] [Updated] (IGNITE-10056) Attempt to create MVCC cache with TTL causes full cluster halt
[
https://issues.apache.org/jira/browse/IGNITE-10056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10056:
---
Summary: Attempt to create MVCC cache with TTL causes full cluster halt
(was: Attemp to create MVCC cache with TTL causes full cluster halt)
> Attempt to create MVCC cache with TTL causes full cluster halt
> --
>
> Key: IGNITE-10056
> URL: https://issues.apache.org/jira/browse/IGNITE-10056
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
> Environment:
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.7
>
>
> 1. Start cluster with cache template and activate:
> {code:xml}
>
>
> value="TRANSACTIONAL_SNAPSHOT"/>
>
>
>
>
>
>factory-method="factoryOf">
>
>
>
>
>
>
>
>
>
> {code}
> 2. Try to create cache via {{sqlline}}
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t1(a int, b varchar, primary
> key(a)) with "template=tmpl";
> Error: class org.apache.ignite.IgniteCheckedException: Grid configuration
> parameter invalid: expiry policy cannot be used with TRANSACTIONAL_SNAPSHOT
> atomicity mode (state=5,code=1)
> java.sql.SQLException: class org.apache.ignite.IgniteCheckedException: Grid
> configuration parameter invalid: expiry policy cannot be used with
> TRANSACTIONAL_SNAPSHOT atomicity mode
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
> That's fine but all nodes stopped by failure handler:
> {noformat}
> [21:40:03,657][SEVERE][exchange-worker-#43][CacheAffinitySharedManager]
> Failed to initialize cache. Will try to rollback cache start routine.
> [cacheName=SQL_PUBLIC_T1]
> class org.apache.ignite.IgniteCheckedException: Grid configuration parameter
> invalid: expiry policy cannot be used with TRANSACTIONAL_SNAPSHOT atomicity
> mode
> at
> org.apache.ignite.internal.processors.GridProcessorAdapter.assertParameter(GridProcessorAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validate(GridCacheProcessor.java:521)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1560)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2146)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:898)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1231)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:738)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> [21:40:03,660][INFO][exchange-worker-#43][GridCacheProcessor] Can not finish
> proxy initialization because proxy does not exist, cacheName=SQL_PUBLIC_T1,
> localNodeId=0c6a653d-b151-46b5-bd0c-7fea4b94ca26
> [21:40:03,662][INFO][exchange-worker-#43][CacheAffinitySharedManager] Caches
> starting performed in 66 ms.
> [21:40:03,667][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Affinity initialization for started caches performed in
[jira] [Created] (IGNITE-10056) Attemp to create MVCC cache with TTL causes full cluster halt
Sergey Kozlov created IGNITE-10056:
--
Summary: Attemp to create MVCC cache with TTL causes full cluster
halt
Key: IGNITE-10056
URL: https://issues.apache.org/jira/browse/IGNITE-10056
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Environment:
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start cluster with cache template and activate:
{code=xml}
{code}
2. Try to create cache via {{sqlline}}
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t1(a int, b varchar, primary
key(a)) with "template=tmpl";
Error: class org.apache.ignite.IgniteCheckedException: Grid configuration
parameter invalid: expiry policy cannot be used with TRANSACTIONAL_SNAPSHOT
atomicity mode (state=5,code=1)
java.sql.SQLException: class org.apache.ignite.IgniteCheckedException: Grid
configuration parameter invalid: expiry policy cannot be used with
TRANSACTIONAL_SNAPSHOT atomicity mode
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
That's fine but all nodes stopped by failure handler:
{noformat}
[21:40:03,657][SEVERE][exchange-worker-#43][CacheAffinitySharedManager] Failed
to initialize cache. Will try to rollback cache start routine.
[cacheName=SQL_PUBLIC_T1]
class org.apache.ignite.IgniteCheckedException: Grid configuration parameter
invalid: expiry policy cannot be used with TRANSACTIONAL_SNAPSHOT atomicity mode
at
org.apache.ignite.internal.processors.GridProcessorAdapter.assertParameter(GridProcessorAdapter.java:140)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.validate(GridCacheProcessor.java:521)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1560)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2146)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:898)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:798)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1231)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:738)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
[21:40:03,660][INFO][exchange-worker-#43][GridCacheProcessor] Can not finish
proxy initialization because proxy does not exist, cacheName=SQL_PUBLIC_T1,
localNodeId=0c6a653d-b151-46b5-bd0c-7fea4b94ca26
[21:40:03,662][INFO][exchange-worker-#43][CacheAffinitySharedManager] Caches
starting performed in 66 ms.
[21:40:03,667][INFO][exchange-worker-#43][CacheAffinitySharedManager] Affinity
initialization for started caches performed in 5 ms.
[21:40:03,673][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
Finished waiting for partition release future [topVer=AffinityTopologyVersion
[topVer=2, minorTopVer=2], waitTime=0ms, futInfo=NA, mode=DISTRIBUTED]
[21:40:03,695][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
Finished waiting for partitions release latch: ClientLatch
[coordinator=TcpDiscoveryNode [id=8a320d9a-c057-45e5-958a-6fff470c8485,
addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500],
discPort=47500, order=1, intOrder=1,
[jira] [Updated] (IGNITE-10054) sqlline hangs with concurrent operations
[
https://issues.apache.org/jira/browse/IGNITE-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10054:
---
Attachment: ignite-c9ddebdb.0.log
ignite-24507fea.0.log
16696.txt
15828.txt
> sqlline hangs with concurrent operations
>
>
> Key: IGNITE-10054
> URL: https://issues.apache.org/jira/browse/IGNITE-10054
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.7
>
> Attachments: 15828.txt, 16696.txt, ignite-24507fea.0.log,
> ignite-c9ddebdb.0.log
>
>
> 1. Start 2 nodes cluster with PDS (wal_mode=FSYNC), activate
> 2. Start 1st {{bin/sqlline}} with following commands (in batch file):
> {noformat}
> create table t1 (a int, b int, primary key(a)) with
> "atomicity=TRANSACTIONAL_SNAPSHOT,backups=1";
> insert into t1 values (1,1);
> insert into t1 values (2,1);
> insert into t1 values (3,1);
> insert into t1 values (4,1);
> insert into t1 values (5,1);
> insert into t1 values (6,1);
> insert into t1 values (7,1);
> insert into t1 values (8,1);
> insert into t1 values (9,1);
> insert into t1 values (10,1);
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> ...repeat TX many times...
> {noformat}
> 3. Start 2nd {{bin/sqlline}} with following commands (in batch file):
> {noformat}
> begin;
> update t1 set b=b-1;
> commit;
> begin;
> update t1 set b=b-1;
> commit;
> begin;
> update t1 set b=b-1;
> commit;
> ...repeat TX many times...
> {noformat}
> 4. After some time both {{sqlline}} hang:
> {noformat}
> 611/113163 commit;
> Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
> transaction because it has been rolled back [t
> imeout=0,
> tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
> xidVersion=GridCacheVersion [topVer=1
> 52310006, order=154082519, nodeOrder=1], concurrency=PESSIMISTIC,
> isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
> invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
> label=null]]]
> (state=5,code=1)
> java.sql.SQLException: Failed to execute DDL statement [stmt=commit,
> err=Failed to finish transaction because it has bee
> n rolled back [timeout=0,
> tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
> xidVersion=GridCacheV
> ersion [topVer=152310006, order=154082519, nodeOrder=1],
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=M
> ARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11
> , label=null]]]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.runCommands(SqlLine.java:1706)
> at sqlline.Commands.run(Commands.java:1317)
> 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
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:595)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 612/113163 begin;
> No rows affected (0 seconds)
> 613/113163 update t1 set b=b+1;
> {noformat}
> {noformat}
> Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
> transaction because it has been rolled back [t
> imeout=0,
> tx=GridNearTxLocal[xid=191ff90c661--0914-10f6--0001,
> xidVersion=GridCacheVersion [topVer=1
> 52310006, order=154082505, nodeOrder=1], concurrency=PESSIMISTIC,
> isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
> invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
> label=null]]]
> (state=5,code=1)
> java.sql.SQLException: Failed to execute DDL
[jira] [Created] (IGNITE-10054) sqlline hangs with concurrent operations
Sergey Kozlov created IGNITE-10054:
--
Summary: sqlline hangs with concurrent operations
Key: IGNITE-10054
URL: https://issues.apache.org/jira/browse/IGNITE-10054
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start 2 nodes cluster with PDS (wal_mode=FSYNC), activate
2. Start 1st {{bin/sqlline}} with following commands (in batch file):
{noformat}
create table t1 (a int, b int, primary key(a)) with
"atomicity=TRANSACTIONAL_SNAPSHOT,backups=1";
insert into t1 values (1,1);
insert into t1 values (2,1);
insert into t1 values (3,1);
insert into t1 values (4,1);
insert into t1 values (5,1);
insert into t1 values (6,1);
insert into t1 values (7,1);
insert into t1 values (8,1);
insert into t1 values (9,1);
insert into t1 values (10,1);
begin;
update t1 set b=b+1;
commit;
begin;
update t1 set b=b+1;
commit;
begin;
update t1 set b=b+1;
commit;
begin;
update t1 set b=b+1;
commit;
...repeat TX many times...
{noformat}
3. Start 2nd {{bin/sqlline}} with following commands (in batch file):
{noformat}
begin;
update t1 set b=b-1;
commit;
begin;
update t1 set b=b-1;
commit;
begin;
update t1 set b=b-1;
commit;
...repeat TX many times...
{noformat}
4. After some time both {{sqlline}} hang:
{noformat}
611/113163 commit;
Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
transaction because it has been rolled back [t
imeout=0,
tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
xidVersion=GridCacheVersion [topVer=1
52310006, order=154082519, nodeOrder=1], concurrency=PESSIMISTIC,
isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
invalidate=false, rollbackOnly=true,
nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
label=null]]]
(state=5,code=1)
java.sql.SQLException: Failed to execute DDL statement [stmt=commit, err=Failed
to finish transaction because it has bee
n rolled back [timeout=0,
tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
xidVersion=GridCacheV
ersion [topVer=152310006, order=154082519, nodeOrder=1],
concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=M
ARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11
, label=null]]]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.runCommands(SqlLine.java:1706)
at sqlline.Commands.run(Commands.java:1317)
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
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.initArgs(SqlLine.java:595)
at sqlline.SqlLine.begin(SqlLine.java:643)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
612/113163 begin;
No rows affected (0 seconds)
613/113163 update t1 set b=b+1;
{noformat}
{noformat}
Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
transaction because it has been rolled back [t
imeout=0,
tx=GridNearTxLocal[xid=191ff90c661--0914-10f6--0001,
xidVersion=GridCacheVersion [topVer=1
52310006, order=154082505, nodeOrder=1], concurrency=PESSIMISTIC,
isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
invalidate=false, rollbackOnly=true,
nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
label=null]]]
(state=5,code=1)
java.sql.SQLException: Failed to execute DDL statement [stmt=commit, err=Failed
to finish transaction because it has bee
n rolled back [timeout=0,
tx=GridNearTxLocal[xid=191ff90c661--0914-10f6--0001,
xidVersion=GridCacheV
ersion [topVer=152310006, order=154082505, nodeOrder=1],
concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=M
ARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11
, label=null]]]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
[jira] [Updated] (IGNITE-10052) Restart node during TX causes vacuum error
[
https://issues.apache.org/jira/browse/IGNITE-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10052:
---
Description:
1. Start 2 nodes with PDS, activate , start {{sqlline}}
2. Create table
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t1 (a int, b int, primary
key(a)) with "atomicity=TRANSACTIONAL_SNAPSHOT,
backups=1";
No rows affected (0,294 seconds)
{noformat}
3. Open TX:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0,007 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
1 row affected (0,112 seconds)
{noformat}
4. Stop and then start 2nd node
5. Rollback TX and check the table data (no rows added):
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> rollback;
No rows affected (0,011 seconds)
0: jdbc:ignite:thin://127.0.0.1/> select * from t1;
+++
| A| B|
+++
+++
No rows selected (0,067 seconds)
{noformat}
6. Start second TX that throws the exception:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0,001 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
Error: Failed to run update. Runtime failure on bounds: [lower=MvccMaxSearchRow
[], upper=MvccMinSearchRow []] (state=50
000,code=1)
java.sql.SQLException: Failed to run update. Runtime failure on bounds:
[lower=MvccMaxSearchRow [], upper=MvccMinSearchR
ow []]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/>
{noformat}
The server nodes print out:
{noformat}
[18:46:32,136][SEVERE][jdbc-request-handler-worker-#62][DmlStatementsProcessor]
Error during update [localNodeId=319a2fda-1315-4bdf-8647-7ddee2d3342e]
class org.apache.ignite.IgniteCheckedException: Runtime failure on bounds:
[lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1919)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:1840)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:530)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1104)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:460)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:368)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxQueryResultsEnlistRequest(GridDhtTransactionalCacheAdapter.java:2000)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$700(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12.apply(GridDhtTransactionalCacheAdapter.java:215)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12.apply(GridDhtTransactionalCacheAdapter.java:213)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
at
[jira] [Created] (IGNITE-10052) Restart node during TX causes vacuum error
Sergey Kozlov created IGNITE-10052:
--
Summary: Restart node during TX causes vacuum error
Key: IGNITE-10052
URL: https://issues.apache.org/jira/browse/IGNITE-10052
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start 2 nodes with PDS, activate , start {{sqlline}}
2. Create table
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t1 (a int, b int, primary
key(a)) with "atomicity=TRANSACTIONAL_SNAPSHOT,
backups=1";
No rows affected (0,294 seconds)
{noformat}
3. Open TX:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0,007 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
1 row affected (0,112 seconds)
{noformat}
4. Stop and then start 2nd node
5. Rollback TX and check the table data (no rows added):
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> rollback;
No rows affected (0,011 seconds)
0: jdbc:ignite:thin://127.0.0.1/> select * from t1;
+++
| A| B|
+++
+++
No rows selected (0,067 seconds)
{noformat}
6. Start second TX that throws the excpetion:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0,001 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
Error: Failed to run update. Runtime failure on bounds: [lower=MvccMaxSearchRow
[], upper=MvccMinSearchRow []] (state=50
000,code=1)
java.sql.SQLException: Failed to run update. Runtime failure on bounds:
[lower=MvccMaxSearchRow [], upper=MvccMinSearchR
ow []]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/>
{noformat}
The server nodes print out:
{noformat}
[18:46:32,136][SEVERE][jdbc-request-handler-worker-#62][DmlStatementsProcessor]
Error during update [localNodeId=319a2fda-1315-4bdf-8647-7ddee2d3342e]
class org.apache.ignite.IgniteCheckedException: Runtime failure on bounds:
[lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1919)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:1840)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:530)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1104)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:460)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:368)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxQueryResultsEnlistRequest(GridDhtTransactionalCacheAdapter.java:2000)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$700(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12.apply(GridDhtTransactionalCacheAdapter.java:215)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12.apply(GridDhtTransactionalCacheAdapter.java:213)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
at
[jira] [Created] (IGNITE-10039) Small data region may lead IgniteOOM
Sergey Kozlov created IGNITE-10039:
--
Summary: Small data region may lead IgniteOOM
Key: IGNITE-10039
URL: https://issues.apache.org/jira/browse/IGNITE-10039
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
For small data region(s) the node restart may lead IgniteOOM. We should
calculate the minimal required size and show a warning message on node output.
{noformat}
[21:36:06,648][SEVERE][exchange-worker-#63][] Critical system error detected.
Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR,
err=class o.a.i.i.mem.IgniteOutOfMemoryException: Failed to find a page for
eviction [segmentCapacity=3952, loaded=1549, maxDirtyPages=1162,
dirtyPages=1549, cpPages=0, pinnedInSegment=0, failedToPrepare=1549]
Out of memory in data region [name=default, initSize=50.0 MiB, maxSize=100.0
MiB, persistenceEnabled=true] Try the following:
^-- Increase maximum off-heap memory size (DataRegionConfiguration.maxSize)
^-- Enable Ignite persistence (DataRegionConfiguration.persistenceEnabled)
^-- Enable eviction or expiration policies]]
class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find
a page for eviction [segmentCapacity=3952, loaded=1549, maxDirtyPages=1162,
dirtyPages=1549, cpPages=0, pinnedInSegment=0, failedToPrepare=1549]
Out of memory in data region [name=default, initSize=50.0 MiB, maxSize=100.0
MiB, persistenceEnabled=true] Try the following:
^-- Increase maximum off-heap memory size (DataRegionConfiguration.maxSize)
^-- Enable Ignite persistence (DataRegionConfiguration.persistenceEnabled)
^-- Enable eviction or expiration policies
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:2361)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.removePageForReplacement(PageMemoryImpl.java:2255)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$900(PageMemoryImpl.java:1864)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:696)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:637)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:144)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:169)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.(AbstractFreeList.java:371)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.CacheFreeListImpl.(CacheFreeListImpl.java:49)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.(GridCacheOffheapManager.java:1339)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:1339)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:1631)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:991)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.(GridDhtLocalPartition.java:224)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.forceCreatePartition(GridDhtPartitionTopologyImpl.java:884)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2444)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2382)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1624)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1298)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1453)
at
[jira] [Created] (IGNITE-10036) node_startup_by_ssh.sample.ini move to /config
Sergey Kozlov created IGNITE-10036:
--
Summary: node_startup_by_ssh.sample.ini move to /config
Key: IGNITE-10036
URL: https://issues.apache.org/jira/browse/IGNITE-10036
Project: Ignite
Issue Type: Bug
Components: build
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
The configuration file for IGNITE-1023 has been added to location
{{bin/include/visorcmd/node_startup_by_ssh.sample.ini}}.
But the more convinient directory is {{/config}} where already collected a few
various confuration files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10004) Parse error leads to leave the transaction
[
https://issues.apache.org/jira/browse/IGNITE-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10004:
---
Description:
1. Start 2 nodes + connect sqlline
2. Execute following queries:
{noformat}
create table t10 (a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
begin;
insert into t10 values(1); <- wrong set
insert into t10 values(2, '2'); <- correct set
commit;
{noformat}
The output:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
SHOT,backups=1";
No rows affected (0,032 seconds)
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Неверное количество столбцов
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
Error: Transaction is already completed. (state=25000,code=5004)
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
was:
1. Start 2 nodes + connect sqlline
2. Execute following queries:
{noformat}
create table t10 (a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
begin;
insert into t10 values(1); <- worng set
insert into t10 values(2, '2'); <- coorect set
commit;
{noformat}
The output:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
SHOT,backups=1";
No rows affected (0,032 seconds)
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Неверное количество столбцов
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
Error: Transaction is already completed. (state=25000,code=5004)
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at
[jira] [Commented] (IGNITE-10007) Deactivation hangs if an open transaction exists
[
https://issues.apache.org/jira/browse/IGNITE-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665158#comment-16665158
]
Sergey Kozlov commented on IGNITE-10007:
More details:
The issue is reproduced for one node as well.
LRT is still presented if sqlline is running (even commit has been executed)
> Deactivation hangs if an open transaction exists
>
>
> Key: IGNITE-10007
> URL: https://issues.apache.org/jira/browse/IGNITE-10007
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Major
> Fix For: 2.7
>
> Attachments:
> PersistenceDeactivationWIthActiveMvccTransactionSelfTest.java,
> stacktrace_18308.txt, stacktrace_7808.txt
>
>
> 1. Start 2 node with PDS
> 2. Activate cluster
> 3. Connect sqlline
> 4. Create table {{create table t1(a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";}}
> 3.Start TX and execute a DML commnd:
> {noformat}
> begin;
> insert into t1 values (1, '1');
> {noformat}
> 4. Try deactivate cluster {{bin/control.bat --deactivate}}. The scripts
> doesn't return control.
> 5. Show LRT:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=352, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
> 6. Complete TX:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> commit;
> Error: class org.apache.ignite.IgniteException: Can not perform the operation
> because the cluster is inactive. Note, tha
> t the cluster is considered inactive by default if Ignite Persistent Store is
> used to let all the nodes join the cluster
> . To activate the cluster call Ignite.active(true). (state=5,code=1)
> java.sql.SQLException: class org.apache.ignite.IgniteException: Can not
> perform the operation because the cluster is ina
> ctive. Note, that the cluster is considered inactive by default if Ignite
> Persistent Store is used to let all the nodes
> join the cluster. To activate the cluster call Ignite.active(true).
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/>
> {noformat}
> It.s ok but LRT is still presented and deactivation script doesn't return
> control back to user:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=510, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10007) Deactivation hangs if an open transaction exists
[
https://issues.apache.org/jira/browse/IGNITE-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10007:
---
Attachment: stacktrace_18308.txt
stacktrace_7808.txt
> Deactivation hangs if an open transaction exists
>
>
> Key: IGNITE-10007
> URL: https://issues.apache.org/jira/browse/IGNITE-10007
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Major
> Fix For: 2.7
>
> Attachments:
> PersistenceDeactivationWIthActiveMvccTransactionSelfTest.java,
> stacktrace_18308.txt, stacktrace_7808.txt
>
>
> 1. Start 2 node with PDS
> 2. Activate cluster
> 3. Connect sqlline
> 4. Create table {{create table t1(a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";}}
> 3.Start TX and execute a DML commnd:
> {noformat}
> begin;
> insert into t1 values (1, '1');
> {noformat}
> 4. Try deactivate cluster {{bin/control.bat --deactivate}}. The scripts
> doesn't return control.
> 5. Show LRT:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=352, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
> 6. Complete TX:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> commit;
> Error: class org.apache.ignite.IgniteException: Can not perform the operation
> because the cluster is inactive. Note, tha
> t the cluster is considered inactive by default if Ignite Persistent Store is
> used to let all the nodes join the cluster
> . To activate the cluster call Ignite.active(true). (state=5,code=1)
> java.sql.SQLException: class org.apache.ignite.IgniteException: Can not
> perform the operation because the cluster is ina
> ctive. Note, that the cluster is considered inactive by default if Ignite
> Persistent Store is used to let all the nodes
> join the cluster. To activate the cluster call Ignite.active(true).
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/>
> {noformat}
> It.s ok but LRT is still presented and deactivation script doesn't return
> control back to user:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=510, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10015) Sporadic JVM crash due to restart nodes
[
https://issues.apache.org/jira/browse/IGNITE-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10015:
---
Attachment: hs_err_pid9126.log
> Sporadic JVM crash due to restart nodes
>
>
> Key: IGNITE-10015
> URL: https://issues.apache.org/jira/browse/IGNITE-10015
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
> Attachments: hs_err_pid9126.log
>
>
> 1. Start 4 node cluster with pre-configured TTL caches.
> 2. Some 4 node may crash:
> {noformat}
> [22:43:01,485][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_002,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_013,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_001,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_012,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_004,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_015,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_003,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,006][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_014,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=ignite-sys-cache,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_011,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_010,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_009,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_006,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_005,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_016,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_008,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_007,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,012][INFO][db-checkpoint-thread-#68][GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=214d43f2-6096-4b42-ab0f-52b7f98078f4,
> startPtr=FileWALPointer [idx=0, fileOff=513096, len=16483],
> checkpointLockWait=0ms, checkpointLockHoldTime=23ms,
> walCpRecordFsyncDuration=880ms, pages=238, reason='timeout']
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0x7) at pc=0x7f0aa29d8522, pid=12344, tid=0x7f08b15f5700
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build
> 1.8.0_161-b12)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [libzip.so+0x12522] newEntry+0x62
> #
> # Core dump written. Default location:
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/core or core.12344
> #
> # An error report file with more information is saved as:
> #
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/hs_err_pid12344.log
> Compiled method (nm)7845 558 n 0
> java.util.zip.ZipFile::getEntry (native)
> total in heap [0x7f0a8d3d1850,0x7f0a8d3d1bc0] = 880
> relocation [0x7f0a8d3d1978,0x7f0a8d3d19c0] = 72
> main code [0x7f0a8d3d19c0,0x7f0a8d3d1bc0] = 512
> [thread 139675315439360 also had an error]
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash
[jira] [Updated] (IGNITE-10015) Sporadic JVM crash due to restart nodes
[
https://issues.apache.org/jira/browse/IGNITE-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10015:
---
Summary: Sporadic JVM crash due to restart nodes (was: Sprodic JVM crash
due to restart nodes)
> Sporadic JVM crash due to restart nodes
>
>
> Key: IGNITE-10015
> URL: https://issues.apache.org/jira/browse/IGNITE-10015
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.7
>
>
> 1. Start 4 node cluster with pre-configured TTL caches.
> 2. Some 4 node may crash:
> {noformat}
> [22:43:01,485][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_002,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_013,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_001,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_012,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_004,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_015,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_003,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,006][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_014,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=ignite-sys-cache,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_011,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_010,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_009,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_006,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_005,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_016,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_008,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy
> initialization, cacheName=cache_007,
> localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
> [22:43:02,012][INFO][db-checkpoint-thread-#68][GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=214d43f2-6096-4b42-ab0f-52b7f98078f4,
> startPtr=FileWALPointer [idx=0, fileOff=513096, len=16483],
> checkpointLockWait=0ms, checkpointLockHoldTime=23ms,
> walCpRecordFsyncDuration=880ms, pages=238, reason='timeout']
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0x7) at pc=0x7f0aa29d8522, pid=12344, tid=0x7f08b15f5700
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build
> 1.8.0_161-b12)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [libzip.so+0x12522] newEntry+0x62
> #
> # Core dump written. Default location:
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/core or core.12344
> #
> # An error report file with more information is saved as:
> #
> /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/hs_err_pid12344.log
> Compiled method (nm)7845 558 n 0
> java.util.zip.ZipFile::getEntry (native)
> total in heap [0x7f0a8d3d1850,0x7f0a8d3d1bc0] = 880
> relocation [0x7f0a8d3d1978,0x7f0a8d3d19c0] = 72
> main code [0x7f0a8d3d19c0,0x7f0a8d3d1bc0] = 512
> [thread 139675315439360 also had an error]
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened
[jira] [Created] (IGNITE-10015) Sprodic JVM crash due to restart nodes
Sergey Kozlov created IGNITE-10015:
--
Summary: Sprodic JVM crash due to restart nodes
Key: IGNITE-10015
URL: https://issues.apache.org/jira/browse/IGNITE-10015
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start 4 node cluster with pre-configured TTL caches.
2. Some 4 node may crash:
{noformat}
[22:43:01,485][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_002, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_013, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_001, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_012, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_004, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_015, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,005][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_003, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,006][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_014, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=ignite-sys-cache, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_011, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,007][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_010, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_009, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_006, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_005, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_016, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_008, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,008][INFO][sys-#73][GridCacheProcessor] Finish proxy initialization,
cacheName=cache_007, localNodeId=e8ad11f2-c6dd-4683-b449-44a726d715fd
[22:43:02,012][INFO][db-checkpoint-thread-#68][GridCacheDatabaseSharedManager]
Checkpoint started [checkpointId=214d43f2-6096-4b42-ab0f-52b7f98078f4,
startPtr=FileWALPointer [idx=0, fileOff=513096, len=16483],
checkpointLockWait=0ms, checkpointLockHoldTime=23ms,
walCpRecordFsyncDuration=880ms, pages=238, reason='timeout']
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x7f0aa29d8522, pid=12344, tid=0x7f08b15f5700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build
1.8.0_161-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C [libzip.so+0x12522] newEntry+0x62
#
# Core dump written. Default location:
/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/core or core.12344
#
# An error report file with more information is saved as:
# /var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/suites/hs_err_pid12344.log
Compiled method (nm)7845 558 n 0 java.util.zip.ZipFile::getEntry
(native)
total in heap [0x7f0a8d3d1850,0x7f0a8d3d1bc0] = 880
relocation [0x7f0a8d3d1978,0x7f0a8d3d19c0] = 72
main code [0x7f0a8d3d19c0,0x7f0a8d3d1bc0] = 512
[thread 139675315439360 also had an error]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-cache/gg-pro-fab/bin/ignite.sh:
line 200: 12344 Aborted (core dumped) "$JAVA" ${JVM_OPTS}
${QUIET} "${RESTART_SUCCESS_OPT}" ${JMX_MON} -DIGNITE_HOME="${IGNITE_HOME}"
-DIGNITE_PROG_NAME="$0" ${JVM_XOPTS} -cp "${CP}" ${MAIN_CLASS} "${CONFIG}"
{noformat}
or
{noformat}
[jira] [Created] (IGNITE-10013) Node restart may lead to NPE in GridDhtPartitionsExchangeFuture
Sergey Kozlov created IGNITE-10013:
--
Summary: Node restart may lead to NPE in
GridDhtPartitionsExchangeFuture
Key: IGNITE-10013
URL: https://issues.apache.org/jira/browse/IGNITE-10013
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start 4 nodes with ~100 caches, create a few dynamic caches
2. Load data (~500 entries per cache)
3. Restart every node starting from first
The first node may throw NPE:
{noformat}
[20:00:18,355][INFO][exchange-worker-#63][time] Started exchange init
[topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
mvccCrd=MvccCoordinator [nodeId=c7a332ee-ee85-4604-aa93-919f15e34e36,
crdVer=1540497597005, topVer=AffinityTopologyVersion [topVer=1,
minorTopVer=0]], mvccCrdChange=false, crd=true, evt=NODE_JOINED,
evtNode=cc8ed618-2f14-46cf-be03-645291c397aa, customEvt=null, allowMerge=true]
[20:00:18,358][INFO][exchange-worker-#63][GridDhtPartitionsExchangeFuture]
Finish exchange future [startVer=AffinityTopologyVersion [topVer=5,
minorTopVer=0], resVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
err=null]
[20:00:18,364][SEVERE][sys-#77][GridCacheIoManager] Failed processing message
[senderId=c50165fb-1afd-4b3e-8fba-ac825aa532fa,
msg=GridDhtPartitionsSingleMessage [parts=HashMap
{-553318226=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=490],
-553318133=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=512],
-553318412=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=490],
-553315529=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=490],
-553315497=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=490],
-553315498=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=490],
-2100569601=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=100],
-553318319=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=512],
374280891=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion [topVer=4,
minorTopVer=1], updateSeq=5, size=32], 374280890=GridDhtPartitionMap [moving=0,
top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=5, size=64],
374280889=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion [topVer=4,
minorTopVer=1], updateSeq=5, size=128], 374280888=GridDhtPartitionMap
[moving=0, top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=5,
size=512], 374280887=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=23], 374280886=GridDhtPartitionMap
[moving=0, top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=5,
size=31], 374280885=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=61], 374280884=GridDhtPartitionMap
[moving=0, top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=5,
size=490], -553315527=GridDhtPartitionMap [moving=0,
top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=5, size=512],
-553315495=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=5, size=512],
-553315528=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=4, size=490],
-553315496=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=4, size=512],
-553315526=GridDhtPartitionMap [moving=0, top=AffinityTopologyVersion
[topVer=4, minorTopVer=1], updateSeq=4, size=512]}, partCntrs=null,
partsSizes=HashMap {-553318226=HashMap {1=1, 2=1, 3=1, 4=1, 5=1, 6=1, 7=1, 9=1,
11=1, 13=1, 20=1, 21=1, 22=1, 24=1, 27=1, 28=1, 31=1, 32=1, 33=1, 34=1, 35=1,
36=1, 39=1, 42=1, 43=1, 47=1, 55=1, 57=1, 58=1, 63=1, 64=1, 65=1, 66=1, 67=1,
70=1, 71=1, 72=1, 73=1, 74=1, 75=1, 79=1, 80=1, 82=1, 84=1, 86=1, 88=1, 90=1,
95=1, 96=1, 99=1}, -553318133=HashMap {1=1, 2=1, 3=1, 4=1, 5=1, 6=1, 7=1, 8=1,
9=1, 10=1, 11=1, 12=1, 13=1, 14=1, 15=1, 16=1, 17=1, 18=1, 19=1, 20=1, 21=1,
22=1, 23=1, 24=1, 25=1, 26=1, 27=1, 28=1, 29=1, 30=1, 31=1, 32=1, 33=1, 34=1,
35=1, 36=1, 37=1, 38=1, 39=1, 40=1, 41=1, 42=1, 43=1, 44=1, 45=1, 46=1, 47=1,
48=1, 49=1, 50=1, 51=1, 52=1, 53=1, 54=1, 55=1, 56=1, 57=1, 58=1, 59=1, 60=1,
61=1, 62=1, 63=1, 64=1, 65=1, 66=1, 67=1, 68=1, 69=1, 70=1, 71=1, 72=1, 73=1,
74=1, 75=1, 76=1, 77=1, 78=1, 79=1, 80=1, 81=1, 82=1, 83=1, 84=1, 85=1, 86=1,
87=1, 88=1, 89=1, 90=1, 91=1, 92=1, 93=1, 94=1, 95=1, 96=1, 97=1, 98=1, 99=1,
100=1},
[jira] [Created] (IGNITE-10010) Node halted if table was dropped
Sergey Kozlov created IGNITE-10010:
--
Summary: Node halted if table was dropped
Key: IGNITE-10010
URL: https://issues.apache.org/jira/browse/IGNITE-10010
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start 2 nodes with PDS
2. Activate cluster
3. Connect sqlline.
4. Create table {{create table t1(a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";}}
5. Stop node 1
6. Drop table {{drop table t1;}}
7. Start node 1
8. Node 2 stopped by handler:
{noformat}
c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\ignite.bat server.xml -v -J-DID=1
Ignite Command Line Startup, ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV
2018 Copyright(C) Apache Software Foundation
[18:04:22,745][INFO][main][IgniteKernal]
>>>__
>>> / _/ ___/ |/ / _/_ __/ __/
>>> _/ // (7 7// / / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/
>>>
>>> ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV
>>> 2018 Copyright(C) Apache Software Foundation
>>>
>>> Ignite documentation: http://ignite.apache.org
[18:04:22,745][INFO][main][IgniteKernal] Config URL:
file:/c:/Work/apache-ignite-2.7.0-SNAPSHOT-bin/server.xml
[18:04:22,760][INFO][main][IgniteKernal] IgniteConfiguration
[igniteInstanceName=null, pubPoolSize=8, svcPoolSize=8, cal
lbackPoolSize=8, stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4,
igfsPoolSize=8, dataStreamerPoolSize=8, utilityCacheP
oolSize=8, utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8,
igniteHome=c:\Work\apache-ignite-2.7.0-SNAPSHO
T-bin, igniteWorkDir=c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin\work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@6f94
fa3e, nodeId=d02069db-6d0b-4a40-b185-1d95fa330853, marsh=BinaryMarshaller [],
marshLocJobs=false, daemon=false, p2pEnabl
ed=false, netTimeout=5000, sndRetryDelay=1000, sndRetryCnt=3,
metricsHistSize=1, metricsUpdateFreq=2000, metricsExpT
ime=9223372036854775807, discoSpi=TcpDiscoverySpi [addrRslvr=null,
sockTimeout=0, ackTimeout=0, marsh=null, reconCnt=10,
reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
clientReconnectDisabled=false, internalLsnr=null], segPlc=ST
OP, segResolveAttempts=2, waitForSegOnStart=true, allResolversPassReq=true,
segChkFreq=1, commSpi=TcpCommunicationSp
i [connectGate=null,
connPlc=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$FirstConnectionPolicy@22ff4249,
enableForcibleNodeKill=false, enableTroubleshootingLog=false, locAddr=null,
locHost=null, locPort=47100, locPortRange=1
00, shmemPort=-1, directBuf=true, directSndBuf=false, idleConnTimeout=60,
connTimeout=5000, maxConnTimeout=60, r
econCnt=10, sockSndBuf=32768, sockRcvBuf=32768, msgQueueLimit=0,
slowClientQueueLimit=0, nioSrvr=null, shmemSrv=null, us
ePairedConnections=false, connectionsPerNode=1, tcpNoDelay=true,
filterReachableAddresses=false, ackSndThreshold=32, una
ckedMsgsBufSize=0, sockWriteTimeout=2000, boundTcpPort=-1,
boundTcpShmemPort=-1, selectorsCnt=4, selectorSpins=0, addrRs
lvr=null, ctxInitLatch=java.util.concurrent.CountDownLatch@2d1ef81a[Count = 1],
stopping=false], evtSpi=org.apache.ignit
e.spi.eventstorage.NoopEventStorageSpi@4c402120, colSpi=NoopCollisionSpi [],
deploySpi=LocalDeploymentSpi [], indexingSp
i=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@815b41f, addrRslvr=null,
encryptionSpi=org.apache.ignite.spi.encry
ption.noop.NoopEncryptionSpi@5542c4ed, clientMode=false,
rebalanceThreadPoolSize=1, txCfg=TransactionConfiguration [txSe
rEnabled=false, dfltIsolation=REPEATABLE_READ, dfltConcurrency=PESSIMISTIC,
dfltTxTimeout=0, txTimeoutOnPartitionMapExch
ange=0, pessimisticTxLogSize=0, pessimisticTxLogLinger=1,
tmLookupClsName=null, txManagerFactory=null, useJtaSync=fa
lse], cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED,
p2pMissedCacheSize=100, locHost=127.0.0.
1, timeSrvPortBase=31100, timeSrvPortRange=100, failureDetectionTimeout=1,
sysWorkerBlockedTimeout=null, clientFailu
reDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null,
connectorCfg=ConnectorConfiguration [jettyPath=null, hos
t=null, port=11211, noDelay=true, directBuf=false, sndBufSize=32768,
rcvBufSize=32768, idleQryCurTimeout=60, idleQry
CurCheckFreq=6, sndQueueLimit=0, selectorCnt=4, idleTimeout=7000,
sslEnabled=false, sslClientAuth=false, sslCtxFacto
ry=null, sslFactory=null, portRange=100, threadPoolSize=8,
msgInterceptor=null], odbcCfg=null, warmupClos=null, atomicCf
g=AtomicConfiguration [seqReserveSize=1000, cacheMode=PARTITIONED, backups=1,
aff=null, grpName=null], classLdr=null, ss
lCtxFactory=null, platformCfg=null, binaryCfg=BinaryConfiguration
[idMapper=null, nameMapper=null, serializer=null, comp
actFooter=true], memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration
[sysRegionInitSize=52428800,
[jira] [Created] (IGNITE-10007) Deactivation hangs if an open transaction exists
Sergey Kozlov created IGNITE-10007:
--
Summary: Deactivation hangs if an open transaction exists
Key: IGNITE-10007
URL: https://issues.apache.org/jira/browse/IGNITE-10007
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start 2 node with PDS
2. Activate cluster
3. Connect sqlline
4. Create table {{create table t1(a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";}}
3.Start TX and execute a DML commnd:
{noformat}
begin;
insert into t1 values (1, '1');
{noformat}
4. Try deactivate cluster {{bin/control.bat --deactivate}}. The scripts doesn't
return control.
5. Show LRT:
{noformat}
c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User:
Matching transactions:
TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
order=1, ver=2.7.0#19700101-sha1:,
isClient=false, consistentId=1]
Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
state=ACTIVE, startTime=2018-10-25 17:34:35.5
22, duration=352, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
topVer=AffinityTopologyVersion [topVer=2, minorTop
Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
[5d3e8936]]
{noformat}
6. Complete TX:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> commit;
Error: class org.apache.ignite.IgniteException: Can not perform the operation
because the cluster is inactive. Note, tha
t the cluster is considered inactive by default if Ignite Persistent Store is
used to let all the nodes join the cluster
. To activate the cluster call Ignite.active(true). (state=5,code=1)
java.sql.SQLException: class org.apache.ignite.IgniteException: Can not perform
the operation because the cluster is ina
ctive. Note, that the cluster is considered inactive by default if Ignite
Persistent Store is used to let all the nodes
join the cluster. To activate the cluster call Ignite.active(true).
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/>
{noformat}
It.s ok but LRT is still presented and deactivation script doesn't return
control back to user:
{noformat}
c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User:
Matching transactions:
TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
order=1, ver=2.7.0#19700101-sha1:,
isClient=false, consistentId=1]
Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
state=ACTIVE, startTime=2018-10-25 17:34:35.5
22, duration=510, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
topVer=AffinityTopologyVersion [topVer=2, minorTop
Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
[5d3e8936]]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10004) Parse error leads to leave the transaction
Sergey Kozlov created IGNITE-10004:
--
Summary: Parse error leads to leave the transaction
Key: IGNITE-10004
URL: https://issues.apache.org/jira/browse/IGNITE-10004
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Sergey Kozlov
1. Start 2 nodes + connect sqlline
2. Execute following queries:
{noformat}
create table t10 (a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
begin;
insert into t10 values(1); <- worng set
insert into t10 values(2, '2'); <- coorect set
commit;
{noformat}
The output:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
SHOT,backups=1";
No rows affected (0,032 seconds)
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Неверное количество столбцов
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
Error: Transaction is already completed. (state=25000,code=5004)
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9971) MLPTrainer example failures
[
https://issues.apache.org/jira/browse/IGNITE-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-9971:
--
Description:
The example run output looks like non clear:
{noformat}
>>> Ignite grid started.
окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
WARNING: Failed to load implementation from:
com.github.fommil.netlib.NativeSystemBLAS
окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
WARNING: Failed to load implementation from:
com.github.fommil.netlib.NativeRefBLAS
>>> Fail percentage: 0.0%.
>>> Distributed multilayer perceptron example completed.
{noformat}
Also second run of the example with running server node {{ExampleNodeStartup}}
fails:
{noformat}
>>> Ignite grid started.
Exception in thread "MLPTrainerExample-#51"
org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache
with the same name is already started): TRAINING_SET
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2973)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2912)
at
org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2761)
at
org.apache.ignite.examples.ml.nn.MLPTrainerExample.lambda$main$0(MLPTrainerExample.java:71)
at java.lang.Thread.run(Thread.java:745)
[12:46:14] Ignite node stopped OK [uptime=00:00:00.033]
{noformat}
was:
The example run output looks like non-clear:
{noformat}
>>> Ignite grid started.
окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
WARNING: Failed to load implementation from:
com.github.fommil.netlib.NativeSystemBLAS
окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
WARNING: Failed to load implementation from:
com.github.fommil.netlib.NativeRefBLAS
>>> Fail percentage: 0.0%.
>>> Distributed multilayer perceptron example completed.
{noformat}
Also second run of the example with running server node {{ExampleNodeStartup}}
fails:
{noformat}
>>> Ignite grid started.
Exception in thread "MLPTrainerExample-#51"
org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache
with the same name is already started): TRAINING_SET
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2973)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2912)
at
org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2761)
at
org.apache.ignite.examples.ml.nn.MLPTrainerExample.lambda$main$0(MLPTrainerExample.java:71)
at java.lang.Thread.run(Thread.java:745)
[12:46:14] Ignite node stopped OK [uptime=00:00:00.033]
{noformat}
> MLPTrainer example failures
> ---
>
> Key: IGNITE-9971
> URL: https://issues.apache.org/jira/browse/IGNITE-9971
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Sergey Kozlov
>Priority: Major
>
> The example run output looks like non clear:
> {noformat}
> >>> Ignite grid started.
> окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
> WARNING: Failed to load implementation from:
> com.github.fommil.netlib.NativeSystemBLAS
> окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
> WARNING: Failed to load implementation from:
> com.github.fommil.netlib.NativeRefBLAS
> >>> Fail percentage: 0.0%.
> >>> Distributed multilayer perceptron example completed.
> {noformat}
> Also second run of the example with running server node
> {{ExampleNodeStartup}} fails:
> {noformat}
> >>> Ignite grid started.
> Exception in thread "MLPTrainerExample-#51"
> org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache
> with the same name is already started): TRAINING_SET
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4431)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2973)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2912)
> at
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2761)
> at
> org.apache.ignite.examples.ml.nn.MLPTrainerExample.lambda$main$0(MLPTrainerExample.java:71)
> at java.lang.Thread.run(Thread.java:745)
> [12:46:14] Ignite node stopped OK [uptime=00:00:00.033]
> {noformat}
--
This message was sent by Atlassian JIRA
[jira] [Created] (IGNITE-9971) MLPTrainer example failures
Sergey Kozlov created IGNITE-9971:
-
Summary: MLPTrainer example failures
Key: IGNITE-9971
URL: https://issues.apache.org/jira/browse/IGNITE-9971
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Sergey Kozlov
The example run output looks like non-clear:
{noformat}
>>> Ignite grid started.
окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
WARNING: Failed to load implementation from:
com.github.fommil.netlib.NativeSystemBLAS
окт 23, 2018 12:42:51 PM com.github.fommil.netlib.BLAS
WARNING: Failed to load implementation from:
com.github.fommil.netlib.NativeRefBLAS
>>> Fail percentage: 0.0%.
>>> Distributed multilayer perceptron example completed.
{noformat}
Also second run of the example with running server node {{ExampleNodeStartup}}
fails:
{noformat}
>>> Ignite grid started.
Exception in thread "MLPTrainerExample-#51"
org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache
with the same name is already started): TRAINING_SET
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2973)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2912)
at
org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2761)
at
org.apache.ignite.examples.ml.nn.MLPTrainerExample.lambda$main$0(MLPTrainerExample.java:71)
at java.lang.Thread.run(Thread.java:745)
[12:46:14] Ignite node stopped OK [uptime=00:00:00.033]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9918) Default configuration missed
[
https://issues.apache.org/jira/browse/IGNITE-9918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-9918:
--
Description:
Node start failed if try to execute {{bin\ignite.bat}} without arguments:
{noformat}
C:\GitRoot\gg-qa\i2test\var\suite-client\ignite\bin>ignite.bat
class org.apache.ignite.IgniteException: Spring XML configuration path is
invalid: config\default-config.xml. Note that
this path should be either absolute or a relative local file system path,
relative to META-INF in classpath or valid URL
to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1014)
at org.apache.ignite.Ignition.start(Ignition.java:351)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Spring XML
configuration path is invalid: config\default-conf
ig.xml. Note that this path should be either absolute or a relative local file
system path, relative to META-INF in clas
spath or valid URL to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:730)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:699)
at org.apache.ignite.Ignition.start(Ignition.java:348)
... 1 more
Caused by: java.net.MalformedURLException: no protocol:
config\default-config.xml
at java.net.URL.(URL.java:593)
at java.net.URL.(URL.java:490)
at java.net.URL.(URL.java:439)
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3849)
... 5 more
Failed to start grid: Spring XML configuration path is invalid:
config\default-config.xml. Note that this path should be
either absolute or a relative local file system path, relative to META-INF in
classpath or valid URL to IGNITE_HOME.
{noformat}
Obviously that there's no {{config/default-config.xml}}
was:
Node start failed if try to execute {{bin/ignite.sh}} without arguments:
{noformat}
C:\GitRoot\gg-qa\i2test\var\suite-client\ignite\bin>ignite.bat
class org.apache.ignite.IgniteException: Spring XML configuration path is
invalid: config\default-config.xml. Note that
this path should be either absolute or a relative local file system path,
relative to META-INF in classpath or valid URL
to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1014)
at org.apache.ignite.Ignition.start(Ignition.java:351)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Spring XML
configuration path is invalid: config\default-conf
ig.xml. Note that this path should be either absolute or a relative local file
system path, relative to META-INF in clas
spath or valid URL to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:730)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:699)
at org.apache.ignite.Ignition.start(Ignition.java:348)
... 1 more
Caused by: java.net.MalformedURLException: no protocol:
config\default-config.xml
at java.net.URL.(URL.java:593)
at java.net.URL.(URL.java:490)
at java.net.URL.(URL.java:439)
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3849)
... 5 more
Failed to start grid: Spring XML configuration path is invalid:
config\default-config.xml. Note that this path should be
either absolute or a relative local file system path, relative to META-INF in
classpath or valid URL to IGNITE_HOME.
{noformat}
Obviously that there's no {{config/default-config.xml}}
> Default configuration missed
>
>
> Key: IGNITE-9918
> URL: https://issues.apache.org/jira/browse/IGNITE-9918
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 2.7
>
>
> Node start failed if try to execute {{bin\ignite.bat}} without arguments:
> {noformat}
> C:\GitRoot\gg-qa\i2test\var\suite-client\ignite\bin>ignite.bat
> class org.apache.ignite.IgniteException: Spring XML configuration path is
> invalid: config\default-config.xml. Note that
> this path should be either absolute or a relative local file system path,
> relative to META-INF in classpath or valid URL
> to IGNITE_HOME.
>
[jira] [Created] (IGNITE-9918) Default configuration missed
Sergey Kozlov created IGNITE-9918:
-
Summary: Default configuration missed
Key: IGNITE-9918
URL: https://issues.apache.org/jira/browse/IGNITE-9918
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
Node start failed if try to execute {{bin/ignite.sh}} without arguments:
{noformat}
C:\GitRoot\gg-qa\i2test\var\suite-client\ignite\bin>ignite.bat
class org.apache.ignite.IgniteException: Spring XML configuration path is
invalid: config\default-config.xml. Note that
this path should be either absolute or a relative local file system path,
relative to META-INF in classpath or valid URL
to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1014)
at org.apache.ignite.Ignition.start(Ignition.java:351)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Spring XML
configuration path is invalid: config\default-conf
ig.xml. Note that this path should be either absolute or a relative local file
system path, relative to META-INF in clas
spath or valid URL to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:858)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:730)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:699)
at org.apache.ignite.Ignition.start(Ignition.java:348)
... 1 more
Caused by: java.net.MalformedURLException: no protocol:
config\default-config.xml
at java.net.URL.(URL.java:593)
at java.net.URL.(URL.java:490)
at java.net.URL.(URL.java:439)
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3849)
... 5 more
Failed to start grid: Spring XML configuration path is invalid:
config\default-config.xml. Note that this path should be
either absolute or a relative local file system path, relative to META-INF in
classpath or valid URL to IGNITE_HOME.
{noformat}
Obviously that there's no {{config/default-config.xml}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
