[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372509#comment-16372509
]
ruchir choudhry commented on IGNITE-7759:
-
Hello Roman,
Can i pick this ticket ,
Regards,
Ruchir
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7756) Streamer fails if IgniteUuid is indexed
[
https://issues.apache.org/jira/browse/IGNITE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372494#comment-16372494
]
Nikolay Izhikov edited comment on IGNITE-7756 at 2/22/18 7:11 AM:
--
[~avinogradov] Can you, please, take a look at my changes?
Upsource - https://reviews.ignite.apache.org/ignite/review/IGNT-CR-499
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1105845&;
was (Author: nizhikov):
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1105845&;
> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed
> [node=57961924-82ec-4d56-81eb-1a4109a0]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial
> value for cache entry
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid,
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1343)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1207)
> at
> org.apache.ignite.internal.processors.cache.I
[jira] [Updated] (IGNITE-5975) [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure
[ https://issues.apache.org/jira/browse/IGNITE-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5975: --- Fix Version/s: 2.5 > [Test Failed] > GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure > --- > > Key: IGNITE-5975 > URL: https://issues.apache.org/jira/browse/IGNITE-5975 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.5 > > > Fails locally. > Example of failing - > http://ci.ignite.apache.org/viewLog.html?buildId=758964&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteDataStrucutures#testNameId-2988875689386264427. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
[
https://issues.apache.org/jira/browse/IGNITE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372502#comment-16372502
]
Nikolay Izhikov commented on IGNITE-6005:
-
[~agura], [~dpavlov]
TC run - https://ci.ignite.apache.org/viewLog.html?buildId=1105744
> [Test failed]
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteDataStrucutures
> Typical problem is
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous
> operation permit (thread got interrupted).
> at
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
>
[jira] [Commented] (IGNITE-7756) Streamer fails if IgniteUuid is indexed
[
https://issues.apache.org/jira/browse/IGNITE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372494#comment-16372494
]
Nikolay Izhikov commented on IGNITE-7756:
-
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1105845&;
> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed
> [node=57961924-82ec-4d56-81eb-1a4109a0]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial
> value for cache entry
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid,
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1343)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1207)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:345)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3527)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.ini
[jira] [Commented] (IGNITE-7462) Web console: remove invoking of depricated methods from code generation
[ https://issues.apache.org/jira/browse/IGNITE-7462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372398#comment-16372398 ] Vasiliy Sisko commented on IGNITE-7462: --- Configuration generation actualized. Fixed: Zookeeper Discovery SPI - generation of Base path field. S3 discovery SPI - missed fields. S3 checkpoint SPI - missed fieds, client configuration - missed fields, fixed generation of retry policies. Cluster communication - removed Discovery startup delay for 2.3.0 version Cluster data storage - missed Checkpoint write order. > Web console: remove invoking of depricated methods from code generation > --- > > Key: IGNITE-7462 > URL: https://issues.apache.org/jira/browse/IGNITE-7462 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: 2.5 > > > e.g. Warning:(2867, 13) java: setLongQueryWarningTimeout(long) in > org.apache.ignite.configuration.CacheConfiguration has been deprecated -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7784) Remove unnessary dependencies from WC front-end
Alexander Kalinin created IGNITE-7784: - Summary: Remove unnessary dependencies from WC front-end Key: IGNITE-7784 URL: https://issues.apache.org/jira/browse/IGNITE-7784 Project: Ignite Issue Type: Task Reporter: Alexander Kalinin Assignee: Alexander Kalinin There are some lageacy modules in packages.json (Like phantom.js). These should be deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7320) Multilevel header in admin panel looks wierd in Safari and Edge
[ https://issues.apache.org/jira/browse/IGNITE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-7320: - Fix Version/s: 2.5 > Multilevel header in admin panel looks wierd in Safari and Edge > --- > > Key: IGNITE-7320 > URL: https://issues.apache.org/jira/browse/IGNITE-7320 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.5 > > Attachments: Lk1YqS (1).jpg > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7777) Thin Client lib: Node.js
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372306#comment-16372306 ] Dmitriy Setrakyan commented on IGNITE-: --- Great addition to the project! I have a question about SQL queries. What is the return value of the query? Is it going to be some time of a cursor? Will it be paginated? > Thin Client lib: Node.js > > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Alexey Kosenchuk >Priority: Major > > Implement Thin (lightweight) Client lib in Node.js programming language for > Ignite Binary Client Protocol > https://apacheignite.readme.io/docs/binary-client-protocol > Examples of other Thin Clients: > .net > https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client > java > https://github.com/gridgain/apache-ignite/tree/ignite-7421/modules/thinclient > Scope of work > - > Functionality: > Support all operations of the Ignite Binary Client Protocol 2.4. > Support name/password authentication - TBD (not in the protocol yet). > Support optional SSL/TLS communication - TBD (not in the protocol yet). > Support optional failover/reconnect - TBD. > Minimal Node.js version - TBD. > Synch ops emulation - callbacks, or Promises, or asynch/await - TBD. > Examples: > Cover all basic features - Key-value API, SQL, Scan queries, Cluster > configuration/management, Authentication, SSL/TLS. > Tests: > Jasmine tests for all API methods and all basic features. > Simple Jasmine tests to start examples. > How to emulate node failure to test failover/reconnect? - TBD. > Docs: > Auto-generated API spec from comments. JSdoc, or javadoc, or what? - TBD. > Readme for the lib. > Simple instruction to setup/run examples. > Simple instruction to setup/run Jasmine tests. > Docs format - .md in the repo, or dash.readme.io ? - TBD. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7415) Ability to disable WAL (Documentation)
[ https://issues.apache.org/jira/browse/IGNITE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372170#comment-16372170 ] Prachi Garg edited comment on IGNITE-7415 at 2/21/18 11:09 PM: --- [~dmagda], Please review: * For SQL, see Command and parameters section - [https://apacheignite-sql.readme.io/v2.3/docs/alter-table_24_hidden] * WAL documentation - [https://apacheignite.readme.io/v2.3/docs/write-ahead-log-24#section-enabledisable-wal] * "Performance Improvement" callout at the end of the page - [https://apacheignite.readme.io/v2.3/docs/data-loading-24] was (Author: pgarg): [~dmagda], Please review: * For SQL, Command and parameters section - [https://apacheignite-sql.readme.io/v2.3/docs/alter-table_24_hidden] * WAL documentation - https://apacheignite.readme.io/v2.3/docs/write-ahead-log-24#section-enabledisable-wal * "Performance Improvement" callout at the end of the page - https://apacheignite.readme.io/v2.3/docs/data-loading-24 > Ability to disable WAL (Documentation) > -- > > Key: IGNITE-7415 > URL: https://issues.apache.org/jira/browse/IGNITE-7415 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Anton Vinogradov >Assignee: Denis Magda >Priority: Critical > Fix For: 2.4 > > > Need to update > [https://apacheignite.readme.io/docs/write-ahead-log#section-wal-modes] > [https://apacheignite.readme.io/docs/data-loading] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7415) Ability to disable WAL (Documentation)
[ https://issues.apache.org/jira/browse/IGNITE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-7415: --- Assignee: Denis Magda (was: Prachi Garg) > Ability to disable WAL (Documentation) > -- > > Key: IGNITE-7415 > URL: https://issues.apache.org/jira/browse/IGNITE-7415 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Anton Vinogradov >Assignee: Denis Magda >Priority: Critical > Fix For: 2.4 > > > Need to update > [https://apacheignite.readme.io/docs/write-ahead-log#section-wal-modes] > [https://apacheignite.readme.io/docs/data-loading] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7783) Thin Client lib: PHP
Alexey Kosenchuk created IGNITE-7783: Summary: Thin Client lib: PHP Key: IGNITE-7783 URL: https://issues.apache.org/jira/browse/IGNITE-7783 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Alexey Kosenchuk Assignee: Alexey Kosenchuk Implement Thin (lightweight) Client lib in PHP programming language for Ignite Binary Client Protocol https://apacheignite.readme.io/docs/binary-client-protocol -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7782) Thin Client lib: Python
Alexey Kosenchuk created IGNITE-7782: Summary: Thin Client lib: Python Key: IGNITE-7782 URL: https://issues.apache.org/jira/browse/IGNITE-7782 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Alexey Kosenchuk Assignee: Alexey Kosenchuk Implement Thin (lightweight) Client lib in Python programming language for Ignite Binary Client Protocol https://apacheignite.readme.io/docs/binary-client-protocol -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7688) DDL does not work properly on sql queries.
[ https://issues.apache.org/jira/browse/IGNITE-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-7688: Labels: persistant persistence persistence.xml sql (was: persistant persistence persistence.xml) > DDL does not work properly on sql queries. > -- > > Key: IGNITE-7688 > URL: https://issues.apache.org/jira/browse/IGNITE-7688 > Project: Ignite > Issue Type: Bug > Components: 2.3 >Affects Versions: 2.3 > Environment: we have 5 node running on Ubuntu 16.04(VM). we > donwloaded binary dist. from download page. >Reporter: Muratcan TUKSAL >Priority: Critical > Labels: persistant, persistence, persistence.xml, sql > Fix For: 2.5 > > Attachments: buggy-config.xml > > > * start ignite cluster persistent enabled mode (tried on 5 node) > * activate cluster via ignitevisor > * Create a table through jdbc > * kill all nodes > * start all nodes again > * activate cluster via ignitevisor > * drop that specific table > * deactivate cluster(doesnt matter via top -deactivate or kill all nodes) > * activate cluster > * dropped table still there with no data -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7781) JMX beans documentation
[ https://issues.apache.org/jira/browse/IGNITE-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-7781: Assignee: Prachi Garg > JMX beans documentation > --- > > Key: IGNITE-7781 > URL: https://issues.apache.org/jira/browse/IGNITE-7781 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Prachi Garg >Priority: Major > Labels: documentation, jmx > Fix For: 2.5 > > Attachments: MXBeansJavaDoc.zip > > > There are about 30 JMX beans implemented in Ignite, but there is no > documentation for most of these beans, except memory metrics and brief > overview of cache metrics. > Folowing MBeans/MXBeans can be documented: > ||MBeans group||Interface||Path||Comment|| > |Eviction > metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, > org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, > org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, > org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For > each cache, if eviction for cache is configured| > |Cache group > metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache > groups".|For each group| > |Cache > metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, > > org.apacheCacheLocalMetricsMXBeanImpl|For > each cache| > |Cluster > metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, > org.apache...Kernal.ClusterMetricsMXBeanImpl| > |Data region (memory) > metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For > each data region| > |Data storage > metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent > Store".DataStorageMetrics| > |Instance > information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| > |Ignition > state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| > |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, > org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread > Pools".|For each executor| > |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, > org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, > org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, > org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, > org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, > org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, > org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, > org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, > org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, > org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, > org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, > org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, > > org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, > > org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| > > JavaDoc for this beans is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7781) JMX beans documentation
[ https://issues.apache.org/jira/browse/IGNITE-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-7781: - Fix Version/s: (was: 2.4) 2.5 > JMX beans documentation > --- > > Key: IGNITE-7781 > URL: https://issues.apache.org/jira/browse/IGNITE-7781 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Labels: documentation, jmx > Fix For: 2.5 > > Attachments: MXBeansJavaDoc.zip > > > There are about 30 JMX beans implemented in Ignite, but there is no > documentation for most of these beans, except memory metrics and brief > overview of cache metrics. > Folowing MBeans/MXBeans can be documented: > ||MBeans group||Interface||Path||Comment|| > |Eviction > metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, > org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, > org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, > org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For > each cache, if eviction for cache is configured| > |Cache group > metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache > groups".|For each group| > |Cache > metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, > > org.apacheCacheLocalMetricsMXBeanImpl|For > each cache| > |Cluster > metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, > org.apache...Kernal.ClusterMetricsMXBeanImpl| > |Data region (memory) > metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For > each data region| > |Data storage > metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent > Store".DataStorageMetrics| > |Instance > information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| > |Ignition > state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| > |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, > org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread > Pools".|For each executor| > |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, > org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, > org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, > org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, > org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, > org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, > org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, > org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, > org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, > org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, > org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, > org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, > > org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, > > org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| > > JavaDoc for this beans is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7781) JMX beans documentation
[ https://issues.apache.org/jira/browse/IGNITE-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-7781: - Fix Version/s: 2.4 > JMX beans documentation > --- > > Key: IGNITE-7781 > URL: https://issues.apache.org/jira/browse/IGNITE-7781 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Labels: documentation, jmx > Fix For: 2.4 > > Attachments: MXBeansJavaDoc.zip > > > There are about 30 JMX beans implemented in Ignite, but there is no > documentation for most of these beans, except memory metrics and brief > overview of cache metrics. > Folowing MBeans/MXBeans can be documented: > ||MBeans group||Interface||Path||Comment|| > |Eviction > metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, > org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, > org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, > org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For > each cache, if eviction for cache is configured| > |Cache group > metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache > groups".|For each group| > |Cache > metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, > > org.apacheCacheLocalMetricsMXBeanImpl|For > each cache| > |Cluster > metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, > org.apache...Kernal.ClusterMetricsMXBeanImpl| > |Data region (memory) > metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For > each data region| > |Data storage > metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent > Store".DataStorageMetrics| > |Instance > information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| > |Ignition > state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| > |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, > org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread > Pools".|For each executor| > |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, > org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, > org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, > org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, > org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, > org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, > org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, > org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, > org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, > org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, > org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, > org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, > > org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, > > org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| > > JavaDoc for this beans is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7781) JMX beans documentation
Aleksey Plekhanov created IGNITE-7781: - Summary: JMX beans documentation Key: IGNITE-7781 URL: https://issues.apache.org/jira/browse/IGNITE-7781 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Attachments: MXBeansJavaDoc.zip There are about 30 JMX beans implemented in Ignite, but there is no documentation for most of these beans, except memory metrics and brief overview of cache metrics. Folowing MBeans/MXBeans can be documented: ||MBeans group||Interface||Path||Comment|| |Eviction metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For each cache, if eviction for cache is configured| |Cache group metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache groups".|For each group| |Cache metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, org.apacheCacheLocalMetricsMXBeanImpl|For each cache| |Cluster metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, org.apache...Kernal.ClusterMetricsMXBeanImpl| |Data region (memory) metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For each data region| |Data storage metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent Store".DataStorageMetrics| |Instance information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| |Ignition state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread Pools".|For each executor| |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| JavaDoc for this beans is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7781) JMX beans documentation
[ https://issues.apache.org/jira/browse/IGNITE-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-7781: -- Labels: documentation jmx (was: docuentation jmx) > JMX beans documentation > --- > > Key: IGNITE-7781 > URL: https://issues.apache.org/jira/browse/IGNITE-7781 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Labels: documentation, jmx > Attachments: MXBeansJavaDoc.zip > > > There are about 30 JMX beans implemented in Ignite, but there is no > documentation for most of these beans, except memory metrics and brief > overview of cache metrics. > Folowing MBeans/MXBeans can be documented: > ||MBeans group||Interface||Path||Comment|| > |Eviction > metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, > org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, > org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, > org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For > each cache, if eviction for cache is configured| > |Cache group > metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache > groups".|For each group| > |Cache > metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, > > org.apacheCacheLocalMetricsMXBeanImpl|For > each cache| > |Cluster > metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, > org.apache...Kernal.ClusterMetricsMXBeanImpl| > |Data region (memory) > metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For > each data region| > |Data storage > metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent > Store".DataStorageMetrics| > |Instance > information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| > |Ignition > state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| > |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, > org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread > Pools".|For each executor| > |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, > org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, > org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, > org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, > org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, > org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, > org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, > org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, > org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, > org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, > org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, > org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, > > org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, > > org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| > > JavaDoc for this beans is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7780) Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon
[ https://issues.apache.org/jira/browse/IGNITE-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371678#comment-16371678 ] Dmitriy Pavlov commented on IGNITE-7780: Thank you, I've started https://ci.ignite.apache.org/viewQueued.html?itemId=1105751&tab=queuedBuildOverviewTab to check this fix > Fix > ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon > -- > > Key: IGNITE-7780 > URL: https://issues.apache.org/jira/browse/IGNITE-7780 > Project: Ignite > Issue Type: Test >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7780) Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon
[ https://issues.apache.org/jira/browse/IGNITE-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7780: --- Fix Version/s: 2.5 > Fix > ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon > -- > > Key: IGNITE-7780 > URL: https://issues.apache.org/jira/browse/IGNITE-7780 > Project: Ignite > Issue Type: Test >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7780) Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon
[ https://issues.apache.org/jira/browse/IGNITE-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7780: --- Labels: MakeTeamcityGreenAgain (was: ) > Fix > ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon > -- > > Key: IGNITE-7780 > URL: https://issues.apache.org/jira/browse/IGNITE-7780 > Project: Ignite > Issue Type: Test >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Labels: MakeTeamcityGreenAgain > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7263) Daemon-mode Ignite node should not open&listen client port (10800)
[ https://issues.apache.org/jira/browse/IGNITE-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371655#comment-16371655 ] Pavel Vinokurov commented on IGNITE-7263: - [~dpavlov], I fixed test in [https://github.com/apache/ignite/pull/3555] Link to issue for the test fix - https://issues.apache.org/jira/browse/IGNITE-7780 > Daemon-mode Ignite node should not open&listen client port (10800) > -- > > Key: IGNITE-7263 > URL: https://issues.apache.org/jira/browse/IGNITE-7263 > Project: Ignite > Issue Type: Bug > Components: thin client, visor >Affects Versions: 2.1 >Reporter: Alexey Popov >Assignee: Pavel Vinokurov >Priority: Minor > Fix For: 2.5 > > > When I run a Visor console with default configuration file it opens a default > port (10800) for ODBC driver connection (and for thin JDBC, and for new > "thin" client). > Then I run several Ignite nodes. > So after that, the ODBC driver with default settings goes directly to a Visor > (daemon-mode Ignite) and does not able to get any data (daemon-mode Ignite > does not keep any data) > It is better to avoid such situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7780) Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon
[ https://issues.apache.org/jira/browse/IGNITE-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371650#comment-16371650 ] ASF GitHub Bot commented on IGNITE-7780: GitHub user pvinokurov opened a pull request: https://github.com/apache/ignite/pull/3555 IGNITE-7780 Fixed test ClientConnectorConfigurationValidationSelfTest#testJdbcCon… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7780 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3555.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3555 commit 9a01ac90cef25638c4d9829d39f830ea1c9469c8 Author: pvinokurov Date: 2018-02-21T16:48:56Z Fixed test ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon > Fix > ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon > -- > > Key: IGNITE-7780 > URL: https://issues.apache.org/jira/browse/IGNITE-7780 > Project: Ignite > Issue Type: Test >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7780) Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon
Pavel Vinokurov created IGNITE-7780: --- Summary: Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon Key: IGNITE-7780 URL: https://issues.apache.org/jira/browse/IGNITE-7780 Project: Ignite Issue Type: Test Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5555) Ignite PDS 1: JVM crash on teamcity (Rare)
[
https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371617#comment-16371617
]
ASF GitHub Bot commented on IGNITE-:
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/3554
IGNITE-: reproducing JVM crash (probably protected with assert) i…
…n reproducing suite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3554.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3554
commit f1530738ab6530f7b965dea621646b1e2f2c9a93
Author: dpavlov
Date: 2018-02-21T16:26:58Z
IGNITE-: reproducing JVM crash (probably protected with assert) in
reproducing suite
> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.5
>
> Attachments: crash_report, hs_err_pid7100.log.txt, thread_dump
>
>
> Most recent crashes
> https://ci.ignite.apache.org/viewLog.html?buildId=1095007&buildTypeId=IgniteTests24Java8_IgnitePds1&tab=buildResultsDiv
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ]
> BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started)
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=1086130&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgnitePds1
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ]
> BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started)
> {noformat}
> (older failure
> http://ci.ignite.apache.org/viewLog.html?buildId=675694&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgnitePds1#)
> Stacktrace indicates failure was in ignite code related to B+tree
> {noformat}J 34156 C2
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.readLockPage(JLorg/apache/ignite/internal/pagemem/FullPageId;ZZ)J
> (88 bytes) @ 0x7f98cfc24a5a [0x7f98cfc24540+0x51a]
> J 34634 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(JJJLorg/apache/ignite/internal/processors/cache/persistence/tree/io/BPlusIO;Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Get;I)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (380 bytes) @ 0x7f98d32dd524 [0x7f98d32dd100+0x424]
> J 34633 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;Lorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageHandler;Ljava/lang/Object;ILjava/lang/Object;)Ljava/lang/Object;
> (81 bytes) @ 0x7f98d2091c94 [0x7f98d2091a40+0x254]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca146c [0x7f98d2ca1180+0x2ec]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 35053 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(Ljava/lang/Object;Ljava/lang/Object;Lorg/apache/ignite/internal/util/Igni
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6879) Support Spring 2.0
[ https://issues.apache.org/jira/browse/IGNITE-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371560#comment-16371560 ] Robert Wruck commented on IGNITE-6879: -- [https://github.com/tweerlei/ignite-spring-data-2] This is for Ignite 2.3.0. I could try to make a pull request for 2.4.0-SNAPSHOT > Support Spring 2.0 > -- > > Key: IGNITE-6879 > URL: https://issues.apache.org/jira/browse/IGNITE-6879 > Project: Ignite > Issue Type: Improvement > Components: spring >Affects Versions: 2.3 >Reporter: Alexey Kukushkin >Priority: Major > > Ignite-spring and ignite-spring-data now use Spring 1.1 and cannot be rebuilt > with Spring 2.0. Trying to change the Spring dependency version to > 2.0.0.release results in compile errors like below and requires regression in > general. > This improvement was created to either migrate from Spring 1.1 to 2.0 or > create another set of modules ignite-spring-xxx-2 to have backward > compatibility with Spring 1.1. > [ERROR] > /Users/kukushal/Dev/incubator-ignite/modules/spring-data/src/main/java/org/apache/ignite/springdata/repository/IgniteRepository.java:[57,10] > name clash: deleteAll(java.lang.Iterable) in > org.apache.ignite.springdata.repository.IgniteRepository and > deleteAll(java.lang.Iterable) in > org.springframework.data.repository.CrudRepository have the same erasure, yet > neither overrides the other -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7263) Daemon-mode Ignite node should not open&listen client port (10800)
[ https://issues.apache.org/jira/browse/IGNITE-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371482#comment-16371482 ] Dmitriy Pavlov commented on IGNITE-7263: [~pvinokurov], test which merged to master does not work testJdbcConnectionDisabledForDaemon https://ci.ignite.apache.org/viewLog.html?buildId=1103998&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteBinaryObjectsSimpleMapperQueries could you please address it? > Daemon-mode Ignite node should not open&listen client port (10800) > -- > > Key: IGNITE-7263 > URL: https://issues.apache.org/jira/browse/IGNITE-7263 > Project: Ignite > Issue Type: Bug > Components: thin client, visor >Affects Versions: 2.1 >Reporter: Alexey Popov >Assignee: Pavel Vinokurov >Priority: Minor > Fix For: 2.5 > > > When I run a Visor console with default configuration file it opens a default > port (10800) for ODBC driver connection (and for thin JDBC, and for new > "thin" client). > Then I run several Ignite nodes. > So after that, the ODBC driver with default settings goes directly to a Visor > (daemon-mode Ignite) and does not able to get any data (daemon-mode Ignite > does not keep any data) > It is better to avoid such situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
[
https://issues.apache.org/jira/browse/IGNITE-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371478#comment-16371478
]
ASF GitHub Bot commented on IGNITE-7362:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/3552
IGNITE-7362: Fixed PDO issue when working with ODBC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7362
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3552.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3552
commit 37a23e76ebe45933e149d0399d5831c6bf133f02
Author: Igor Sapego
Date: 2018-01-30T17:26:34Z
IGNITE-7362: Added deprecated driver info support
commit 345c3f9f84dc646e1dbf8338c78416201c48cf4d
Author: Igor Sapego
Date: 2018-02-07T14:06:01Z
IGNITE-7362: Adjusted buffers writing
commit 04ecaf6978ca75fa6d2ec9214209fc8c3505dbad
Author: Igor Sapego
Date: 2018-02-12T15:29:28Z
IGNITE-7362: Re-worked columns fetching
commit 6f1c9d2e344005d21160bc2541c15ae66e87e3bc
Author: Igor Sapego
Date: 2018-02-13T10:10:42Z
IGNITE-7362: Fixes
commit 1333927954d39dcbbaa5ceb1c1a8d4da806a6d69
Author: Igor Sapego
Date: 2018-02-21T13:43:56Z
IGNITE-7362: Fixed errors.
> ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
> ---
>
> Key: IGNITE-7362
> URL: https://issues.apache.org/jira/browse/IGNITE-7362
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Third-party frameworks and ODBC bindings for different languages use metadata
> requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate
> varlen data, inserted by the user, which is only 64 by default.
> {code:java}
> ini_set("display_errors", 1);
> error_reporting(E_ALL);
> try {
> $ignite = new PDO('odbc:Apache Ignite');
> $ignite->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'DROP TABLE IF EXISTS test';
> $ignite->exec($sql);
> $sql = 'CREATE TABLE IF NOT EXISTS test (id int PRIMARY KEY, userkey
> VARCHAR(1000))';
> $ignite->exec($sql);
> $id = 1;
> $varval = 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed
> do elit, sed';
> $dbs = $ignite->prepare("INSERT INTO test (id, userkey) VALUES ($id,
> '$varval')");
> $dbs->execute();
> $dbs = $ignite->prepare("SELECT userkey from test where id=$id");
> $dbs->execute();
> $res = $dbs->fetchColumn();
> assert($varval == $res);
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
[
https://issues.apache.org/jira/browse/IGNITE-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-7362:
Description:
Third-party frameworks and ODBC bindings for different languages use metadata
requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate
varlen data, inserted by the user, which is only 64 by default.
{code:java}
setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
$sql = 'DROP TABLE IF EXISTS test';
$ignite->exec($sql);
$sql = 'CREATE TABLE IF NOT EXISTS test (id int PRIMARY KEY, userkey
VARCHAR(1000))';
$ignite->exec($sql);
$id = 1;
$varval = 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
elit, sed';
$dbs = $ignite->prepare("INSERT INTO test (id, userkey) VALUES ($id,
'$varval')");
$dbs->execute();
$dbs = $ignite->prepare("SELECT userkey from test where id=$id");
$dbs->execute();
$res = $dbs->fetchColumn();
assert($varval == $res);
} catch (PDOException $e) {
print "Error!: " . $e->getMessage() . "\n";
die();
}
?>
{code}
was:
Third-party frameworks and ODBC bindings for different languages use metadata
requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate
varlen data, inserted by the user, which is only 64 by default.
{code}
setAttribute(PDO::ATTR_ERRMODE,
PDO::ERRMODE_EXCEPTION);
$sql = 'CREATE TABLE IF NOT EXISTS test_md5 (id int PRIMARY
KEY, userkey
LONGVARCHAR, server LONGVARCHAR, tsession LONGVARCHAR, tpost LONGVARCHAR,
tget LONGVARCHAR, adddate int) WITH
"atomicity=transactional,cachegroup=somegroup"';
$ignite->exec($sql);
for($i=0; $i <= 10; $i++){
$dbs = $ignite->prepare("INSERT INTO test_md5 (id,
userkey, server,
tsession, tpost, tget, adddate) VALUES ($i, 'Lorem ipsum dolor sit amet,
consectetur adipiscing elit, sed do elit, sed', 'b', 'c', 'd', 'e', 1)");
$dbs->execute();
}
} catch (PDOException $e) {
print "Error!: " . $e->getMessage() . "\n";
die();
}
?>
{code}
> ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
> ---
>
> Key: IGNITE-7362
> URL: https://issues.apache.org/jira/browse/IGNITE-7362
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Third-party frameworks and ODBC bindings for different languages use metadata
> requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate
> varlen data, inserted by the user, which is only 64 by default.
> {code:java}
> ini_set("display_errors", 1);
> error_reporting(E_ALL);
> try {
> $ignite = new PDO('odbc:Apache Ignite');
> $ignite->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'DROP TABLE IF EXISTS test';
> $ignite->exec($sql);
> $sql = 'CREATE TABLE IF NOT EXISTS test (id int PRIMARY KEY, userkey
> VARCHAR(1000))';
> $ignite->exec($sql);
> $id = 1;
> $varval = 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed
> do elit, sed';
> $dbs = $ignite->prepare("INSERT INTO test (id, userkey) VALUES ($id,
> '$varval')");
> $dbs->execute();
> $dbs = $ignite->prepare("SELECT userkey from test where id=$id");
> $dbs->execute();
> $res = $dbs->fetchColumn();
> assert($varval == $res);
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
[
https://issues.apache.org/jira/browse/IGNITE-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371475#comment-16371475
]
Igor Sapego commented on IGNITE-7362:
-
It seems that root cause is the PDO sets the {{SQL_ATTR_ODBC_CURSORS}}
connection attribute to {{SQL_CUR_USE_IF_NEEDED}}, which enables cursor
library, if driver does not support fetching in {{PRIOR}} direction (which is
our case). Standard cursor library in its place works incorrectly with the
driver, which causes a lot of issues.
So, the current fix is to add {{SQL_FD_FETCH_PRIOR}} flag for
{{SQL_FETCH_DIRECTION}} driver info.
> ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
> ---
>
> Key: IGNITE-7362
> URL: https://issues.apache.org/jira/browse/IGNITE-7362
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Third-party frameworks and ODBC bindings for different languages use metadata
> requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate
> varlen data, inserted by the user, which is only 64 by default.
> {code}
> ini_set("display_errors", 1);
> error_reporting(E_ALL);
> try {
> $ignite = new PDO('odbc:Apache Ignite');
> $ignite->setAttribute(PDO::ATTR_ERRMODE,
> PDO::ERRMODE_EXCEPTION);
> $sql = 'CREATE TABLE IF NOT EXISTS test_md5 (id int PRIMARY
> KEY, userkey
> LONGVARCHAR, server LONGVARCHAR, tsession LONGVARCHAR, tpost LONGVARCHAR,
> tget LONGVARCHAR, adddate int) WITH
> "atomicity=transactional,cachegroup=somegroup"';
> $ignite->exec($sql);
> for($i=0; $i <= 10; $i++){
> $dbs = $ignite->prepare("INSERT INTO test_md5 (id,
> userkey, server,
> tsession, tpost, tget, adddate) VALUES ($i, 'Lorem ipsum dolor sit amet,
> consectetur adipiscing elit, sed do elit, sed', 'b', 'c', 'd', 'e', 1)");
> $dbs->execute();
> }
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7300) Allow expressions in SQL INSERTs within transactions
[
https://issues.apache.org/jira/browse/IGNITE-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-7300:
Issue Type: Task (was: Bug)
> Allow expressions in SQL INSERTs within transactions
>
>
> Key: IGNITE-7300
> URL: https://issues.apache.org/jira/browse/IGNITE-7300
> Project: Ignite
> Issue Type: Task
>Reporter: Alexander Paschenko
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.5
>
>
> The problem is related to IGNITE-7267 - the latter honors raw rows, but drops
> support for inserts with expressions which yield local subqueries. To fix
> this, {{UpdatePlan.isLocalSubquery()}} must be honored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7779) Ignite fails to start with a custom GridSecurityProcessor and enabled assertions
Robert Wruck created IGNITE-7779: Summary: Ignite fails to start with a custom GridSecurityProcessor and enabled assertions Key: IGNITE-7779 URL: https://issues.apache.org/jira/browse/IGNITE-7779 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.3 Reporter: Robert Wruck When a custom GridSecurityProcessor is installed, ServerImpl.joinTopology will call localAuthentication, which asserts that the passed SecurityCredentials are not null. Problem 1: There is no good way to set the SecurityCredentials for the local node. The GridGain implementation for example does this by "somehow" obtaining the GridKernalContext and directly setting the magic ATTR_SECURITY_CREDENTIALS attribute. Problem 2: Whether a GridSecurityProcessor accepts a null SecurityCredentials instance should not be decided in localAuthentication anyway. Please provide a documented way for GridSecurityProcessors to set set the SecurityCredentials and remove the assertion - it works just fine with null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7436) Username/password authentication for thin clients
[ https://issues.apache.org/jira/browse/IGNITE-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371385#comment-16371385 ] Taras Ledkov commented on IGNITE-7436: -- I've filed the issue to track p.2 activity: IGNITE-7778 Now we use metastorage to persist user data and metastorage works only with persistent cluster. So, we have to use another persistent storage for users or provide to persist metastorage for in-memory clusters. > Username/password authentication for thin clients > - > > Key: IGNITE-7436 > URL: https://issues.apache.org/jira/browse/IGNITE-7436 > Project: Ignite > Issue Type: Improvement > Components: jdbc, odbc, thin client >Affects Versions: 2.3 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > > This is an umbrella ticket to track all task related to the thin clients > authentication. > [Devlist > discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Username-password-authentication-for-thin-clients-td26058.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7756) Streamer fails if IgniteUuid is indexed
[
https://issues.apache.org/jira/browse/IGNITE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371386#comment-16371386
]
ASF GitHub Bot commented on IGNITE-7756:
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/3550
IGNITE-7756: IgniteUuid added to predefined types.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-7756
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3550.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3550
commit cbc9179b70f32391888de8fdc9eacc2df13c5965
Author: Nikolay Izhikov
Date: 2018-02-21T13:03:06Z
IGNITE-7756: IgniteUuid added to predefined types to resolve indexing issue.
> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed
> [node=57961924-82ec-4d56-81eb-1a4109a0]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial
> value for cache entry
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid,
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryMa
[jira] [Created] (IGNITE-7778) User's authentication data must be persisted on cluster with disabled persistence
Taras Ledkov created IGNITE-7778:
Summary: User's authentication data must be persisted on cluster
with disabled persistence
Key: IGNITE-7778
URL: https://issues.apache.org/jira/browse/IGNITE-7778
Project: Ignite
Issue Type: Task
Reporter: Taras Ledkov
The ticket is related to the: IGNITE-7436 (introduce users in Ignite)
{{IgniteAuthenticationProcessor}} uses metastorage to persist user data. But
metastorage works only with persistent cluster. We have to support user
authentication for in-memory cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7436) Username/password authentication for thin clients
[
https://issues.apache.org/jira/browse/IGNITE-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371355#comment-16371355
]
Vladimir Ozerov commented on IGNITE-7436:
-
[~tledkov-gridgain]. my comments:
1) {{DiscoveryCustomOnlyForServerMessage}} ->
{{DiscoveryServerOnlyCustomMessage}}
2) Passwords should be persisted w/o persistence (remove on-heap metastore)
3) {{ServerImpl}} - it is not a good idea to unmrashal original custom message
to check whether it should be sent to the client or not. Reasons: a)
performance; b) we do not want to have another code piece requiring
deserialziatio of potentially missing class on the server. It is better to
create another implementation of TcpDiscoveryCustomEventMessage for server-only
messages. Can we do that without breaking protoocl desperately?
> Username/password authentication for thin clients
> -
>
> Key: IGNITE-7436
> URL: https://issues.apache.org/jira/browse/IGNITE-7436
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, odbc, thin client
>Affects Versions: 2.3
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> This is an umbrella ticket to track all task related to the thin clients
> authentication.
> [Devlist
> discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Username-password-authentication-for-thin-clients-td26058.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7777) Thin Client lib: Node.js
Alexey Kosenchuk created IGNITE-: Summary: Thin Client lib: Node.js Key: IGNITE- URL: https://issues.apache.org/jira/browse/IGNITE- Project: Ignite Issue Type: New Feature Components: thin client Reporter: Alexey Kosenchuk Assignee: Alexey Kosenchuk Implement Thin (lightweight) Client lib in Node.js programming language for Ignite Binary Client Protocol https://apacheignite.readme.io/docs/binary-client-protocol Examples of other Thin Clients: .net https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client java https://github.com/gridgain/apache-ignite/tree/ignite-7421/modules/thinclient Scope of work - Functionality: Support all operations of the Ignite Binary Client Protocol 2.4. Support name/password authentication - TBD (not in the protocol yet). Support optional SSL/TLS communication - TBD (not in the protocol yet). Support optional failover/reconnect - TBD. Minimal Node.js version - TBD. Synch ops emulation - callbacks, or Promises, or asynch/await - TBD. Examples: Cover all basic features - Key-value API, SQL, Scan queries, Cluster configuration/management, Authentication, SSL/TLS. Tests: Jasmine tests for all API methods and all basic features. Simple Jasmine tests to start examples. How to emulate node failure to test failover/reconnect? - TBD. Docs: Auto-generated API spec from comments. JSdoc, or javadoc, or what? - TBD. Readme for the lib. Simple instruction to setup/run examples. Simple instruction to setup/run Jasmine tests. Docs format - .md in the repo, or dash.readme.io ? - TBD. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7776) Check calculated values in javadoc
Alexander Belyak created IGNITE-7776:
Summary: Check calculated values in javadoc
Key: IGNITE-7776
URL: https://issues.apache.org/jira/browse/IGNITE-7776
Project: Ignite
Issue Type: Bug
Components: documentation
Affects Versions: 2.3, 2.2, 2.1, 2.0
Reporter: Alexander Belyak
Assignee: Alexander Belyak
We have two issue with calculated value in javadoc:
1) wrong numbers, for example: #\{5 * 1024 * 102 * 1024}
2) overflow int type, for example: #\{5 * 1024 * 1024 * 1024}
Need to check&fix as many places as possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7775) Web console. Error in log on second click by cancel on profile page.
Vasiliy Sisko created IGNITE-7775:
-
Summary: Web console. Error in log on second click by cancel on
profile page.
Key: IGNITE-7775
URL: https://issues.apache.org/jira/browse/IGNITE-7775
Project: Ignite
Issue Type: Bug
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin
Opening of base page on Cancel click spend a lot of time.
If Cancel button is pressed second time error message will be printed into
console:
Transition Rejection($id: 52 type: 2, message: The transition has been
superseded by a different transition, detail: Transition#73(
'base.settings.profile'{} -> 'base.configuration.clusters'{} ))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7723) Data loss after node restart with PDS
[
https://issues.apache.org/jira/browse/IGNITE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371212#comment-16371212
]
Alexandr Kuramshin commented on IGNITE-7723:
Attached updated test which shows all problems at once
> Data loss after node restart with PDS
> -
>
> Key: IGNITE-7723
> URL: https://issues.apache.org/jira/browse/IGNITE-7723
> Project: Ignite
> Issue Type: Bug
> Components: general, persistence
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Priority: Major
> Attachments: IgnitePdsDataLossTest.java, IgnitePdsDataLossTest.java
>
>
> Split-brain scenario with topology validator is used to convince possible
> data loss. The same results may be achieved on accidental network problems
> combined with node restart.
> See the reproducer {{IgnitePdsDataLossTest}} for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7723) Data loss after node restart with PDS
[
https://issues.apache.org/jira/browse/IGNITE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandr Kuramshin updated IGNITE-7723:
---
Attachment: IgnitePdsDataLossTest.java
> Data loss after node restart with PDS
> -
>
> Key: IGNITE-7723
> URL: https://issues.apache.org/jira/browse/IGNITE-7723
> Project: Ignite
> Issue Type: Bug
> Components: general, persistence
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Priority: Major
> Attachments: IgnitePdsDataLossTest.java, IgnitePdsDataLossTest.java
>
>
> Split-brain scenario with topology validator is used to convince possible
> data loss. The same results may be achieved on accidental network problems
> combined with node restart.
> See the reproducer {{IgnitePdsDataLossTest}} for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7774) Missing Google Cloud libraries at binary release
[
https://issues.apache.org/jira/browse/IGNITE-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov reassigned IGNITE-7774:
--
Assignee: Roman Guseinov
> Missing Google Cloud libraries at binary release
>
>
> Key: IGNITE-7774
> URL: https://issues.apache.org/jira/browse/IGNITE-7774
> Project: Ignite
> Issue Type: Bug
> Components: build
> Environment: * Ubuntu 16.04.3 LTS
> * Apache Ignite 2.3.0
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: build
>
> It looks like following libraries aren't included in the build:
> * google-http-client-1.22.0.jar
> * google-http-client-jackson2-1.22.0.jar
> * google-oauth-client-1.22.0.jar
> Steps to reproduce:
> # Download apache-ignite-fabric-2.3.0-bin.zip
> ([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
> 2. Unzip archive.
> 2. Move ignite-gce from /libs/optional to /libs
> 3. Update IgniteConfiguration in default-config.xml:
> {code:xml}
>
>
>
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder">
>
>
>
> value="discovery-sp...@apache-ignite.iam.gserviceaccount.com"/>
>
>
>
>
> {code}
> 4. Copy into $IGNITE_HOME
> 5. Run bin/ignite.sh
> 6. Log:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
> application context (make sure all classes used in Spring configuration are
> present at CLASSPATH)
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> instantiate Spring XML application context (make sure all classes used in
> Spring configuration are present at CLASSPATH)
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
> at
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name
> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
> Cannot create inner bean
> 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type
> [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean
> property 'discoverySpi'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3'
> defined in URL
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
> Cannot create inner bean
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
> of type
> [org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
> while setting bean property 'ipFinder'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
> defined in URL
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
> Instantiation of bean failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]:
> No default constructor found; nested exception is
> java.lang.NoClassDefFoundError:
> com/google/api/client/http/AbstractInputStreamContent
> at
> org.springframework.beans.factory.s
[jira] [Commented] (IGNITE-7774) Missing Google Cloud libraries at binary release
[
https://issues.apache.org/jira/browse/IGNITE-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371204#comment-16371204
]
Roman Guseinov commented on IGNITE-7774:
[~oleg-ostanin] , will it solve the issue:
[https://github.com/gridgain/apache-ignite/commit/545c5c30934729a00e889c7e35a5a16e33a21155]
? How do you think?
> Missing Google Cloud libraries at binary release
>
>
> Key: IGNITE-7774
> URL: https://issues.apache.org/jira/browse/IGNITE-7774
> Project: Ignite
> Issue Type: Bug
> Components: build
> Environment: * Ubuntu 16.04.3 LTS
> * Apache Ignite 2.3.0
>Reporter: Roman Guseinov
>Priority: Major
> Labels: build
>
> It looks like following libraries aren't included in the build:
> * google-http-client-1.22.0.jar
> * google-http-client-jackson2-1.22.0.jar
> * google-oauth-client-1.22.0.jar
> Steps to reproduce:
> # Download apache-ignite-fabric-2.3.0-bin.zip
> ([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
> 2. Unzip archive.
> 2. Move ignite-gce from /libs/optional to /libs
> 3. Update IgniteConfiguration in default-config.xml:
> {code:xml}
>
>
>
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder">
>
>
>
> value="discovery-sp...@apache-ignite.iam.gserviceaccount.com"/>
>
>
>
>
> {code}
> 4. Copy into $IGNITE_HOME
> 5. Run bin/ignite.sh
> 6. Log:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
> application context (make sure all classes used in Spring configuration are
> present at CLASSPATH)
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> instantiate Spring XML application context (make sure all classes used in
> Spring configuration are present at CLASSPATH)
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
> at
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name
> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
> Cannot create inner bean
> 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type
> [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean
> property 'discoverySpi'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3'
> defined in URL
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
> Cannot create inner bean
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
> of type
> [org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
> while setting bean property 'ipFinder'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
> defined in URL
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
> Instantiation of bean failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]:
> No default constructor found; nested exceptio
[jira] [Assigned] (IGNITE-6467) Ignite cache 6: new tests CacheExchangeMergeTest.testConcurrentStartServersAndClients() and testDelayExchangeMessages() have flaky junit assertion after cache get
[
https://issues.apache.org/jira/browse/IGNITE-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko reassigned IGNITE-6467:
---
Assignee: Pavel Kovalenko
> Ignite cache 6: new tests
> CacheExchangeMergeTest.testConcurrentStartServersAndClients() and
> testDelayExchangeMessages() have flaky junit assertion after cache get
> --
>
> Key: IGNITE-6467
> URL: https://issues.apache.org/jira/browse/IGNITE-6467
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Pavel Kovalenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> Ignite cache 6: CacheExchangeMergeTest: 3 tests fails with probability >10%
> in master and in PRs
> IgniteCacheTestSuite6:
> CacheExchangeMergeTest.testConcurrentStartServersAndClients()
> IgniteCacheTestSuite6: CacheExchangeMergeTest.testDelayExchangeMessages()
> IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_2 (fail
> rate 22,6%)
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=741151191800314619&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-8990224019412265556&tab=testDetails
> latest failure from master
> https://ci.ignite.apache.org/viewLog.html?buildId=843261&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache6#testNameId741151191800314619
> {noformat}
> Invalid value [node=distributed.CacheExchangeMergeTest0, client=false,
> order=1, cache=c1] expected:<0> but was:
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkNodeCaches(CacheExchangeMergeTest.java:1343)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches0(CacheExchangeMergeTest.java:1213)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches(CacheExchangeMergeTest.java:1195)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.concurrentStart(CacheExchangeMergeTest.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.testConcurrentStartServersAndClients(CacheExchangeMergeTest.java:414)
> Caused by: junit.framework.AssertionFailedError: Invalid value
> [node=distributed.CacheExchangeMergeTest0, client=false, order=1, cache=c1]
> expected:<0> but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest$16.run(CacheExchangeMergeTest.java:1312)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7774) Missing Google Cloud libraries at binary release
Roman Guseinov created IGNITE-7774:
--
Summary: Missing Google Cloud libraries at binary release
Key: IGNITE-7774
URL: https://issues.apache.org/jira/browse/IGNITE-7774
Project: Ignite
Issue Type: Bug
Components: build
Environment: * Ubuntu 16.04.3 LTS
* Apache Ignite 2.3.0
Reporter: Roman Guseinov
It looks like following libraries aren't included in the build:
* google-http-client-1.22.0.jar
* google-http-client-jackson2-1.22.0.jar
* google-oauth-client-1.22.0.jar
Steps to reproduce:
# Download apache-ignite-fabric-2.3.0-bin.zip
([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
2. Unzip archive.
2. Move ignite-gce from /libs/optional to /libs
3. Update IgniteConfiguration in default-config.xml:
{code:xml}
{code}
4. Copy into $IGNITE_HOME
5. Run bin/ignite.sh
6. Log:
{code:java}
class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
application context (make sure all classes used in Spring configuration are
present at CLASSPATH)
[springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
instantiate Spring XML application context (make sure all classes used in
Spring configuration are present at CLASSPATH)
[springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
at
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 1 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0'
defined in URL
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
Cannot create inner bean
'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type
[org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean
property 'discoverySpi'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3'
defined in URL
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
Cannot create inner bean
'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
of type
[org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
while setting bean property 'ipFinder'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name
'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
defined in URL
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
Instantiation of bean failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]:
No default constructor found; nested exception is
java.lang.NoClassDefFoundError:
com/google/api/client/http/AbstractInputStreamContent
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1531)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1276)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutow
[jira] [Assigned] (IGNITE-6467) Ignite cache 6: new tests CacheExchangeMergeTest.testConcurrentStartServersAndClients() and testDelayExchangeMessages() have flaky junit assertion after cache get
[
https://issues.apache.org/jira/browse/IGNITE-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-6467:
Assignee: (was: Semen Boikov)
> Ignite cache 6: new tests
> CacheExchangeMergeTest.testConcurrentStartServersAndClients() and
> testDelayExchangeMessages() have flaky junit assertion after cache get
> --
>
> Key: IGNITE-6467
> URL: https://issues.apache.org/jira/browse/IGNITE-6467
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> Ignite cache 6: CacheExchangeMergeTest: 3 tests fails with probability >10%
> in master and in PRs
> IgniteCacheTestSuite6:
> CacheExchangeMergeTest.testConcurrentStartServersAndClients()
> IgniteCacheTestSuite6: CacheExchangeMergeTest.testDelayExchangeMessages()
> IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_2 (fail
> rate 22,6%)
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=741151191800314619&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-8990224019412265556&tab=testDetails
> latest failure from master
> https://ci.ignite.apache.org/viewLog.html?buildId=843261&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache6#testNameId741151191800314619
> {noformat}
> Invalid value [node=distributed.CacheExchangeMergeTest0, client=false,
> order=1, cache=c1] expected:<0> but was:
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkNodeCaches(CacheExchangeMergeTest.java:1343)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches0(CacheExchangeMergeTest.java:1213)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches(CacheExchangeMergeTest.java:1195)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.concurrentStart(CacheExchangeMergeTest.java:446)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.testConcurrentStartServersAndClients(CacheExchangeMergeTest.java:414)
> Caused by: junit.framework.AssertionFailedError: Invalid value
> [node=distributed.CacheExchangeMergeTest0, client=false, order=1, cache=c1]
> expected:<0> but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest$16.run(CacheExchangeMergeTest.java:1312)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7771) Names of Ignite JMX beans should not be quoted unless required
[ https://issues.apache.org/jira/browse/IGNITE-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371184#comment-16371184 ] Stanislav Lukyanov commented on IGNITE-7771: GridMBeansTest checks that JMX beans are available, but the bean names are not hardcoded there - it would be better to alter the test to use hardcoded names to make sure we don't miss an incompatible change in our JMX API. Need to update that test together with this fix. > Names of Ignite JMX beans should not be quoted unless required > -- > > Key: IGNITE-7771 > URL: https://issues.apache.org/jira/browse/IGNITE-7771 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > > Names of Ignite JMX beans and bean groups are currently quoted if they > contain non-alphanumeric characters. This leads to names with spaces, e.g. > Thread Pools, appearing as "Thread Pools". Moreover, Thread Pools and "Thread > Pools" are recognized by JMX as distinct names, so code accessing that MBean > needs to take that into account. > It would be better not to quote the bean and group names unless they contain > specific control characters. That way users won't need to quote names in > their JMX clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7770) Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 removal
[ https://issues.apache.org/jira/browse/IGNITE-7770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371171#comment-16371171 ] Dmitriy Pavlov commented on IGNITE-7770: Hi [~andrey-kuznetsov], I've muted this test if you don't mind. It fails too often > Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 > removal > > > Key: IGNITE-7770 > URL: https://issues.apache.org/jira/browse/IGNITE-7770 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Andrey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > > Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 > removal > After appying IGNITE-7518 Get rid of org.jsr166.LongAdder8, > IgniteCacheTestSuite6: > TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations (fail rate > 38,6%) > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3733584033131292028&branch=%3Cdefault%3E&tab=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7770) Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 removal
[ https://issues.apache.org/jira/browse/IGNITE-7770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7770: --- Labels: MakeTeamcityGreenAgain Muted_test (was: MakeTeamcityGreenAgain) > Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 > removal > > > Key: IGNITE-7770 > URL: https://issues.apache.org/jira/browse/IGNITE-7770 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Andrey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > > Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 > removal > After appying IGNITE-7518 Get rid of org.jsr166.LongAdder8, > IgniteCacheTestSuite6: > TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations (fail rate > 38,6%) > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3733584033131292028&branch=%3Cdefault%3E&tab=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
