[jira] [Created] (IGNITE-15191) Ignite 3 CLI 'node list' command: bad wording
Valentin Kulichenko created IGNITE-15191:
Summary: Ignite 3 CLI 'node list' command: bad wording
Key: IGNITE-15191
URL: https://issues.apache.org/jira/browse/IGNITE-15191
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0.0-alpha2
Reporter: Valentin Kulichenko
The {{node list}} command shows the following output if there is only one node
running:
{noformat}
Currently, there are 1 nodes...
{noformat}
The wording is wrong. We can replace it with a more generic option, similar to
this:
{noformat}
Number of running nodes: 1
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15190) Ignite 3 CLI: if a node start takes longer than the timeout, it does not appear in the list
Valentin Kulichenko created IGNITE-15190:
Summary: Ignite 3 CLI: if a node start takes longer than the
timeout, it does not appear in the list
Key: IGNITE-15190
URL: https://issues.apache.org/jira/browse/IGNITE-15190
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0.0-alpha2
Reporter: Valentin Kulichenko
The {{node start}} command has a timeout, after which it treats the startup
process as failed, and exits, without including the node in the list shown by
the {{node list}} command.
It is possible that the node actually manages to start after the timeout, in
which case the CLI tool and the user are not aware of the running node.
We need to revisit the node management approach in the CLI, so that we can
avoid issues like this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15026) Remove storage of physical page ids in a DurableBackgroundCleanupIndexTreeTask
[
https://issues.apache.org/jira/browse/IGNITE-15026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386404#comment-17386404
]
Ignite TC Bot commented on IGNITE-15026:
{panel:title=Branch: [pull/9207/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9207/head] Base: [master] : New Tests
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=6100112]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testDonotAddTaskOnDeactivateForInMemory - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testExecuteTaskOnDropIdxAfterReActivatedForInMemory -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testExecuteTaskOnDropIdxForInMemory - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testDestroyIndexTreesForInMemory - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testExecuteTaskOnDropIdxAfterReActivated - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testCorrectTaskExecute - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testDestroyIndexTrees - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testTaskNotExecuteIfAbsentCacheGroupOrRootPages - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testExecuteTaskOnDropIdxAfterRestart - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
DropIndexTest.testExecuteTaskOnDropIdx - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
RenameIndexTreeTest.testRenameFromTask - PASSED{color}
... and 1 new tests
{color:#8b}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6100114]]
* {color:#013220}IgnitePdsTestSuite:
DurableBackgroundTasksProcessorSelfTest.testConvertAfterRestoreIfNeeded -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6100144&buildTypeId=IgniteTests24Java8_RunAll]
> Remove storage of physical page ids in a DurableBackgroundCleanupIndexTreeTask
> --
>
> Key: IGNITE-15026
> URL: https://issues.apache.org/jira/browse/IGNITE-15026
> Project: Ignite
> Issue Type: Improvement
> Components: persistence, sql
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DurableBackgroundCleanupIndexTreeTask does one bad thing - it stores page id
> into a logical metastorage record. BUT, there are no guarantees that this
> page exists in current checkpoint state on the storage device.
> Imagine that someone waits for checkpoint, then before the next checkpoint
> they create SQL index, then drop it and end the process with "kill -9".
> There's a chance that something like this could happen by accident.
> Then page id in DurableBackgroundCleanupIndexTreeTask will either point to a
> nonexistent page (trace 1) or to the existing page that has nothing to do
> with meta tree (trace 2).
> {noformat}
> java.lang.ArrayIndexOutOfBoundsException: 4937
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.getStore(FilePageStoreManager.java:1085)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageReadWriteManagerImpl.read(PageReadWriteManagerImpl.java:65)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:510)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:871)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:697)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:686)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:185)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.acquirePage(BPlusTree.java:6061)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.destroyDownPages(BPlusTree.java:2607)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.destroy(BPlusTree.java:2555)
> at
> org.apache.ignite.internal.processors.query.h2.DurableBackgroundCleanupIndexTreeTask.execute(DurableBackgroundCleanupIndexTreeTask.java:231)
> at
>
[jira] [Updated] (IGNITE-15189) Document new SQL engine based on Calcite
[ https://issues.apache.org/jira/browse/IGNITE-15189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15189: --- Labels: documentation (was: docuentation) > Document new SQL engine based on Calcite > > > Key: IGNITE-15189 > URL: https://issues.apache.org/jira/browse/IGNITE-15189 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Yury Gerzhedovich >Priority: Major > Labels: documentation > > We need to begin document of the new SQL engine. Let's start to form Contents. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14970) Implement basic java thin client for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386260#comment-17386260 ] Pavel Tupitsyn commented on IGNITE-14970: - Merged to main: 0448b1d679beb32235cc200f26b5d6166590c7ab > Implement basic java thin client for 3.0 > > > Key: IGNITE-14970 > URL: https://issues.apache.org/jira/browse/IGNITE-14970 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 12h 50m > Remaining Estimate: 0h > > We need to implement basic version of java thin client for 3.0. It should be > able to connect to the cluster and send some simple requests (maybe put and > get). > For this we need to implement connection point on the server side and basic > connection logic on client side. > This ticket is not about implementing any public API, it's only to create > thin client stub that can be used to implement different APIs on top of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15189) Document new SQL engine based on Calcite
Yury Gerzhedovich created IGNITE-15189: -- Summary: Document new SQL engine based on Calcite Key: IGNITE-15189 URL: https://issues.apache.org/jira/browse/IGNITE-15189 Project: Ignite Issue Type: Task Components: documentation Reporter: Yury Gerzhedovich We need to begin document of the new SQL engine. Let's start to form Contents. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14924) Implement HoconConfigurationSource
[ https://issues.apache.org/jira/browse/IGNITE-14924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386238#comment-17386238 ] Semyon Danilov commented on IGNITE-14924: - Looks good to me! > Implement HoconConfigurationSource > -- > > Key: IGNITE-14924 > URL: https://issues.apache.org/jira/browse/IGNITE-14924 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Ivan Bessonov >Priority: Major > Labels: iep-55, ignite-3 > Time Spent: 1h 10m > Remaining Estimate: 0h > > According to > [IEP-55|https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration] > we must support HOCON format as the main format for configuration files. But > now we support only json configs by our configuration framework and forced to > convert hocon to json before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15188) JDBC driver for 3.0: Implements DatabaseMetadata
Taras Ledkov created IGNITE-15188:
-
Summary: JDBC driver for 3.0: Implements DatabaseMetadata
Key: IGNITE-15188
URL: https://issues.apache.org/jira/browse/IGNITE-15188
Project: Ignite
Issue Type: Improvement
Components: jdbc
Reporter: Taras Ledkov
Implements DatabaseMetadata.
Extends
[IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0]
with new commands.
Take a look at the common approach for the metadata / view at the Ignite 2.x:
{{SystemViewRowAttributeWalker}}, {{SchemaManager}}. Looks like we should use
best practice from Ignite 2.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15187) JDBC driver for 3.0: Implements ResultSetMetadata
Taras Ledkov created IGNITE-15187: - Summary: JDBC driver for 3.0: Implements ResultSetMetadata Key: IGNITE-15187 URL: https://issues.apache.org/jira/browse/IGNITE-15187 Project: Ignite Issue Type: Improvement Components: jdbc Reporter: Taras Ledkov Implements ResultSetMetadata. Extends [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0] with new commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15186) JDBC driver for 3.0: Implements Statements
[ https://issues.apache.org/jira/browse/IGNITE-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-15186: -- Issue Type: Improvement (was: Bug) > JDBC driver for 3.0: Implements Statements > -- > > Key: IGNITE-15186 > URL: https://issues.apache.org/jira/browse/IGNITE-15186 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Taras Ledkov >Priority: Major > > Implements Statement, PreparedStatement and ResultSet. > Extends > [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0] > with new commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15185) JDBC driver for 3.0: Implements Driver & Connection
[
https://issues.apache.org/jira/browse/IGNITE-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15185:
--
Issue Type: Improvement (was: New Feature)
> JDBC driver for 3.0: Implements Driver & Connection
> ---
>
> Key: IGNITE-15185
> URL: https://issues.apache.org/jira/browse/IGNITE-15185
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Reporter: Taras Ledkov
>Priority: Major
>
> Implements JDBC driver & Connection according with
> [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0].
> See more at Ignite 2.x:
> - driver implementation: {{IgniteJdbcThinDriver}}
> - connection properties: {{ConnectionPropertiesImpl}}
> Create ticket to documentation JDBC connection string & connection properties
> (for now it will only be network properties).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15186) JDBC driver for 3.0: Implements Statements
Taras Ledkov created IGNITE-15186: - Summary: JDBC driver for 3.0: Implements Statements Key: IGNITE-15186 URL: https://issues.apache.org/jira/browse/IGNITE-15186 Project: Ignite Issue Type: Bug Components: jdbc Reporter: Taras Ledkov Implements Statement, PreparedStatement and ResultSet. Extends [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0] with new commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14858) Calcite integration. New Thin JDBC driver for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14858: -- Component/s: jdbc > Calcite integration. New Thin JDBC driver for 3.0 > - > > Key: IGNITE-14858 > URL: https://issues.apache.org/jira/browse/IGNITE-14858 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Yury Gerzhedovich >Priority: Major > Labels: calcite2-required, calcite3-required > > Need to implement new JDBC driver Calcite for Ignite 3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15185) JDBC driver for 3.0: Implements Driver & Connection
[
https://issues.apache.org/jira/browse/IGNITE-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15185:
--
Component/s: (was: sql)
jdbc
> JDBC driver for 3.0: Implements Driver & Connection
> ---
>
> Key: IGNITE-15185
> URL: https://issues.apache.org/jira/browse/IGNITE-15185
> Project: Ignite
> Issue Type: New Feature
> Components: jdbc
>Reporter: Taras Ledkov
>Priority: Major
>
> Implements JDBC driver & Connection according with
> [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0].
> See more at Ignite 2.x:
> - driver implementation: {{IgniteJdbcThinDriver}}
> - connection properties: {{ConnectionPropertiesImpl}}
> Create ticket to documentation JDBC connection string & connection properties
> (for now it will only be network properties).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15185) JDBC driver for 3.0: Implements Driver & Connection
[
https://issues.apache.org/jira/browse/IGNITE-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15185:
--
Issue Type: New Feature (was: Bug)
> JDBC driver for 3.0: Implements Driver & Connection
> ---
>
> Key: IGNITE-15185
> URL: https://issues.apache.org/jira/browse/IGNITE-15185
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Implements JDBC driver & Connection according with
> [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0].
> See more at Ignite 2.x:
> - driver implementation: {{IgniteJdbcThinDriver}}
> - connection properties: {{ConnectionPropertiesImpl}}
> Create ticket to documentation JDBC connection string & connection properties
> (for now it will only be network properties).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15185) JDBC driver for 3.0: Implements Driver & Connection
Taras Ledkov created IGNITE-15185:
-
Summary: JDBC driver for 3.0: Implements Driver & Connection
Key: IGNITE-15185
URL: https://issues.apache.org/jira/browse/IGNITE-15185
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Taras Ledkov
Implements JDBC driver & Connection according with
[IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0].
See more at Ignite 2.x:
- driver implementation: {{IgniteJdbcThinDriver}}
- connection properties: {{ConnectionPropertiesImpl}}
Create ticket to documentation JDBC connection string & connection properties
(for now it will only be network properties).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15184) Ignite server cannot reconnect client: Close incoming connection, unknown node
Alexey Kukushkin created IGNITE-15184:
-
Summary: Ignite server cannot reconnect client: Close incoming
connection, unknown node
Key: IGNITE-15184
URL: https://issues.apache.org/jira/browse/IGNITE-15184
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.9.1, 2.7
Environment: Reproduced on AI 2.7 and 2.9.1
Client OS: Windows Server 2012 R2 6.3 amd64
Server OS: Linux 3.10.0-1062.9.1.el7.x86_64 amd64
See the Ignite configuration in the client and server logs in the Description
Reporter: Alexey Kukushkin
Ignite client nodes eventually lose connectivity with the cluster and never
reconnect. The below logs show the server rejects the client reconnection with
a warning "{color:#de350b}Close incoming connection, unknown node{color}".
It is possible the problem was caused by a severely degraded network
throughput. However, the server should keep the client session for
"clientFailureDetectionTimeout" (10 seconds by default) and the client should
keep trying to re-connect automatically during that time. Instead, we see the
server immediately says "Close incoming connection, unknown node" and the
client never re-connects.
Ignite should survive temporary network problems (with duration less than
clientFailureDetectionTimeout).
See the server and client errors and configurations in the logs below.
h3. Server
{{[05:33:00,946][INFO][main][IgniteKernal%StaticGrid] IgniteConfiguration
[igniteInstanceName=StaticGrid, pubPoolSize=16, svcPoolSize=16,
callbackPoolSize=16, stripedPoolSize=16, sysPoolSize=16, mgmtPoolSize=4,
dataStreamerPoolSize=16, utilityCachePoolSize=16,
utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=16,
buildIdxPoolSize=4, igniteHome=/ignite/apache-ignite-2.9.1-bin,
igniteWorkDir=/ignite/apache-ignite-2.9.1-bin/work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@6f94fa3e,
nodeId=e5845e09-df08-4b85-b633-f14dec8f8106, marsh=BinaryMarshaller [],
marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000,
netCompressionLevel=1, sndRetryDelay=1000, sndRetryCnt=3,
metricsHistSize=1, metricsUpdateFreq=2000,
metricsExpTime=9223372036854775807, discoSpi=TcpDiscoverySpi [addrRslvr=null,
sockTimeout=0, ackTimeout=0, marsh=null, reconCnt=10, reconDelay=2000,
maxAckTimeout=60, soLinger=0, forceSrvMode=false,
clientReconnectDisabled=false, internalLsnr=null,
skipAddrsRandomization=false], segPlc=RESTART_JVM, segResolveAttempts=10,
waitForSegOnStart=true, allResolversPassReq=true, segChkFreq=2,
commSpi=TcpCommunicationSpi [connectGate=null,
connPlc=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$FirstConnectionPolicy@62ddbd7e,
chConnPlc=null, enableForcibleNodeKill=false, enableTroubleshootingLog=false,
locAddr=null, locHost=null, locPort=51605, locPortRange=100, shmemPort=-1,
directBuf=true, directSndBuf=false, idleConnTimeout=60, connTimeout=5000,
maxConnTimeout=60, reconCnt=10, sockSndBuf=32768, sockRcvBuf=32768,
msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null, shmemSrv=null,
usePairedConnections=false, connectionsPerNode=1, tcpNoDelay=true,
filterReachableAddresses=false, ackSndThreshold=32, unackedMsgsBufSize=0,
sockWriteTimeout=2000, boundTcpPort=-1, boundTcpShmemPort=-1, selectorsCnt=8,
selectorSpins=0, forceClientToSrvConnections=false, addrRslvr=null,
ctxInitLatch=java.util.concurrent.CountDownLatch@74e52ef6[Count = 1],
stopping=false, metricsLsnr=null, connectionRequestor=null],
evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@6ed3ccb2,
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [],
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@3c9754d8,
addrRslvr=null,
encryptionSpi=org.apache.ignite.spi.encryption.noop.NoopEncryptionSpi@3bf7ca37,
tracingSpi=org.apache.ignite.spi.tracing.NoopTracingSpi@79079097,
clientMode=false, rebalanceThreadPoolSize=4, rebalanceTimeout=1,
rebalanceBatchesPrefetchCnt=3, rebalanceThrottle=0, rebalanceBatchSize=524288,
txCfg=TransactionConfiguration [txSerEnabled=false,
dfltIsolation=REPEATABLE_READ, dfltConcurrency=PESSIMISTIC, dfltTxTimeout=0,
txTimeoutOnPartitionMapExchange=0, deadlockTimeout=1,
pessimisticTxLogSize=0, pessimisticTxLogLinger=1, tmLookupClsName=null,
txManagerFactory=null, useJtaSync=false], cacheSanityCheckEnabled=true,
discoStartupDelay=6, deployMode=SHARED, p2pMissedCacheSize=100,
locHost=10.212.120.66, timeSrvPortBase=31100, timeSrvPortRange=100,
failureDetectionTimeout=12, sysWorkerBlockedTimeout=null,
clientFailureDetectionTimeout=12, metricsLogFreq=6,
connectorCfg=ConnectorConfiguration [jettyPath=null, host=null, port=11211,
noDelay=true, directBuf=false, sndBufSize=32768, rcvBufSize=32768,
idleQryCurTimeout=60, idleQryCurCheckFreq=6, sndQueueLimit=0,
selectorCnt=4, idleTimeout=7000, sslEnabled
[jira] [Commented] (IGNITE-14970) Implement basic java thin client for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386161#comment-17386161 ] Andrey Mashenkov commented on IGNITE-14970: --- [~ptupitsyn], LGTM. Let's proceed with merging it. > Implement basic java thin client for 3.0 > > > Key: IGNITE-14970 > URL: https://issues.apache.org/jira/browse/IGNITE-14970 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 11h 50m > Remaining Estimate: 0h > > We need to implement basic version of java thin client for 3.0. It should be > able to connect to the cluster and send some simple requests (maybe put and > get). > For this we need to implement connection point on the server side and basic > connection logic on client side. > This ticket is not about implementing any public API, it's only to create > thin client stub that can be used to implement different APIs on top of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15166) Support renaming in named list configuration elements
[
https://issues.apache.org/jira/browse/IGNITE-15166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov reassigned IGNITE-15166:
--
Assignee: Ivan Bessonov
> Support renaming in named list configuration elements
> -
>
> Key: IGNITE-15166
> URL: https://issues.apache.org/jira/browse/IGNITE-15166
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha2
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: iep-55, ignite-3
>
> h3. Motivation
> Current NamedListChange API does not allow you to perform rename operation.
> Best that you can do is to manually copy the required element and then delete
> the original. This is bad for several reasons:
> * inconvenient both in Java API and CLI tool;
> * results in "onDelete" and "onCreate" events, which is probably not what
> people want.
> There must be a way to rename elements in Java API at least so that "ALTER
> ..." DDL command could be properly implemented.
> h3. Java API
> {{NamedListChange}} is a right place to add "rename" method. It should have
> two parameters and following restrictions:
> * "old" and "new" names are not null;
> * element with "old" name must exist;
> * element with "new" name must not exist.
> New method must be added {{to ConfigurationNamedListListener}}, named
> "onRename". It should have "onUpdate" semantics, but with two new parameters:
> "oldKey" and "newKey". Names are a subject to change.
> h3. CLI
> -This is a little less obvious since HOCON/JSON describe data, not
> operations. We already have specific syntax for "delete" operation. I suggest
> making "rename" look similar:-
> {code:java}
> root.namedList {
> oldName = newName
> }{code}
> -In short, now we can assign 3 things to the element:-
> * -regular composite object with its inner values;-
> * -"null" for deletion;-
> * -"String" for renaming.-
> HOCON/JSON format will have no alterations for this feature. DDL commands are
> to be used for these operations instead.
> h3. Implementation hints
> This will be similar to how we store ordering of named list elements. But
> this time we have to assign each element a unique identifier. This can be a
> String or a number. Laziest solution is to use UUID with hyphens removed from
> it. That'll do it.
> NamedListNode object will store these ids. In short, following algorithms
> will have to be altered:
> * conversion of update tree to the flat map - this one should be easy;
> * applying the flat map to the tree - a bit trickier. Matching from ids to
> keys will be required, we have to make sure that it won't cost too much;
> * matching old list with a new one to properly invoke listeners - should be
> partially solved by the code from the issue above, but still, might be tricky
> as well.
> -HOCON / JSON "parsers" will have to be altered as well to support "rename"
> operation. That should be easy.-
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15178) Add validation of MessageGroup IDs
[
https://issues.apache.org/jira/browse/IGNITE-15178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386149#comment-17386149
]
Ivan Bessonov commented on IGNITE-15178:
Looks good, thank you for the contribution. Merged to main branch.
> Add validation of MessageGroup IDs
> --
>
> Key: IGNITE-15178
> URL: https://issues.apache.org/jira/browse/IGNITE-15178
> Project: Ignite
> Issue Type: Task
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-67, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently message groups IDs are simply {{short}} values that are manually
> assigned to every module. This can lead to ID clashes which will lead to
> message handlers being invoked unexpectedly.
> We should find a way to validate group IDs across all modules. One way is to
> check that message group classes are the same when a handler is registered in
> the {{MessagingService}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15178) Add validation of MessageGroup IDs
[
https://issues.apache.org/jira/browse/IGNITE-15178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15178:
---
Labels: iep-67 ignite-3 (was: ignite-3)
> Add validation of MessageGroup IDs
> --
>
> Key: IGNITE-15178
> URL: https://issues.apache.org/jira/browse/IGNITE-15178
> Project: Ignite
> Issue Type: Task
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-67, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently message groups IDs are simply {{short}} values that are manually
> assigned to every module. This can lead to ID clashes which will lead to
> message handlers being invoked unexpectedly.
> We should find a way to validate group IDs across all modules. One way is to
> check that message group classes are the same when a handler is registered in
> the {{MessagingService}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15178) Add validation of MessageGroup IDs
[
https://issues.apache.org/jira/browse/IGNITE-15178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15178:
---
Labels: ignite-3 (was: )
> Add validation of MessageGroup IDs
> --
>
> Key: IGNITE-15178
> URL: https://issues.apache.org/jira/browse/IGNITE-15178
> Project: Ignite
> Issue Type: Task
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently message groups IDs are simply {{short}} values that are manually
> assigned to every module. This can lead to ID clashes which will lead to
> message handlers being invoked unexpectedly.
> We should find a way to validate group IDs across all modules. One way is to
> check that message group classes are the same when a handler is registered in
> the {{MessagingService}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15183) Add thin clients thread pool monitoring
Aleksey Plekhanov created IGNITE-15183:
--
Summary: Add thin clients thread pool monitoring
Key: IGNITE-15183
URL: https://issues.apache.org/jira/browse/IGNITE-15183
Project: Ignite
Issue Type: Improvement
Reporter: Aleksey Plekhanov
Currently, JMX bean is not created for thin clients thread pool
("client-connector"), so monitoring of this pool is not possible. JMX bean
registration for this pool should be added.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15178) Add validation of MessageGroup IDs
[
https://issues.apache.org/jira/browse/IGNITE-15178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-15178:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Add validation of MessageGroup IDs
> --
>
> Key: IGNITE-15178
> URL: https://issues.apache.org/jira/browse/IGNITE-15178
> Project: Ignite
> Issue Type: Task
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently message groups IDs are simply {{short}} values that are manually
> assigned to every module. This can lead to ID clashes which will lead to
> message handlers being invoked unexpectedly.
> We should find a way to validate group IDs across all modules. One way is to
> check that message group classes are the same when a handler is registered in
> the {{MessagingService}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15149) Fix javadoc in Configuration module.
[
https://issues.apache.org/jira/browse/IGNITE-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15149:
---
Reviewer: Aleksandr Polovtcev (was: Andrey Mashenkov)
> Fix javadoc in Configuration module.
>
>
> Key: IGNITE-15149
> URL: https://issues.apache.org/jira/browse/IGNITE-15149
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Let's fix Javadoc styles regarding the policy.
> Startpoint is to remove modules from excludes
> {noformat}
> ./check-rules/checkstyle-disabled-modules.xml
> {noformat}
> and run
> {code:java}
> mvn clean checkstyle:checkstyle-aggregate -P javadoc-public-api
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13744) Calcite. Use TableSpool for IgniteNestedLoopJoin
[
https://issues.apache.org/jira/browse/IGNITE-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386098#comment-17386098
]
Stanilovsky Evgeny commented on IGNITE-13744:
-
[~korlov] i rewrite PR take into account you *Spool serialization suggestions,
i also fix (Table|Index)Scan costs, seems in ai master it more efficient.
> Calcite. Use TableSpool for IgniteNestedLoopJoin
>
>
> Key: IGNITE-13744
> URL: https://issues.apache.org/jira/browse/IGNITE-13744
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Stanilovsky Evgeny
>Priority: Minor
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Now {{NestedLoopJoinNode}} uses internal buffer to save all rows of the right
> input.
> We have to do refactoring {{IgniteNestedLoopJoin}} to use rewind of the right
> input and use TableSpool for not rewindable inputs.
> This refactoring separates implementation the join logic from materialization
> of the right input if it is needed. In the future we can use disk offload for
> TableSpool etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15168) Investigate local dependency purge for always clean build
[ https://issues.apache.org/jira/browse/IGNITE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386096#comment-17386096 ] Peter Ivanov edited comment on IGNITE-15168 at 7/23/21, 8:56 AM: - Visa: https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6099708 was (Author: vveider): Tests > Investigate local dependency purge for always clean build > - > > Key: IGNITE-15168 > URL: https://issues.apache.org/jira/browse/IGNITE-15168 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > This plugin > [https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html] > can remove internal module dependency artifacts from local repository in > order to use local resolution scope each time the project is being built, > thus, providing clean build without additional artifacts resolution or > downloading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15168) Investigate local dependency purge for always clean build
[ https://issues.apache.org/jira/browse/IGNITE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386096#comment-17386096 ] Peter Ivanov commented on IGNITE-15168: --- Tests > Investigate local dependency purge for always clean build > - > > Key: IGNITE-15168 > URL: https://issues.apache.org/jira/browse/IGNITE-15168 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > This plugin > [https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html] > can remove internal module dependency artifacts from local repository in > order to use local resolution scope each time the project is being built, > thus, providing clean build without additional artifacts resolution or > downloading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15159) Manual encrypted snapshots.
[
https://issues.apache.org/jira/browse/IGNITE-15159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386093#comment-17386093
]
Ignite TC Bot commented on IGNITE-15159:
{panel:title=Branch: [pull/9269/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9269/head] Base: [master] : New Tests
(128)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=6099151]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotRestoreWithIndexingTest.testClusterSnapshotRestoreOnBiggerTopology[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotRestoreWithIndexingTest.testBasicClusterSnapshotRestore[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotCheckWithIndexesTest.testClusterSnapshotCheckWithIndexes[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotCheckWithIndexesTest.testClusterSnapshotCheckWithNodeFilter[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotRestoreWithIndexingTest.testBasicClusterSnapshotRestoreWithMetadata[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotCheckWithIndexesTest.testClusterSnapshotCheckEmptyCache[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotWithIndexesTest.testClusterSnapshotConsistentConfig[Encryption=true]
- PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotWithIndexesTest.testClusterSnapshotWithIndexes[Encryption=true]
- PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotWithIndexesTest.testClusterSnapshotConsistentConfig[Encryption=false]
- PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgniteClusterSnapshotWithIndexesTest.testClusterSnapshotWithIndexes[Encryption=false]
- PASSED{color}
{color:#8b}Basic 3{color} [[tests
118|https://ci.ignite.apache.org/viewLog.html?buildId=6099207]]
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testClusterSnapshotIncorrectNameFails[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testClusterSnapshotFromClient[Encryption=true] -
PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testClusterSnapshotFinishedTryCancel[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testClusterSnapshotInMemoryFail[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testClusterSnapshotWithSharedCacheGroup[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testConsistentClusterSnapshotLoadNewTopology[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testSnapshotPrimaryBackupsTheSame[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
EncryptedSnapshotTest.testSnapshotTaskIsBlockedWithoutMetastore[Encryption is
enabled.] - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testRejectCacheStopDuringClusterSnapshot[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotRestoreSelfTest.testRestoreAllGroupsWithoutConsistentId[Encryption
is disabled] - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotSelfTest.testClusterSnapshotInProgressCancelled[Encryption=true]
- PASSED{color}
... and 107 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6099183&buildTypeId=IgniteTests24Java8_RunAll]
> Manual encrypted snapshots.
> ---
>
> Key: IGNITE-15159
> URL: https://issues.apache.org/jira/browse/IGNITE-15159
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As first implementation, let's introduce manually replaceable encrypted
> snapshots.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15149) Fix javadoc in Configuration module.
[
https://issues.apache.org/jira/browse/IGNITE-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386082#comment-17386082
]
Aleksandr Polovtcev commented on IGNITE-15149:
--
LGTM!
> Fix javadoc in Configuration module.
>
>
> Key: IGNITE-15149
> URL: https://issues.apache.org/jira/browse/IGNITE-15149
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Let's fix Javadoc styles regarding the policy.
> Startpoint is to remove modules from excludes
> {noformat}
> ./check-rules/checkstyle-disabled-modules.xml
> {noformat}
> and run
> {code:java}
> mvn clean checkstyle:checkstyle-aggregate -P javadoc-public-api
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14970) Implement basic java thin client for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386067#comment-17386067 ] Igor Sapego commented on IGNITE-14970: -- [~ptupitsyn] looks good now > Implement basic java thin client for 3.0 > > > Key: IGNITE-14970 > URL: https://issues.apache.org/jira/browse/IGNITE-14970 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 11h 10m > Remaining Estimate: 0h > > We need to implement basic version of java thin client for 3.0. It should be > able to connect to the cluster and send some simple requests (maybe put and > get). > For this we need to implement connection point on the server side and basic > connection logic on client side. > This ticket is not about implementing any public API, it's only to create > thin client stub that can be used to implement different APIs on top of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
