[GitHub] ignite pull request #4153: IGNITE-1260 Added support for S3 keyPrefix in AWS...
GitHub user udaykale opened a pull request: https://github.com/apache/ignite/pull/4153 IGNITE-1260 Added support for S3 keyPrefix in AWS S3-based IP finder Resolves IGNITE-1260 You can merge this pull request into a Git repository by running: $ git pull https://github.com/udaykale/ignite IGNITE-1260 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4153.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 #4153 commit 515af752392b6872afe4085ed0555d6787f1d4f7 Author: uday Date: 2018-06-08T07:54:24Z IGNITE-1260 Added support for S3 keyPrefix in AWS S3-based IP finder ---
[jira] [Created] (IGNITE-8745) Add ability to monitor TCP discovery ring information
Alexey Goncharuk created IGNITE-8745: Summary: Add ability to monitor TCP discovery ring information Key: IGNITE-8745 URL: https://issues.apache.org/jira/browse/IGNITE-8745 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8746) EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator node
Pavel Vinokurov created IGNITE-8746: --- Summary: EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator node Key: IGNITE-8746 URL: https://issues.apache.org/jira/browse/IGNITE-8746 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov Attachments: EvtDataLostTwiceOnCoordinatorReprocuder.java After a node left the cluster the coordinator recieves the partition lost event twice. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4111: IGNITE-8645 fix for client tx metrics aren't incl...
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/4111 ---
[GitHub] ignite pull request #4154: IGNITE-8645 fix for client tx metrics aren't incl...
GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/4154 IGNITE-8645 fix for client tx metrics aren't included to cache metrics You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-8645 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4154.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 #4154 commit c3ed2cf9ebadea7e78ef34de0914c16603d9352a Author: voipp Date: 2018-06-01T16:28:55Z IGNITE-8645 fix for client tx metrics aren't included to cache metrics ---
[GitHub] ignite pull request #4154: IGNITE-8645 fix for client tx metrics aren't incl...
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/4154 ---
[GitHub] ignite pull request #4154: IGNITE-8645 fix for client tx metrics aren't incl...
GitHub user voipp reopened a pull request: https://github.com/apache/ignite/pull/4154 IGNITE-8645 fix for client tx metrics aren't included to cache metrics You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-8645 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4154.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 #4154 commit c3ed2cf9ebadea7e78ef34de0914c16603d9352a Author: voipp Date: 2018-06-01T16:28:55Z IGNITE-8645 fix for client tx metrics aren't included to cache metrics ---
[GitHub] ignite pull request #4155: IGNITE-8661 WALItreater is not stopped if can not...
GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/4155 IGNITE-8661 WALItreater is not stopped if can not deserialize record You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8661 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4155.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 #4155 commit e57074824be2e114c8d8607f43f66c028a06d860 Author: Dmitriy Govorukhin Date: 2018-06-01T11:53:48Z IGNITE-8661 add IteratorParametersBuilder + refactoring commit fc63c038e15dd49e7114fad0083af2c0e90e2b98 Author: Dmitriy Govorukhin Date: 2018-06-01T13:13:57Z IGNITE-8661 refactoring commit 667fea64a99c2dcc4ad9c173a96f2d345fafffc2 Author: Dmitriy Govorukhin Date: 2018-06-07T11:10:27Z IGNITE-8661 commit d64289500c21db130416de2e094a06a44486f2d1 Author: Dmitriy Govorukhin Date: 2018-06-07T16:51:51Z IGNITE-8661 wip commit 2706b2bc6cb008c3f921c2b1ba33a9aca18ab412 Author: Dmitriy Govorukhin Date: 2018-06-08T09:18:02Z Merge branch 'master' into ignite-8661 ---
[jira] [Created] (IGNITE-8747) Remove\RemoveAll method should not count expired entry as removed.
Andrew Mashenkov created IGNITE-8747: Summary: Remove\RemoveAll method should not count expired entry as removed. Key: IGNITE-8747 URL: https://issues.apache.org/jira/browse/IGNITE-8747 Project: Ignite Issue Type: Improvement Components: cache Reporter: Andrew Mashenkov We have 2 TCK 1.0 test that are passed due to we have eagerTtl=true by default. The reason is remove() return true even if an expired entry was removed. Seems, we have to evict expired entry from cache on remove(), but do not count it as removed. java.lang.AssertionError at org.jsr107.tck.expiry.CacheExpiryTest.expire_whenAccessed(CacheExpiryTest.java:326) java.lang.AssertionError: expected:<0> but was:<1> at org.jsr107.tck.expiry.CacheExpiryTest.testCacheStatisticsRemoveAll(CacheExpiryTest.java:160) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Things To Do Before You Turn 30^W^WRelease 3.0
Ilya, In my view putting @Deprecated is enough for now for things that should be removed. When we will come closer to 3.0 release we will look through all deprecated stuff and remove it. This applies to IGNITE_BINARY_SORT_OBJECT_FIELDS. Can you please annotate it? As far as list of breaking changes we may want to do in 3.0, I think we need to file tickets for 3.0 and label them as "breaking change" to reflect in release notes those that will be implemented. Thoughs? --Yakov 2018-06-07 19:36 GMT+03:00 Ilya Kasnacheev : > Hello! > > Do we have an official subj list? Such as Wiki page or JIRA label? > > Cause if we don't, we'll surely forget a lot of things and will have to > wait for 4.0. > We already did that with IGNITE_BINARY_SORT_OBJECT_FIELDS in 2.0 :( > > I expect to have in this list breaking changes, and @Deprecated stuff to be > finally removed, and maybe unmaintained modules to be put to rest. > > Regards, > -- > Ilya Kasnacheev >
[GitHub] ignite pull request #4156: IGNITE-5973 Flaky failures.
GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4156 IGNITE-5973 Flaky failures. â¦(fix). You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-5973 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4156.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 #4156 commit 48044b147d11992cefddf74502207dca355d9f62 Author: pereslegin-pa Date: 2018-06-08T09:46:13Z IGNITE-5973 Add ability to close datastructure in interrupted thread (fix). ---
[GitHub] ignite pull request #4157: IGNITE-8711 test was adopted to take into account...
GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4157 IGNITE-8711 test was adopted to take into account changes from IGNITE-5789 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8711 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4157.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 #4157 commit 9d69d868fe6cc348c3087291da6a5391e88fd97b Author: Sergey Chugunov Date: 2018-06-08T10:48:15Z IGNITE-8711 test was adopted to take into account changes from IGNITE-5789 ---
[jira] [Created] (IGNITE-8748) All FileIO#write methods should return number of written bytes
Sergey Chugunov created IGNITE-8748: --- Summary: All FileIO#write methods should return number of written bytes Key: IGNITE-8748 URL: https://issues.apache.org/jira/browse/IGNITE-8748 Project: Ignite Issue Type: Improvement Reporter: Sergey Chugunov FileIO#write(byte[], int, int) doesn't return a value of written bytes which makes it impossible for callers to detect a situation of no space left on device. API should be changed to return written bytes, all callers of this method should adopt changes to be ready to detect "no space left" situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8749) Exception for "no space left" situation should be propagated to FailureHandler
Sergey Chugunov created IGNITE-8749: --- Summary: Exception for "no space left" situation should be propagated to FailureHandler Key: IGNITE-8749 URL: https://issues.apache.org/jira/browse/IGNITE-8749 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Sergey Chugunov Fix For: 2.6 For now if "no space left" situation is detected in FileWriteAheadLogManager#formatFile method and corresponding exception is thrown the exception doesn't get propagated to FailureHandler and node continues working. As "no space left" is a critical situation, corresponding exception should be propagated to handler to make necessary actions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4158: IGNITE-8742: research - test suite constriction.
GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/4158 IGNITE-8742: research - test suite constriction. You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-8742 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4158.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 #4158 commit b1eb5f29a8b2fcf0f97e7bd216fd2d464ccaaabf Author: Dmitriy Sorokin Date: 2018-06-08T12:19:44Z IGNITE-8742: research - test suite constriction. ---
[GitHub] ignite pull request #4157: IGNITE-8711 test was adopted to take into account...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4157 ---
[jira] [Created] (IGNITE-8750) IgniteWalFlushDefaultSelfTest.testFailAfterStart fails on TC
Pavel Kovalenko created IGNITE-8750:
---
Summary: IgniteWalFlushDefaultSelfTest.testFailAfterStart fails on
TC
Key: IGNITE-8750
URL: https://issues.apache.org/jira/browse/IGNITE-8750
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.5
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko
Fix For: 2.6
{noformat}
org.apache.ignite.IgniteException: Failed to get object field
[obj=GridCacheSharedManagerAdapter [starting=true, stop=false],
fieldNames=[mmap]]
Caused by: java.lang.NoSuchFieldException: mmap
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4052: IGNITE-5954 Remove obsolete near cache value from...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4052 ---
Re: Things To Do Before You Turn 30^W^WRelease 3.0
Hello! Thanks for swift response! What about changes that would benefit from discussion? For example, I think we should consider having usePairedConnections=true by default in 3.0 (or, increase socketWriteTimeout). Should I create an IEP about it, or fill a JIRA ticket and see what happens? Regards, -- Ilya Kasnacheev 2018-06-08 13:01 GMT+03:00 Yakov Zhdanov : > Ilya, > > In my view putting @Deprecated is enough for now for things that should be > removed. When we will come closer to 3.0 release we will look through all > deprecated stuff and remove it. This applies to > IGNITE_BINARY_SORT_OBJECT_FIELDS. > Can you please annotate it? > > As far as list of breaking changes we may want to do in 3.0, I think we > need to file tickets for 3.0 and label them as "breaking change" to reflect > in release notes those that will be implemented. > > Thoughs? > > --Yakov > > 2018-06-07 19:36 GMT+03:00 Ilya Kasnacheev : > > > Hello! > > > > Do we have an official subj list? Such as Wiki page or JIRA label? > > > > Cause if we don't, we'll surely forget a lot of things and will have to > > wait for 4.0. > > We already did that with IGNITE_BINARY_SORT_OBJECT_FIELDS in 2.0 :( > > > > I expect to have in this list breaking changes, and @Deprecated stuff to > be > > finally removed, and maybe unmaintained modules to be put to rest. > > > > Regards, > > -- > > Ilya Kasnacheev > > >
Re: Things To Do Before You Turn 30^W^WRelease 3.0
We can start with separate discussion on dev list. Or can you point to existing one? I think I need some details here. --Yakov
[jira] [Created] (IGNITE-8751) Possible race on node segmentation.
Andrew Mashenkov created IGNITE-8751: Summary: Possible race on node segmentation. Key: IGNITE-8751 URL: https://issues.apache.org/jira/browse/IGNITE-8751 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Andrew Mashenkov Segmentation policy may be ignored, probably, due to a race. See [1] for details. [1] [http://apache-ignite-users.70518.x6.nabble.com/Node-pause-for-no-obvious-reason-td21923.html] Logs from segmented node. [08:42:42,290][INFO][tcp-disco-sock-reader-#15][TcpDiscoverySpi] Finished serving remote node connection [rmtAddr=/10.29.42.45:38712, rmtPort=38712 [08:42:42,290][WARNING][disco-event-worker-#161][GridDiscoveryManager] Local node SEGMENTED: TcpDiscoveryNode [id=8333aa56-8bf4-4558-a387-809b1d2e2e5b, addrs=[10.29.42.44, 127.0.0.1], sockAddrs=[sap-datanode1/10.29.42.44:49500, /127.0.0.1:49500], discPort=49500, order=1, intOrder=1, lastExchangeTime=1528447362286, loc=true, ver=2.5.0#20180523-sha1:86e110c7, isClient=false] [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] Critical system error detected. Will be handled accordingly to configured handler [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated unexpectedly.]] java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated unexpectedly. at org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated unexpectedly.]] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8752) Deadlock when registering binary metadata while holding topology read lock
Alexey Goncharuk created IGNITE-8752: Summary: Deadlock when registering binary metadata while holding topology read lock Key: IGNITE-8752 URL: https://issues.apache.org/jira/browse/IGNITE-8752 Project: Ignite Issue Type: Bug Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8753) Improve error message when requested topology version was preempted from Discovery Cache
Sergey Chugunov created IGNITE-8753: --- Summary: Improve error message when requested topology version was preempted from Discovery Cache Key: IGNITE-8753 URL: https://issues.apache.org/jira/browse/IGNITE-8753 Project: Ignite Issue Type: Improvement Reporter: Sergey Chugunov When a lot of nodes try to join cluster at the same time (which is common when ZookeeperDiscoverySpi is used), size of Discovery Cache may be exhausted so next node won't find topology version it needs to proceed with joining. For now exception is thrown in this situation, we need to improve its message with suggestion to check DISCOVERY_HISTORY setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4159: IGNITE-8529 Implement testing framework for check...
GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/4159 IGNITE-8529 Implement testing framework for checking WAL delta records consistency You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-8529 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4159.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 #4159 commit a5c142daf7c46a354d5417dac7cf7c3c79a9488b Author: Aleksey Plekhanov Date: 2018-06-07T10:39:52Z IGNITE-8529 Draft 3 WIP commit 0ddd4d82c3625e45f21650267685bd2020997cb1 Author: Aleksey Plekhanov Date: 2018-06-07T12:25:42Z IGNITE-8529 Draft 3 WIP commit ada909a74d5b000ac741c07421da7f5bcc955023 Author: Aleksey Plekhanov Date: 2018-06-07T16:46:33Z IGNITE-8529 Draft 3 WIP commit 3f570c578b4946c6d599e9efbabf6260a45bce50 Author: Aleksey Plekhanov Date: 2018-06-07T16:51:08Z IGNITE-8529 Draft 3 WIP commit 883acf9447c2619799f6078523504082ada4dc21 Author: Aleksey Plekhanov Date: 2018-06-07T21:36:02Z IGNITE-8529 Draft 2 WIP commit 7cb3d90ff758e42ef7d876d17cb4d597fb0ee240 Author: Aleksey Plekhanov Date: 2018-06-08T07:46:42Z IGNITE-8529 Draft 3 WIP commit 41d2dc6a44c3a3775254f9d68595e04ba4198e98 Author: Aleksey Plekhanov Date: 2018-06-08T10:43:18Z IGNITE-8529 Implement testing framework for checking WAL delta records consistency commit 4678f6a6b4c7a5922063f2118bb4810f5e2b6d12 Author: Aleksey Plekhanov Date: 2018-06-08T12:52:01Z IGNITE-8529 Made page memory reusable after cache destroy. commit c64719bf6be1562b0ad8f660eecf780cafca4334 Author: Aleksey Plekhanov Date: 2018-06-08T14:23:14Z IGNITE-8529 Made page memory reusable after cache destroy (fix). commit 755cae5c68ef472a56871a891095721aebe60ff0 Author: Aleksey Plekhanov Date: 2018-06-08T14:32:47Z IGNITE-8529 Cleanup ---
[GitHub] ignite pull request #4160: IGNITE-8727 Fixed WalFlush with MMap tests.
GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4160 IGNITE-8727 Fixed WalFlush with MMap tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8727 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4160.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 #4160 commit ceeec8591ad50b8475f0aa2d609b1d95372f6bd9 Author: Pavel Kovalenko Date: 2018-06-08T14:39:48Z IGNITE-8727 Fixed WalFlush with MMap tests. ---
[jira] [Created] (IGNITE-8754) Node outside of baseline does not start when service configured
Vladislav Pyatkov created IGNITE-8754:
-
Summary: Node outside of baseline does not start when service
configured
Key: IGNITE-8754
URL: https://issues.apache.org/jira/browse/IGNITE-8754
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
Attachments: ServiceOnNodeOutOfBaselineTest.java
Enough to configure service in {{ServiceConfiguration}} and the node does not
started if the node outside of baseline.
{noformat}
"async-runnable-runner-1" #287 prio=5 os_prio=0 tid=0x24e0c800
nid=0x4e6c waiting on condition [0xe87fe000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:287)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:228)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1105)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
- locked <0x00076c142400> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:649)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
at
org.gridgain.internal.ServiceOnNodeOutOfBaselineTest.lambda$test$0(ServiceOnNodeOutOfBaselineTest.java:107)
at
org.gridgain.internal.ServiceOnNodeOutOfBaselineTest$$Lambda$22/781127963.run(Unknown
Source)
at
org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$1(GridTestUtils.java:898)
at
org.apache.ignite.testframework.GridTestUtils$$Lambda$23/1655470614.call(Unknown
Source)
at
org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:956)
at
org.apache.ignite.testframework.GridTestUtils$$Lambda$24/1782331932.run(Unknown
Source)
at
org.apache.ignite.testframework.GridTestUtils$6.call(GridTestUtils.java:1254)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4148: IGNITE-8739 cherry picked from GG-13874 Implement...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4148 ---
Hello
Hello
[jira] [Created] (IGNITE-8755) NegativeArraySizeException when trying to serialize in GridClientOptimizedMarshaller humongous object
Ivan Daschinskiy created IGNITE-8755:
Summary: NegativeArraySizeException when trying to serialize in
GridClientOptimizedMarshaller humongous object
Key: IGNITE-8755
URL: https://issues.apache.org/jira/browse/IGNITE-8755
Project: Ignite
Issue Type: Bug
Components: binary
Affects Versions: 2.5
Reporter: Ivan Daschinskiy
Fix For: 2.6
When trying to serialize humongous object in GridClientOptimizedMarshaller,
NegativeArraySizeException thrown. See below
{code:java}
java.io.IOException: class org.apache.ignite.IgniteCheckedException: Failed to
serialize object: GridClientResponse [clientId=null, reqId=0, destId=null,
status=0, errMsg=null,
result=org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest$HugeObject@60a582c1]
at
org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller.marshal(GridClientOptimizedMarshaller.java:101)
at
org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest.testHugeObject(TcpRestParserSelfTest.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2086)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2001)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to serialize
object: GridClientResponse [clientId=null, reqId=0, destId=null, status=0,
errMsg=null,
result=org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest$HugeObject@60a582c1]
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:206)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
at
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10059)
at
org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller.marshal(GridClientOptimizedMarshaller.java:88)
... 10 more
Caused by: java.lang.NegativeArraySizeException
at
org.apache.ignite.internal.util.io.GridUnsafeDataOutput.requestFreeSize(GridUnsafeDataOutput.java:131)
at
org.apache.ignite.internal.util.io.GridUnsafeDataOutput.write(GridUnsafeDataOutput.java:166)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.write(OptimizedObjectOutputStream.java:142)
at
org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest$HugeObject.writeExternal(TcpRestParserSelfTest.java:122)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeExternalizable(OptimizedObjectOutputStream.java:319)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:814)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:242)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at
org.apache.ignite.internal.processors.rest.client.message.GridClientResponse.writeExternal(GridClientResponse.java:103)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeExternalizable(OptimizedObjectOutputStream.java:319)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:814)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:242)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:201)
{code}
The main cause of this that GridClientOptimizedMarshaller marshall object
through OptimizedMarshaller without backed OutputStream, so arithmetical
overflow occurs in GridUnsafeDataOutput.requestFreeSiz
Re: Hello
Hi, I hope this email finds you well. Sincerely, Dmitriy Pavlov пт, 8 июн. 2018 г. в 18:18, Сергей Тайлаков : > Hello >
[GitHub] ignite pull request #4024: IGNITE-7818
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4024 ---
[jira] [Created] (IGNITE-8756) SQL: CREATE/ALTER USER documentation should contain information about case sensitivity of username
Andrey Aleksandrov created IGNITE-8756:
--
Summary: SQL: CREATE/ALTER USER documentation should contain
information about case sensitivity of username
Key: IGNITE-8756
URL: https://issues.apache.org/jira/browse/IGNITE-8756
Project: Ignite
Issue Type: Improvement
Components: sql
Affects Versions: 2.5
Reporter: Andrey Aleksandrov
Fix For: 2.6
Now documentation contains next:
https://apacheignite-sql.readme.io/docs/create-user#section-description
For instance, if {{test}} was set as a username then:
* You can use {{Test}}, {{TEst}}, {{TEST}} and other combinations from JDBC
and ODBC.
* You have to use {{TEST}} as the username from Ignite's native SQL APIs
designed for Java, .NET and other programming languages.
But next behavior exists:
When you create the user in quotes ("test") using SQL as next:
CREATE USER "test" WITH PASSWORD 'test'
It will be created as it was set (in this case it will be test)
If you create the user without quotes (test) using SQL as next:
CREATE USER test WITH PASSWORD 'test'
then username will be stored in uppercase (TEST).
The same situation with ALTER USER.
The documentation should be updated to clear that SQL supports case sensitive
data too (using quotas).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4049: IGNITE-8183 ZookeeperDiscoverySpiTest#testSegment...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4049 ---
[jira] [Created] (IGNITE-8757) idle_verify utility doesn't show both update counter and hash conflicts
Ivan Rakov created IGNITE-8757: -- Summary: idle_verify utility doesn't show both update counter and hash conflicts Key: IGNITE-8757 URL: https://issues.apache.org/jira/browse/IGNITE-8757 Project: Ignite Issue Type: Bug Reporter: Ivan Rakov Assignee: Ivan Rakov If there are two partitions in cluster, one with different update counters and one with different data, idle_verify will show only partition with broken counters. We should show both for better visibility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4161: GNITE-8699: Flaky test.
GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/4161 GNITE-8699: Flaky test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-8699 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4161.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 #4161 commit 709ae0f6d914c7cb99ce8b637a75c7fbba1a951a Author: Vitaliy Biryukov Date: 2018-06-08T21:37:39Z GNITE-8699: Flaky test. ---
Re: Node.JS thin client: Node.JS thin client fails
Tested on the master. Everything works fine for me. Thanks. -- Denis On Thu, Jun 7, 2018 at 10:20 AM, Pavel Petroshenko wrote: > Thank, Vladimir. > > Denis, confirming, AI 2.5 is not supported. > > However, all the tests and examples happily pass on the latest master (as > of today). So please use it for testing. > > Thanks, > p. > > > On Thu, Jun 7, 2018 at 12:33 AM, Vladimir Ozerov > wrote: > >> Denis, >> >> No, AI 2.5 is not supported. >> >> чт, 7 июня 2018 г. в 2:37, Denis Magda : >> >>> Pavel, >>> >>> I'm tried to run an SQL example following the prepared documentation: >>> https://apacheignite.readme.io/v2.5/docs/nodejs-thin-client# >>> section-examples >>> >>> Getting an exception below when execute `node SqlQueryEntriesExample.js` >>> example. Do we support Ignite 2.5 (using its binaries)? Do I need to use >>> Ignite master instead? >>> >>> [16:31:13,389][SEVERE][client-connector-#46][ClientListenerNioListener] >>> Failed to parse client request. >>> >>> class org.apache.ignite.binary.BinaryObjectException: Unexpected field >>> type >>> [pos=73, expected=String, actual=-1] >>> >>> at >>> org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFl >>> agNoHandles(BinaryReaderExImpl.java:1677) >>> >>> at >>> org.apache.ignite.internal.binary.BinaryReaderExImpl.readStr >>> ing(BinaryReaderExImpl.java:1055) >>> >>> at >>> org.apache.ignite.internal.processors.platform.utils.Platfor >>> mConfigurationUtils.readQueryEntity(PlatformConfigurationUtils.java:500) >>> >>> at >>> org.apache.ignite.internal.processors.platform.client.cache. >>> ClientCacheConfigurationSerializer.read(ClientCacheConfigura >>> tionSerializer.java:352) >>> >>> at >>> org.apache.ignite.internal.processors.platform.client.cache. >>> ClientCacheGetOrCreateWithConfigurationRequest.(Client >>> CacheGetOrCreateWithConfigurationRequest.java:46) >>> >>> at >>> org.apache.ignite.internal.processors.platform.client.Client >>> MessageParser.decode(ClientMessageParser.java:336) >>> >>> at >>> org.apache.ignite.internal.processors.platform.client.Client >>> MessageParser.decode(ClientMessageParser.java:220) >>> >>> at >>> org.apache.ignite.internal.processors.odbc.ClientListenerNio >>> Listener.onMessage(ClientListenerNioListener.java:138) >>> >>> at >>> org.apache.ignite.internal.processors.odbc.ClientListenerNio >>> Listener.onMessage(ClientListenerNioListener.java:44) >>> >>> at >>> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailF >>> ilter.onMessageReceived(GridNioFilterChain.java:279) >>> >>> at >>> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.pro >>> ceedMessageReceived(GridNioFilterAdapter.java:109) >>> >>> at >>> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body( >>> GridNioAsyncNotifyFilter.java:97) >>> >>> at >>> org.apache.ignite.internal.util.worker.GridWorker.run(GridWo >>> rker.java:110) >>> >>> at >>> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run( >>> GridWorkerPool.java:70) >>> >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool >>> Executor.java:1142) >>> >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo >>> lExecutor.java:617) >>> >>> at java.lang.Thread.run(Thread.java:745) >>> >> >
[GitHub] ignite pull request #4162: IGNITE-8757 idle_verify utility doesn't show both...
GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4162 IGNITE-8757 idle_verify utility doesn't show both update counter and ⦠â¦hash conflict You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8757 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4162.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 #4162 commit af11c6925ef5c42ebf5273e80638e162fec9f35e Author: Ivan Rakov Date: 2018-06-08T23:02:13Z IGNITE-8757 idle_verify utility doesn't show both update counter and hash conflict ---
[jira] [Created] (IGNITE-8758) Web console: Broken UI under Firefox in case of long user name
Pavel Konstantinov created IGNITE-8758: -- Summary: Web console: Broken UI under Firefox in case of long user name Key: IGNITE-8758 URL: https://issues.apache.org/jira/browse/IGNITE-8758 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Jaust change a user name in the profile to 1 and check how it looks under Firefox -- This message was sent by Atlassian JIRA (v7.6.3#76005)
