[jira] [Commented] (IGNITE-11469) Support Automatic modules for ignite-rest-http: resolve package inference between Jetty & Tomcat
[
https://issues.apache.org/jira/browse/IGNITE-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790474#comment-16790474
]
Alex Volkov commented on IGNITE-11469:
--
Now build from master fails on start when rest is enabled with error:
{code:java}
Exception during start processors, node will be stopped and close connections
java.lang.NoClassDefFoundError: javax/servlet/ServletRequest
at
org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.start(GridJettyRestProtocol.java:127)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.startProtocol(GridRestProcessor.java:1013)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.startHttpProtocol(GridRestProcessor.java:984)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.start(GridRestProcessor.java:541)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1759)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1035)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1992)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1683)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1109)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1027)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:913)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:812)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:682)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:651)
at org.apache.ignite.Ignition.start(Ignition.java:346)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:300)
Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletRequest
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 16 more
{code}
on Java 8.
> Support Automatic modules for ignite-rest-http: resolve package inference
> between Jetty & Tomcat
>
>
> Key: IGNITE-11469
> URL: https://issues.apache.org/jira/browse/IGNITE-11469
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> error: the unnamed module reads package javax.servlet.http from both
> javax.servlet.api and tomcat.servlet.api
> error: the unnamed module reads package javax.servlet.descriptor from both
> javax.servlet.api and tomcat.servlet.api
> error: the unnamed module reads package javax.servlet.annotation from both
> javax.servlet.api and tomcat.servlet.api
> error: the unnamed module reads package javax.servlet from both
> javax.servlet.api and tomcat.servlet.api
> {noformat}
> Exclude of tomcat dependency solves the problem
> {code}
> compile(group: 'org.apache.ignite', name: 'ignite-rest-http', version:
> ignVer) {
> exclude group: 'org.apache.tomcat'
> // to remove "javax.servlet.http, javax.servlet.descriptor,
> javax.servlet.annotation, javax.servlet" package conflicts.
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10998) Option --check-crc is not shown in help for control.sh
Alex Volkov created IGNITE-10998: Summary: Option --check-crc is not shown in help for control.sh Key: IGNITE-10998 URL: https://issues.apache.org/jira/browse/IGNITE-10998 Project: Ignite Issue Type: Bug Affects Versions: 2.8 Reporter: Alex Volkov After implementing IGNITE-10507 it seems like this option (--check-crc) is not shown in help for control.sh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10802) Documentation for option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE
Alex Volkov created IGNITE-10802: Summary: Documentation for option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE Key: IGNITE-10802 URL: https://issues.apache.org/jira/browse/IGNITE-10802 Project: Ignite Issue Type: Task Components: documentation Affects Versions: 2.8 Reporter: Alex Volkov After implementation -IGNITE-10172- it's not clear how cluster should behave in some cases. For example, if I have cluster with option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=True and one additional node with flag IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=False comes to this cluster. What behaviour should I expect from the cluster? In general, please provide documentation for this option. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10660) Can't drop index created for dynamic cache
Alex Volkov created IGNITE-10660:
Summary: Can't drop index created for dynamic cache
Key: IGNITE-10660
URL: https://issues.apache.org/jira/browse/IGNITE-10660
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Alex Volkov
Here are steps to reproduce:
# Start cluster with persistence.
# Start cache with configuration (transactional, replicated full_sync with
query entity).
# Connect to cluster using sqlline.
# Create index on this cache.
# Try to drop index created on step 4.
Expecting result:
Index dropped.
Actual result:
Got error:
{code:java}
[avolkov@lab37 bin]$ ./sqlline.sh --color=true --verbose=true
--showWarnings=true --showNestedErrs=true --outputFormat=csv -u
jdbc:ignite:thin://lab37:10800
Setting property: [showWarnings, true]
Setting property: [showNestedErrs, true]
Setting property: [outputFormat, csv]
issuing: !connect jdbc:ignite:thin://lab37:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver
Connecting to jdbc:ignite:thin://lab37:10800
Connected to: Apache Ignite (version 2.7.1#20181210-sha1:a39dbf0f)
Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181210-sha1:a39dbf0f)
Autocommit status: true
Transaction isolation: TRANSACTION_REPEATABLE_READ
sqlline version 1.3.0
0: jdbc:ignite:thin://lab37:10800> !tables
'TABLE_CAT','TABLE_SCHEM','TABLE_NAME','TABLE_TYPE','REMARKS','TYPE_CAT','TYPE_SCHEM','TYPE_NAME','SELF_REFERENCING_COL_NAME','REF_GENERATION'
'','cache_group_1_015','ALLTYPESINDEXED','TABLE','','','','','',''
'','cache_group_1_001','ALLTYPESINDEXED','TABLE','','','','','',''
'','cache1','ALLTYPESINDEXED','TABLE','','','','','',''
0: jdbc:ignite:thin://lab37:10800> select * from "cache1".ALLTYPESINDEXED;
'STRCOL','LONGCOL'
No rows selected (0.576 seconds)
0: jdbc:ignite:thin://lab37:10800> create index test_idx_1 on
"cache1".ALLTYPESINDEXED(STRCOL);
No rows affected (0.05 seconds)
0: jdbc:ignite:thin://lab37:10800> drop index test_idx_1;
Error: Index doesn't exist: TEST_IDX_1 (state=42000,code=3006)
java.sql.SQLException: Index doesn't exist: TEST_IDX_1
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://lab37:10800> !index
'TABLE_CAT','TABLE_SCHEM','TABLE_NAME','NON_UNIQUE','INDEX_QUALIFIER','INDEX_NAME','TYPE','ORDINAL_POSITION','COLUMN_NAME','ASC_OR_DESC','CARDINALITY','PAGES','FILTER_CONDITION'
'','cache_group_1_001','ALLTYPESINDEXED','true','','ALLTYPESINDEXED_LONGCOL_IDX','3','0','LONGCOL','A','0','0',''
'','cache1','ALLTYPESINDEXED','true','','ALLTYPESINDEXED_STRCOL_ASC_IDX','3','0','STRCOL','A','0','0',''
'','cache1','ALLTYPESINDEXED','true','','TEST_IDX_1','3','0','STRCOL','A','0','0',''
'','cache_group_1_015','ALLTYPESINDEXED','true','','ALLTYPESINDEXED_LONGCOL_IDX','3','0','LONGCOL','A','0','0',''
{code}
In node log I see the exception:
{code:java}
[16:01:15,412][SEVERE][client-connector-#179][JdbcRequestHandler] Failed to
execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC,
pageSize=1024, maxRows=0, sqlQry=drop index test_idx_1, args=[],
stmtType=ANY_STATEMENT_TYPE, autoCommit=true]]
class org.apache.ignite.internal.processors.query.IgniteSQLException: Index
doesn't exist: TEST_IDX_1
at
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:644)
at
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:244)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFieldsNative(IgniteH2Indexing.java:1977)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2141)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2135)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2130)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2707)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2144)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
[jira] [Created] (IGNITE-9359) OptimizeMakeChangeGAExample hangs forever with additional nods in topology
Alex Volkov created IGNITE-9359:
---
Summary: OptimizeMakeChangeGAExample hangs forever with additional
nods in topology
Key: IGNITE-9359
URL: https://issues.apache.org/jira/browse/IGNITE-9359
Project: Ignite
Issue Type: Bug
Components: ml
Affects Versions: 2.6
Reporter: Alex Volkov
To reproduce this issue please follow these steps:
1. Run two nodes using ignite.sh script.
For example:
{code:java}
bin/ignite.sh examples/config/example-ignite.xml -J-Xmx1g -J-Xms1g
-J-DCONSISTENT_ID=node1 -J-DIGNITE_QUIET=false
{code}
2. Run HelloWorldGAExample from IDEA IDE.
*Expecting result:*
Example successfully run and completed.
*Actual result:*
There are a lot of NPE exceptions in example log:
{code:java}
[2018-08-23 17:38:59,246][ERROR][pub-#20][GridJobWorker] Failed to execute job
due to unexpected runtime exception
[jobId=2a309376561-70889d5c-33f2-4c96-bf1e-f280c0ac4a1c, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl [taskName=o.a.i.ml.genetic.FitnessTask,
dep=GridDeployment [ts=1535035116486, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
clsLdrId=4baf8376561-70889d5c-33f2-4c96-bf1e-f280c0ac4a1c, userVer=0, loc=true,
sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
pendingUndeploy=false, undeployed=false, usage=2],
taskClsName=o.a.i.ml.genetic.FitnessTask,
sesId=b4209376561-70889d5c-33f2-4c96-bf1e-f280c0ac4a1c,
startTime=1535035123014, endTime=9223372036854775807,
taskNodeId=70889d5c-33f2-4c96-bf1e-f280c0ac4a1c,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=false,
topPred=o.a.i.i.cluster.ClusterGroupAdapter$AttributeFilter@5668ad01,
subjId=70889d5c-33f2-4c96-bf1e-f280c0ac4a1c, mapFut=GridFutureAdapter
[ignoreInterrupts=false, state=INIT, res=null, hash=574227802]IgniteFuture
[orig=], execName=null],
jobId=2a309376561-70889d5c-33f2-4c96-bf1e-f280c0ac4a1c], err=null]
java.lang.NullPointerException
at org.apache.ignite.ml.genetic.FitnessJob.execute(FitnessJob.java:76)
at org.apache.ignite.ml.genetic.FitnessJob.execute(FitnessJob.java:35)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6749)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
and it hangs on this one:
{code:java}
[2018-08-23 17:38:59,582][WARN ][sys-#54][AlwaysFailoverSpi] Received topology
with only nodes that job had failed on (forced to fail)
[failedNodes=[3db84480-08b8-4d54-9d3a-e23b53761f29,
70889d5c-33f2-4c96-bf1e-f280c0ac4a1c, 4f815cff-f77c-4a41-9ae1-ebb00b1dd44c]]
class org.apache.ignite.cluster.ClusterTopologyException: Failed to failover a
job to another node (failover SPI returned null)
[job=org.apache.ignite.ml.genetic.FitnessJob@1045c79e, node=TcpDiscoveryNode
[id=4f815cff-f77c-4a41-9ae1-ebb00b1dd44c, addrs=ArrayList [0:0:0:0:0:0:0:1,
127.0.0.1, 172.25.4.42, 172.25.4.92], sockAddrs=HashSet [/172.25.4.92:47501,
/172.25.4.42:47501, /0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501], discPort=47501,
order=2, intOrder=2, lastExchangeTime=1535035115978, loc=false,
ver=2.7.0#19700101-sha1:, isClient=false]]
at org.apache.ignite.internal.util.IgniteUtils$7.apply(IgniteUtils.java:853)
at org.apache.ignite.internal.util.IgniteUtils$7.apply(IgniteUtils.java:851)
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:985)
at
org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:541)
at org.apache.ignite.ml.genetic.GAGrid.calculateFitness(GAGrid.java:102)
at org.apache.ignite.ml.genetic.GAGrid.evolve(GAGrid.java:171)
at
org.apache.ignite.examples.ml.genetic.change.OptimizeMakeChangeGAExample.main(OptimizeMakeChangeGAExample.java:148)
Caused by: class
org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to
failover a job to another node (failover SPI returned null)
[job=org.apache.ignite.ml.genetic.FitnessJob@1045c79e, node=TcpDiscoveryNode
[id=4f815cff-f77c-4a41-9ae1-ebb00b1dd44c, addrs=ArrayList [0:0:0:0:0:0:0:1,
127.0.0.1, 172.25.4.42, 172.25.4.92], sockAddrs=HashSet [/172.25.4.92:47501,
/172.25.4.42:47501, /0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501], discPort=47501,
order=2, intOrder=2, lastExchangeTime=1535035115978, loc=false,
ver=2.7.0#19700101-sha1:, isClient=false]]
at
[jira] [Updated] (IGNITE-9354) HelloWorldGAExample hangs forever with additional nods in topology
[
https://issues.apache.org/jira/browse/IGNITE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Volkov updated IGNITE-9354:
Attachment: log.zip
> HelloWorldGAExample hangs forever with additional nods in topology
> --
>
> Key: IGNITE-9354
> URL: https://issues.apache.org/jira/browse/IGNITE-9354
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.6
>Reporter: Alex Volkov
>Priority: Major
> Attachments: log.zip
>
>
> To reproduce this issue please follow these steps:
> 1. Run two nodes using ignite.sh script.
> For example:
> {code:java}
> bin/ignite.sh examples/config/example-ignite.xml -J-Xmx1g -J-Xms1g
> -J-DCONSISTENT_ID=node1 -J-DIGNITE_QUIET=false
> {code}
> 2. Run HelloWorldGAExample from IDEA IDE.
> *Expecting result:*
> Example successfully run and completed.
> *Actual result:*
> There are a lot of NPE exceptions in example log:
> {code:java}
> [2018-08-23 09:49:25,029][ERROR][pub-#19][GridJobWorker] Failed to execute
> job due to unexpected runtime exception
> [jobId=c296b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.ml.genetic.FitnessTask, dep=GridDeployment [ts=1535006960878,
> depMode=SHARED, clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
> clsLdrId=8d16b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, userVer=0,
> loc=true,
> sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
> pendingUndeploy=false, undeployed=false, usage=2],
> taskClsName=o.a.i.ml.genetic.FitnessTask,
> sesId=b196b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1,
> startTime=1535006964236, endTime=9223372036854775807,
> taskNodeId=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1,
> clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
> failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=false,
> topPred=o.a.i.i.cluster.ClusterGroupAdapter$AttributeFilter@2d746ce4,
> subjId=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, mapFut=GridFutureAdapter
> [ignoreInterrupts=false, state=INIT, res=null, hash=679592043]IgniteFuture
> [orig=], execName=null],
> jobId=c296b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1], err=null]
> java.lang.NullPointerException
> at org.apache.ignite.ml.genetic.FitnessJob.execute(FitnessJob.java:76)
> at org.apache.ignite.ml.genetic.FitnessJob.execute(FitnessJob.java:35)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6749)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> and it hangs on this one:
> {code:java}
> [2018-08-23 09:49:35,229][WARN ][pub-#17][AlwaysFailoverSpi] Received
> topology with only nodes that job had failed on (forced to fail)
> [failedNodes=[eac48ea7-da79-453a-a94c-291039c5cc15,
> 0907d876-e0ce-4fda-966d-ad91a03f9722, e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1]]
> class org.apache.ignite.cluster.ClusterTopologyException: Failed to failover
> a job to another node (failover SPI returned null)
> [job=org.apache.ignite.ml.genetic.FitnessJob@35f8a9d3, node=TcpDiscoveryNode
> [id=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, addrs=ArrayList [0:0:0:0:0:0:0:1,
> 127.0.0.1, 172.25.4.42, 172.25.4.92], sockAddrs=HashSet [/172.25.4.42:47502,
> /172.25.4.92:47502, /0:0:0:0:0:0:0:1:47502, /127.0.0.1:47502],
> discPort=47502, order=3, intOrder=3, lastExchangeTime=1535006974981,
> loc=true, ver=2.7.0#19700101-sha1:, isClient=false]]
> at org.apache.ignite.internal.util.IgniteUtils$7.apply(IgniteUtils.java:853)
> at org.apache.ignite.internal.util.IgniteUtils$7.apply(IgniteUtils.java:851)
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:985)
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:541)
> at org.apache.ignite.ml.genetic.GAGrid.calculateFitness(GAGrid.java:102)
> at org.apache.ignite.ml.genetic.GAGrid.evolve(GAGrid.java:171)
> at
> org.apache.ignite.examples.ml.genetic.helloworld.HelloWorldGAExample.main(HelloWorldGAExample.java:90)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to
> failover a job to another node (failover SPI returned null)
> [job=org.apache.ignite.ml.genetic.FitnessJob@35f8a9d3,
[jira] [Created] (IGNITE-9354) HelloWorldGAExample hangs forever with additional nods in topology
Alex Volkov created IGNITE-9354:
---
Summary: HelloWorldGAExample hangs forever with additional nods in
topology
Key: IGNITE-9354
URL: https://issues.apache.org/jira/browse/IGNITE-9354
Project: Ignite
Issue Type: Bug
Components: ml
Affects Versions: 2.6
Reporter: Alex Volkov
Attachments: log.zip
To reproduce this issue please follow these steps:
1. Run two nodes using ignite.sh script.
For example:
{code:java}
bin/ignite.sh examples/config/example-ignite.xml -J-Xmx1g -J-Xms1g
-J-DCONSISTENT_ID=node1 -J-DIGNITE_QUIET=false
{code}
2. Run HelloWorldGAExample from IDEA IDE.
*Expecting result:*
Example successfully run and completed.
*Actual result:*
There are a lot of NPE exceptions in example log:
{code:java}
[2018-08-23 09:49:25,029][ERROR][pub-#19][GridJobWorker] Failed to execute job
due to unexpected runtime exception
[jobId=c296b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl [taskName=o.a.i.ml.genetic.FitnessTask,
dep=GridDeployment [ts=1535006960878, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
clsLdrId=8d16b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, userVer=0, loc=true,
sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
pendingUndeploy=false, undeployed=false, usage=2],
taskClsName=o.a.i.ml.genetic.FitnessTask,
sesId=b196b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1,
startTime=1535006964236, endTime=9223372036854775807,
taskNodeId=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=false,
topPred=o.a.i.i.cluster.ClusterGroupAdapter$AttributeFilter@2d746ce4,
subjId=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, mapFut=GridFutureAdapter
[ignoreInterrupts=false, state=INIT, res=null, hash=679592043]IgniteFuture
[orig=], execName=null],
jobId=c296b856561-e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1], err=null]
java.lang.NullPointerException
at org.apache.ignite.ml.genetic.FitnessJob.execute(FitnessJob.java:76)
at org.apache.ignite.ml.genetic.FitnessJob.execute(FitnessJob.java:35)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6749)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
and it hangs on this one:
{code:java}
[2018-08-23 09:49:35,229][WARN ][pub-#17][AlwaysFailoverSpi] Received topology
with only nodes that job had failed on (forced to fail)
[failedNodes=[eac48ea7-da79-453a-a94c-291039c5cc15,
0907d876-e0ce-4fda-966d-ad91a03f9722, e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1]]
class org.apache.ignite.cluster.ClusterTopologyException: Failed to failover a
job to another node (failover SPI returned null)
[job=org.apache.ignite.ml.genetic.FitnessJob@35f8a9d3, node=TcpDiscoveryNode
[id=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, addrs=ArrayList [0:0:0:0:0:0:0:1,
127.0.0.1, 172.25.4.42, 172.25.4.92], sockAddrs=HashSet [/172.25.4.42:47502,
/172.25.4.92:47502, /0:0:0:0:0:0:0:1:47502, /127.0.0.1:47502], discPort=47502,
order=3, intOrder=3, lastExchangeTime=1535006974981, loc=true,
ver=2.7.0#19700101-sha1:, isClient=false]]
at org.apache.ignite.internal.util.IgniteUtils$7.apply(IgniteUtils.java:853)
at org.apache.ignite.internal.util.IgniteUtils$7.apply(IgniteUtils.java:851)
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:985)
at
org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:541)
at org.apache.ignite.ml.genetic.GAGrid.calculateFitness(GAGrid.java:102)
at org.apache.ignite.ml.genetic.GAGrid.evolve(GAGrid.java:171)
at
org.apache.ignite.examples.ml.genetic.helloworld.HelloWorldGAExample.main(HelloWorldGAExample.java:90)
Caused by: class
org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to
failover a job to another node (failover SPI returned null)
[job=org.apache.ignite.ml.genetic.FitnessJob@35f8a9d3, node=TcpDiscoveryNode
[id=e5eca24b-6f5a-4d3e-9e9e-94ad404b44d1, addrs=ArrayList [0:0:0:0:0:0:0:1,
127.0.0.1, 172.25.4.42, 172.25.4.92], sockAddrs=HashSet [/172.25.4.42:47502,
/172.25.4.92:47502, /0:0:0:0:0:0:0:1:47502, /127.0.0.1:47502], discPort=47502,
order=3, intOrder=3, lastExchangeTime=1535006974981, loc=true,
ver=2.7.0#19700101-sha1:, isClient=false]]
at
[jira] [Created] (IGNITE-9091) IEP-25: creating documentation
Alex Volkov created IGNITE-9091: --- Summary: IEP-25: creating documentation Key: IGNITE-9091 URL: https://issues.apache.org/jira/browse/IGNITE-9091 Project: Ignite Issue Type: Task Components: documentation Reporter: Alex Volkov It would be great to have proper documentation for IEP-25: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-25:+Partition+Map+Exchange+hangs+resolving] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7862) Update flatten-plugin to 1.0.1 version
[
https://issues.apache.org/jira/browse/IGNITE-7862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401778#comment-16401778
]
Alex Volkov commented on IGNITE-7862:
-
Tested with examples. Looks fine, no errors.
> Update flatten-plugin to 1.0.1 version
> --
>
> Key: IGNITE-7862
> URL: https://issues.apache.org/jira/browse/IGNITE-7862
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> With flatten-plugin version {{1.0.0-beta-3}} we has to enlist all transitive
> dependencies.
> dev-list discussion -
> http://apache-ignite-developers.2346864.n4.nabble.com/Maven-Issues-with-flatten-plugin-td27537.html
> Solution is to update plugin to {{1.0.1}} version
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7480) Select for BINARY type field returns 'strange' value.
Alex Volkov created IGNITE-7480:
---
Summary: Select for BINARY type field returns 'strange' value.
Key: IGNITE-7480
URL: https://issues.apache.org/jira/browse/IGNITE-7480
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.2
Reporter: Alex Volkov
Steps to reproduce:
# Connect to grid using console client and dbc:ignite:thin driver.
# Run these sql statements:
{code:java}
CREATE TABLE tmp_table_binary (key_field INT PRIMARY KEY,field1 BINARY);
INSERT INTO tmp_table_binary (key_field, field1) values(1, '00ffaa');
INSERT INTO tmp_table_binary (key_field, field1) values(2, 'ffccaa');
SELECT * FROM tmp_table_binary;
{code}
Here is output from H2:
{code:java}
SELECT * FROM tmp_table_binary;
KEY_FIELD FIELD1
1 00ffaa
2 ffccaa
{code}
And this one is from grid:
{code}
0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE tmp_table_binary (key_field INT
PRIMARY KEY,field1 BINARY);
No rows affected (0.155 seconds)
0: jdbc:ignite:thin://127.0.0.1/> INSERT INTO tmp_table_binary (key_field,
field1) values(1, '00ffaa');
1 row affected (0.089 seconds)
0: jdbc:ignite:thin://127.0.0.1/> INSERT INTO tmp_table_binary (key_field,
field1) values(2, 'ffccaa');
1 row affected (0.009 seconds)
0: jdbc:ignite:thin://127.0.0.1/> SELECT * FROM tmp_table_binary;
+++
| KEY_FIELD| FIELD1 |
+++
| 1 | [B@6219232f|
| 2 | [B@605514f9|
+++
2 rows selected (0.09 seconds)
0: jdbc:ignite:thin://127.0.0.1/> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7479) NOT NULL constraints for complex PK
Alex Volkov created IGNITE-7479:
---
Summary: NOT NULL constraints for complex PK
Key: IGNITE-7479
URL: https://issues.apache.org/jira/browse/IGNITE-7479
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Alex Volkov
According to SQL ANSI 99 spec (11.7 point 5)
If the < unique specification > specifies PRIMARY KEY, then for each < column
name > in the explicit or implicit < unique column list > for which NOT NULL is
not specified, NOT NULL is implicit in the < column definition >.
But now we have violation:
{code:java}
0: jdbc:ignite:thin://127.0.0.1:10800/> create table
tmp_table_age_name_wage_complex_pk (key_field INT,AGE INT,field1 VARCHAR,field2
INT,PRIMARY KEY (key_field, AGE, field1));
SQL: create table tmp_table_age_name_wage_complex_pk (key_field INT,AGE
INT,field1 VARCHAR,field2 INT,PRIMARY KEY (key_field, AGE, field1))
No rows affected (0.129 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> insert into
tmp_table_age_name_wage_complex_pk (key_field,AGE,field1,field2) values (11,
null,'John',3);
SQL: insert into tmp_table_age_name_wage_complex_pk
(key_field,AGE,field1,field2) values (11, null,'John',3)
1 row affected (0.121 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> select * from
tmp_table_age_name_wage_complex_pk;
SQL: select * from tmp_table_age_name_wage_complex_pk
IN IncrementalRows 4
+++++
| KEY_FIELD| AGE |
FIELD1 | FIELD2 |
+++++
| 11 | null | John
| 3 |
+++++
1 row selected (0.04 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/>
{code}
The same SQL script with H2 BD got:
{code:java}
create table tmp_table_age_name_wage_complex_pk (key_field INT,AGE INT,field1
VARCHAR,field2 INT,PRIMARY KEY (key_field, AGE, field1));
Update count: 0
(1 ms)
insert into tmp_table_age_name_wage_complex_pk (key_field,AGE,field1,field2)
values (11, null,'John',3);
NULL not allowed for column "AGE"; SQL statement:
insert into tmp_table_age_name_wage_complex_pk (key_field,AGE,field1,field2)
values (11, null,'John',3) [23502-195] 23502/23502
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7479) NOT NULL constraints for complex PK
[
https://issues.apache.org/jira/browse/IGNITE-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Volkov updated IGNITE-7479:
Affects Version/s: 2.2
> NOT NULL constraints for complex PK
> ---
>
> Key: IGNITE-7479
> URL: https://issues.apache.org/jira/browse/IGNITE-7479
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.2
>Reporter: Alex Volkov
>Priority: Minor
>
> According to SQL ANSI 99 spec (11.7 point 5)
> If the < unique specification > specifies PRIMARY KEY, then for each < column
> name > in the explicit or implicit < unique column list > for which NOT NULL
> is not specified, NOT NULL is implicit in the < column definition >.
> But now we have violation:
>
> {code:java}
> 0: jdbc:ignite:thin://127.0.0.1:10800/> create table
> tmp_table_age_name_wage_complex_pk (key_field INT,AGE INT,field1
> VARCHAR,field2 INT,PRIMARY KEY (key_field, AGE, field1));
> SQL: create table tmp_table_age_name_wage_complex_pk (key_field INT,AGE
> INT,field1 VARCHAR,field2 INT,PRIMARY KEY (key_field, AGE, field1))
> No rows affected (0.129 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> insert into
> tmp_table_age_name_wage_complex_pk (key_field,AGE,field1,field2) values (11,
> null,'John',3);
> SQL: insert into tmp_table_age_name_wage_complex_pk
> (key_field,AGE,field1,field2) values (11, null,'John',3)
> 1 row affected (0.121 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> select * from
> tmp_table_age_name_wage_complex_pk;
> SQL: select * from tmp_table_age_name_wage_complex_pk
> IN IncrementalRows 4
> +++++
> | KEY_FIELD| AGE |
> FIELD1 | FIELD2 |
> +++++
> | 11 | null | John
> | 3 |
> +++++
> 1 row selected (0.04 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/>
> {code}
> The same SQL script with H2 BD got:
>
> {code:java}
> create table tmp_table_age_name_wage_complex_pk (key_field INT,AGE INT,field1
> VARCHAR,field2 INT,PRIMARY KEY (key_field, AGE, field1));
> Update count: 0
> (1 ms)
> insert into tmp_table_age_name_wage_complex_pk (key_field,AGE,field1,field2)
> values (11, null,'John',3);
> NULL not allowed for column "AGE"; SQL statement:
> insert into tmp_table_age_name_wage_complex_pk (key_field,AGE,field1,field2)
> values (11, null,'John',3) [23502-195] 23502/23502
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7360) SQL: incorrect date/time values could be inserted
Alex Volkov created IGNITE-7360:
---
Summary: SQL: incorrect date/time values could be inserted
Key: IGNITE-7360
URL: https://issues.apache.org/jira/browse/IGNITE-7360
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.1
Reporter: Alex Volkov
Priority: Minor
According to ansi 99 spec.:
||Keyword||Valid values of datetime fields||
|YEAR|0001 to |
|MONTH|01 to 12|
|DAY|Within the range 1 (one) to 31, but further constrained by the value of
MONTH and YEAR fields, according to the rules for well-formed dates in
the Gregorian calendar.|
|HOUR|00 to 23|
and so on.
But these values could be inserted:
*For DATE data type:*
{code:java}
0: jdbc:ignite:thin://127.0.0.1:10800/> create table tmp_table_date_and_time
(key_field INT PRIMARY KEY,field1 DATE,field2 TIME);
SQL: create table tmp_table_date_and_time (key_field INT PRIMARY KEY,field1
DATE,field2 TIME)
No rows affected (0.028 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> insert into tmp_table_date_and_time
(key_field,field1,field2) values (2, '1-12-09','13:44:56');
SQL: insert into tmp_table_date_and_time (key_field,field1,field2) values (2,
'1-12-09','13:44:56')
1 row affected (0.009 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> select * from tmp_table_date_and_time;
SQL: select * from tmp_table_date_and_time
IN IncrementalRows 3
++++
| KEY_FIELD| FIELD1 |
FIELD2 |
++++
| 2 | Sat Dec 09 00:00:00 MSK 1 | 13:44:56
|
++++
1 row selected (0.007 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> insert into tmp_table_date_and_time
(key_field,field1,field2) values (6, '-2017-12-09','13:44:56');
SQL: insert into tmp_table_date_and_time (key_field,field1,field2) values (6,
'-2017-12-09','13:44:56')
1 row affected (0.011 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> select * from tmp_table_date_and_time;
SQL: select * from tmp_table_date_and_time
IN IncrementalRows 3
++++
| KEY_FIELD| FIELD1 |
FIELD2 |
++++
| 2 | Sat Dec 09 00:00:00 MSK 1 | 13:44:56
|
| 6 | Tue Dec 09 00:00:00 MSK 2018 | 13:44:56
|
++++
2 rows selected (0.016 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/>
{code}
For TIME data type:
{code:java}
0: jdbc:ignite:thin://127.0.0.1:10800/> create table tmp_table_date_and_time
(key_field INT PRIMARY KEY,field1 DATE,field2 TIME);
SQL: create table tmp_table_date_and_time (key_field INT PRIMARY KEY,field1
DATE,field2 TIME)
No rows affected (0.131 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> insert into tmp_table_date_and_time
(key_field,field1,field2) values (3, '2017-12-09','25:44:56');
SQL: insert into tmp_table_date_and_time (key_field,field1,field2) values (3,
'2017-12-09','25:44:56')
1 row affected (0.097 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/> select * from tmp_table_date_and_time;
SQL: select * from tmp_table_date_and_time
IN IncrementalRows 3
++++
| KEY_FIELD| FIELD1 |
FIELD2 |
++++
| 3 | Sat Dec 09 00:00:00 MSK 2017 | 01:44:56
|
++++
1 row selected (0.017 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800/>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages
[ https://issues.apache.org/jira/browse/IGNITE-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299751#comment-16299751 ] Alex Volkov commented on IGNITE-7107: - Tested on CentOS 7. Looks pretty good. > Apache Ignite RPM packages > -- > > Key: IGNITE-7107 > URL: https://issues.apache.org/jira/browse/IGNITE-7107 > Project: Ignite > Issue Type: New Feature > Components: binary >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Labels: important > Fix For: 2.4 > > > Pack apache-ignite into RPM package for distribution through RPM-based Linux > distros (Fedora / CentOS / RHEL, etc.) > Iteration (I): bundle (all-in-one) RPM -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178743#comment-16178743
]
Alex Volkov commented on IGNITE-6457:
-
Yes, that's work. Bug will be closed.
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
>
[jira] [Commented] (IGNITE-6064) Rework control.sh script
[ https://issues.apache.org/jira/browse/IGNITE-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127059#comment-16127059 ] Alex Volkov commented on IGNITE-6064: - Please add help output for both --help and -help keys and example of use in the help output. > Rework control.sh script > > > Key: IGNITE-6064 > URL: https://issues.apache.org/jira/browse/IGNITE-6064 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.0, 2.1 >Reporter: Dmitriy Govorukhin > Fix For: 2.2 > > > Current behavior control.sh is not clear. > 1. control.sh is a confusing name, need more suitable name. > 2. Print help description if incorrect command was entered > 3. Do not print stacktrace if connection fail, add more conveniently message. > 4. Print information about connection, like "Connecting to > [ip-address]:[port] etc." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4377) Cannot find schema for object with compact footer
[
https://issues.apache.org/jira/browse/IGNITE-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106972#comment-16106972
]
Alex Volkov edited comment on IGNITE-4377 at 7/31/17 8:33 AM:
--
Retested for master. No exceptions during reproducer runs.
[~ptupitsyn], could you please recheck from your side?
was (Author: avolkov):
Retested for 1.8.9. No exceptions during reproducer runs.
[~ptupitsyn], could you please recheck from your side?
> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
> Issue Type: Bug
> Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Priority: Critical
>
> When invoking a computation which returns an object from *client* node,
> "Cannot find schema for object with compact footer" exception occurs some
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
> 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)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server",
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client",
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res =
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
> 12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4377) Cannot find schema for object with compact footer
[
https://issues.apache.org/jira/browse/IGNITE-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106972#comment-16106972
]
Alex Volkov commented on IGNITE-4377:
-
Retested for 1.8.9. No exceptions during reproducer runs.
[~ptupitsyn], could you please recheck from your side?
> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
> Issue Type: Bug
> Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Priority: Critical
>
> When invoking a computation which returns an object from *client* node,
> "Cannot find schema for object with compact footer" exception occurs some
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
> 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)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server",
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client",
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res =
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
> 12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5739) JVM crash on node deactivation
[ https://issues.apache.org/jira/browse/IGNITE-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096104#comment-16096104 ] Alex Volkov commented on IGNITE-5739: - Retested for ver. 2.1.0#20170720-sha1:a6ca5c8a. Node deactivation works fine. This scenario was tested: 1. start node with enabled persistent store in config file. 2. activate cluster. 3. check that cluster is activated. 4. deactivate cluster. >From attached log I see that some caches were started. Please provide config >file which was used and clarify the scenario. > JVM crash on node deactivation > -- > > Key: IGNITE-5739 > URL: https://issues.apache.org/jira/browse/IGNITE-5739 > Project: Ignite > Issue Type: Task >Affects Versions: 2.1 >Reporter: Alexey Kuznetsov >Assignee: Semen Boikov > Fix For: 2.1 > > Attachments: hs_err_pid16076.log, ignite-c43368bb.log > > > Start one node (with persistence). > Activate > Deactivate - node crashed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5766) Folder platform/cpp/bin and files inside this folder are missing in 2.1
Alex Volkov created IGNITE-5766: --- Summary: Folder platform/cpp/bin and files inside this folder are missing in 2.1 Key: IGNITE-5766 URL: https://issues.apache.org/jira/browse/IGNITE-5766 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Alex Volkov Fix For: 2.1 I can't find folder platform/cpp/bin and files bin/odbc/ignite-odbc-amd64.msi, bin/odbc/ignite-odbc-x86.msi inside this folder for 2.1. They were there for 2.0. Could you please check were they move or just missing and fix it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5735) NPE during populated data (CacheQueryDdlExample)
[
https://issues.apache.org/jira/browse/IGNITE-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085653#comment-16085653
]
Alex Volkov commented on IGNITE-5735:
-
Works fine on build 3c1749da. No any exceptions on the remote nodes.
> NPE during populated data (CacheQueryDdlExample)
>
>
> Key: IGNITE-5735
> URL: https://issues.apache.org/jira/browse/IGNITE-5735
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Steps for reproduce:
> 1. Start 2 nodes with *examples/config/example-ignite.xml*
> 2. Start *CacheQueryDdlExample*
> Result:
> Om example node:
> {noformat}
> [10:19:17]__
> [10:19:17] / _/ ___/ |/ / _/_ __/ __/
> [10:19:17] _/ // (7 7// / / / / _/
> [10:19:17] /___/\___/_/|_/___/ /_/ /___/
> [10:19:17]
> [10:19:17] ver. 2.1.2#20170711-sha1:2a2c8030
> [10:19:17] 2017 Copyright(C) Apache Software Foundation
> [10:19:17]
> [10:19:17] Ignite documentation: http://ignite.apache.org
> [10:19:17]
> [10:19:17] Quiet mode.
> [10:19:17] ^-- Logging to file
> '/Users/gridgain/Downloads/gridgain-enterprise-fabric-8.1.2/work/log/ignite-9ef688f8.log'
> [10:19:17] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [10:19:17]
> [10:19:17] OS: Mac OS X 10.10.5 x86_64
> [10:19:17] VM information: Java(TM) SE Runtime Environment 1.8.0_45-b14
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.45-b02
> [10:19:17] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [10:19:17] Configured plugins:
> [10:19:17] ^-- GridGain 8.1.2#20170711-sha1:ff30520a
> [10:19:17] ^-- 2017 Copyright(C) GridGain Systems
> [10:19:17]
> [10:19:17] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [10:19:17] Security status [authentication=off, tls/ssl=off]
> [10:19:18] Rolling updates are disabled. GridGain version update will require
> full cluster restart. Consider changing
> 'GridGainConfiguration.rollingUpdatesEnabled' configuration property.
> [2017-07-12 10:19:20,162][ERROR][main][GridEntLicenseProcessor] License
> violation detected:
> ^-- Maximum number of nodes (3/2) is exceeded.
> [2017-07-12 10:19:20,162][ERROR][main][GridEntLicenseProcessor] Contact
> sa...@gridgain.com for further assistance. Make sure to include your license
> ID: 9D50E008-472D-430F-8B2D-CFB8A3894C0D
> [2017-07-12 10:19:20,163][ERROR][main][GridEntLicenseProcessor] License
> grace/burst period - left 1 hour.
> [10:19:20] Performance suggestions for grid (fix if possible)
> [10:19:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [10:19:20] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [10:19:20] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [10:19:20] ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to
> JVM options)
> [10:19:20] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [10:19:20] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [10:19:20] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [10:19:20]
> [10:19:20] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [10:19:20]
> [10:19:20] Ignite node started OK (id=9ef688f8)
> [10:19:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=8, heap=5.6GB]
> >>> Cache query DDL example started.
> >>> Created database objects.
> >>> Populated data.
> {noformat}
> On remote nodes;
> {noformat}
> SEVERE: 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=4 lim=10001 cap=32768],
> reader=DirectMessageReader [state=DirectMessageState [pos=0, stack=[StateItem
> [stream=DirectByteBufferStreamImplV2 [baseOff=140343292566528, arrOff=-1,
> tmpArrOff=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], null, null, null, null, null, null, null, null, null]],
> lastRead=false], ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker
> [super=AbstractNioClientWorker [idx=2, bytesRcvd=117764, bytesSent=5240,
> bytesRcvd0=20086, bytesSent0=56, select=true, super=GridWorker
>
[jira] [Commented] (IGNITE-5537) bin/control.sh add validation of input parameters
[ https://issues.apache.org/jira/browse/IGNITE-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054095#comment-16054095 ] Alex Volkov commented on IGNITE-5537: - In addition: please set port 11211 as default. > bin/control.sh add validation of input parameters > - > > Key: IGNITE-5537 > URL: https://issues.apache.org/jira/browse/IGNITE-5537 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.0 >Reporter: Ilya Suntsov > Fix For: 2.1 > > > I've tried to run *bin/control.sh* without parameters, with parameter > *help*,*-h*. Utility in these cases tried to connect to grid but should just > prints help. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
