[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom
[
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908207#comment-14908207
]
Andrey Gura commented on IGNITE-1526:
-
{quote}1) It's not possible to compile the platform using IBM JDK ver
1.7;{quote}
Ignite compiles with IBM JDK 7.1. But some problems are possible in case of
using {{com.sun}} packages because not all of them present in IBM JDK.
> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some
> functionality still doesn't work. As an example
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi]
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.io.InvalidClassException:
> org.apache.ignite.internal.util.lang.G
> ridFunc$38; local class incompatible: stream classdesc serialVersionUID =
> -55433
> 49853748590486, local class serialVersionUID = -5664060422647374863
> at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
> at
>
[jira] [Updated] (IGNITE-1551) IgniteCache.put hangs indefinatly
[
https://issues.apache.org/jira/browse/IGNITE-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Bench updated IGNITE-1551:
Description:
We have a process that pulls jobs from a queue and puts associated assets into
a cache using IgniteCache.put.
The object we put into the cache is an object holding a map of Enums and byte
arrays.
{code}
private Map assets = new EnumMap<>(AssetTypeEnum.class);
{code}
We are using a UUID as the key.
The byte arrays can become quite large - the batch it was processing when the
issue occurred were up to 30mb in size.
The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a
few hours until we restarted Tomcat.
I took a memory Snapshot using YourKit while the application was frozen
(https://onedrive.live.com/redir?resid=F06891F3AE093614!892=!AMfOdu7-jEtk_KA=file%2csnapshot)
which shows the thread {{taskExecutorBean-3}} waiting in sun.misc.Unsafe.park.
It has spent 100% of the time I profiled here.
was:
We have a process that pulls jobs from a queue and puts associated assets into
a cache using IgniteCache.put.
The object we put into the cache is an object holding a map of Enums and byte
arrays.
{code}
private Map assets = new EnumMap<>(AssetTypeEnum.class);
{code}
We are using a UUID as the key.
The byte arrays can become quite large - the batch it was processing when the
issue occurred were up to 30mb in size.
The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a
few hours until we restarted Tomcat.
I took a memory Snapshot using YourKit while the application was frozen
(attached) which shows the thread {{taskExecutorBean-3}} waiting in
sun.misc.Unsafe.park. It has spent 100% of the time I profiled here.
> IgniteCache.put hangs indefinatly
> -
>
> Key: IGNITE-1551
> URL: https://issues.apache.org/jira/browse/IGNITE-1551
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Environment: Ubuntu 14.04
> java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Tomcat 7
>Reporter: James Bench
>
> We have a process that pulls jobs from a queue and puts associated assets
> into a cache using IgniteCache.put.
> The object we put into the cache is an object holding a map of Enums and byte
> arrays.
> {code}
> private Map assets = new
> EnumMap<>(AssetTypeEnum.class);
> {code}
> We are using a UUID as the key.
> The byte arrays can become quite large - the batch it was processing when the
> issue occurred were up to 30mb in size.
> The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a
> few hours until we restarted Tomcat.
> I took a memory Snapshot using YourKit while the application was frozen
> (https://onedrive.live.com/redir?resid=F06891F3AE093614!892=!AMfOdu7-jEtk_KA=file%2csnapshot)
> which shows the thread {{taskExecutorBean-3}} waiting in
> sun.misc.Unsafe.park. It has spent 100% of the time I profiled here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1551) IgniteCache.put hangs indefinatly
James Bench created IGNITE-1551:
---
Summary: IgniteCache.put hangs indefinatly
Key: IGNITE-1551
URL: https://issues.apache.org/jira/browse/IGNITE-1551
Project: Ignite
Issue Type: Bug
Components: cache
Environment: Ubuntu 14.04
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
Tomcat 7
Reporter: James Bench
We have a process that pulls jobs from a queue and puts associated assets into
a cache using IgniteCache.put.
The object we put into the cache is an object holding a map of Enums and byte
arrays.
{code}
private Map assets = new EnumMap<>(AssetTypeEnum.class);
{code}
We are using a UUID as the key.
The byte arrays can become quite large - the batch it was processing when the
issue occurred were up to 30mb in size.
The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a
few hours until we restarted Tomcat.
I took a memory Snapshot using YourKit while the application was frozen
(attached) which shows the thread {{taskExecutorBean-3}} waiting in
sun.misc.Unsafe.park. It has spent 100% of the time I profiled here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-601) [Test] Lock reentry tests fails for PARTITIONED_ONLY cache
[ https://issues.apache.org/jira/browse/IGNITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-601: Fix Version/s: ignite-1.5 > [Test] Lock reentry tests fails for PARTITIONED_ONLY cache > -- > > Key: IGNITE-601 > URL: https://issues.apache.org/jira/browse/IGNITE-601 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: failedtest > Fix For: ignite-1.5 > > > To reproduce change GridCachePartitionedBasicApiTest to use PARTITIONED_ONLY > cache instead of NEAR_PARTITIONED. > See GG-7437. Comments from origin Jira: > - Fixed in gg-7434-1 > - Reopening since there are left TODOs in data grid test suite. > Now, see GridCacheReplicatedNearOnlyMultiNodeFullApiSelfTest # lockingEnabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-601) [Test] Lock reentry tests fails for PARTITIONED_ONLY cache
[ https://issues.apache.org/jira/browse/IGNITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-601: --- Assignee: Semen Boikov > [Test] Lock reentry tests fails for PARTITIONED_ONLY cache > -- > > Key: IGNITE-601 > URL: https://issues.apache.org/jira/browse/IGNITE-601 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: failedtest > Fix For: ignite-1.5 > > > To reproduce change GridCachePartitionedBasicApiTest to use PARTITIONED_ONLY > cache instead of NEAR_PARTITIONED. > See GG-7437. Comments from origin Jira: > - Fixed in gg-7434-1 > - Reopening since there are left TODOs in data grid test suite. > Now, see GridCacheReplicatedNearOnlyMultiNodeFullApiSelfTest # lockingEnabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1549) Optimize portable object fields write in non-raw mode.
Vladimir Ozerov created IGNITE-1549: --- Summary: Optimize portable object fields write in non-raw mode. Key: IGNITE-1549 URL: https://issues.apache.org/jira/browse/IGNITE-1549 Project: Ignite Issue Type: Task Components: general Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Blocker Fix For: ignite-1.5 Currently we write user fields as follows: 0 ,, 3 - field ID; 4 - field type; 5 ..8 - field len; 9 .. - the field itself. It can be optimized as follows: 1) Field len usually can be inferred from type. E.g., for int it is 4. 2) Frequently used constants can be written as separate types. E.g. INT - normal int, INT_0 - zero, etc. 3) Last, but not least, values should be encoded using "variable bytes" (and possibly ZigZag) algorithm. This will give us 2 bytes economy for ints and longs on average (I assume here that longs are usually bigger than 4 bytes, e.g. timestamps). *New types will be introduced:* 1) Booleans: BOOL_FALSE, BOOL_TRUE; 2) Bytes: BYTE_C0 => zero, BYTE_C1 => 1, BYTE_C1N => -1; 3) Shorts, chars: SHORT_C0, SHORT_C1, SHORT_C1N; 4) Ints: INT_C0, INT_C1, INT_C1N, INT_1 - int which fits into 1 byte, INT_1N - same for negative value, INT_2, INT_2N, INT_3, INT_3N, INT_3, INT_3N, INT_4, INT_4N. 5) Longs: same as ints, but have only 2, 4, 6 and 8 byte count discriminators to avoid excessive calculations. It means that instead of 6 integer types previously, we will have 2 + 3 + 3 + 3 + 11 + 11 = 32 types. To avoid excessive switches or (even worse) array/map lookups to understand what the type is, we can divide all types space (256) into two parts: optimized and non-optimized. Optimized space will have the MSB set to 1, and mentioned ~30 optimized types (or some of them) are located there. For floats and doubles we simply infer length. For primitive arrays we do not write field length and then arrya length, but only array length. *Expected compaction*: bool: 10 -> 5 bytes (50%); byte: 10 -> 5-6 bytes (45%); short, char: 11 -> 5-7 bytes, 7 on average (35%); int: 13 -> 5-9 bytes, 7 on average (45%). long: 17 -> 5-13 bytes, 11 on average (35%). float: 13 -> 9 bytes (30%); double: 17 -> 13 bytes (25%); *Expected CPU overhead on writes:* Bool, float, double: - Byte, short, char: zero check, sign check; Int, long: two (shift + OR)s to understand bytes count, if small - "zero" and "one" checks, if big - sign check, *Expected CPU overhead on reads:* One additional branch between optimzied and non-optimized spaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-873) Failed to execute compound future reducer
[
https://issues.apache.org/jira/browse/IGNITE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov resolved IGNITE-873.
-
Resolution: Fixed
Assignee: (was: Alexey Goncharuk)
Issue was fixed in ignite-1.4.
> Failed to execute compound future reducer
> -
>
> Key: IGNITE-873
> URL: https://issues.apache.org/jira/browse/IGNITE-873
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
>
> # start node with load + standalone node (used cache with offheap and
> FifoEvictionPolicy)
> # wait for a seconds
> # start one more standalone node and get in its console:
> {code}
> [15:07:16] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Collection reducer: [], init=false,
> res=java.util.concurrent.atomic.AtomicMarkableReference@48ccbaf5, err=null,
> done=true, cancelled=false, err=java.lang.IllegalStateException: Already
> swapped: 1253219600, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6727)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:304)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:295)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:204)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.add(GridCompoundFuture.java:165)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.map(GridDhtGetFuture.java:203)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.init(GridDhtGetFuture.java:157)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.getDhtAsync(GridDhtCacheAdapter.java:599)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearGetRequest(GridDhtCacheAdapter.java:615)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:177)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:175)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:325)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:156)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:124)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
> 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)
> Caused by: java.lang.IllegalStateException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOffheap.onSwap(GridH2KeyValueRowOffheap.java:202)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwapUnswap(GridH2Table.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwap(GridH2Table.java:110)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onSwap(IgniteH2Indexing.java:455)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onSwap(GridQueryProcessor.java:850)
> at
>
[jira] [Assigned] (IGNITE-873) Failed to execute compound future reducer
[
https://issues.apache.org/jira/browse/IGNITE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-873:
---
Assignee: Pavel Konstantinov
Pavel, please check if issue was fixed.
> Failed to execute compound future reducer
> -
>
> Key: IGNITE-873
> URL: https://issues.apache.org/jira/browse/IGNITE-873
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>
> # start node with load + standalone node (used cache with offheap and
> FifoEvictionPolicy)
> # wait for a seconds
> # start one more standalone node and get in its console:
> {code}
> [15:07:16] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Collection reducer: [], init=false,
> res=java.util.concurrent.atomic.AtomicMarkableReference@48ccbaf5, err=null,
> done=true, cancelled=false, err=java.lang.IllegalStateException: Already
> swapped: 1253219600, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6727)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:304)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:295)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:204)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.add(GridCompoundFuture.java:165)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.map(GridDhtGetFuture.java:203)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.init(GridDhtGetFuture.java:157)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.getDhtAsync(GridDhtCacheAdapter.java:599)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearGetRequest(GridDhtCacheAdapter.java:615)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:177)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:175)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:325)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:156)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:124)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
> 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)
> Caused by: java.lang.IllegalStateException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOffheap.onSwap(GridH2KeyValueRowOffheap.java:202)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwapUnswap(GridH2Table.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwap(GridH2Table.java:110)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onSwap(IgniteH2Indexing.java:455)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onSwap(GridQueryProcessor.java:850)
> at
>
[jira] [Commented] (IGNITE-1127) Query with result size more then one page doesn't increase Query executions count metric
[ https://issues.apache.org/jira/browse/IGNITE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907946#comment-14907946 ] Andrey Gura commented on IGNITE-1127: - Pavel, see ticket history: ticket was assigned to you by Sergi after review because you are reporter. Code always merges to master branch if not specified another. > Query with result size more then one page doesn't increase Query executions > count metric > - > > Key: IGNITE-1127 > URL: https://issues.apache.org/jira/browse/IGNITE-1127 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Pavel Konstantinov >Assignee: Andrey Gura > Fix For: ignite-1.5 > > Attachments: master_d9acbd1_ignite-1127.patch > > > Queries for partitioned caches and limited page size doesn't increase > executions count metric in case if not all records was actually fetched by > client code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-780) Fix test TcpClientDiscoverySelfTest.testClientNodeLeaveOneServer
[ https://issues.apache.org/jira/browse/IGNITE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-780. - Resolution: Fixed Assignee: (was: Valentin Kulichenko) Test pass now. > Fix test TcpClientDiscoverySelfTest.testClientNodeLeaveOneServer > - > > Key: IGNITE-780 > URL: https://issues.apache.org/jira/browse/IGNITE-780 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-4 >Reporter: Irina Vasilinets > > Test starts failing after IGNITE-714 merge. > Unmute test after fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-780) Fix test TcpClientDiscoverySelfTest.testClientNodeLeaveOneServer
[ https://issues.apache.org/jira/browse/IGNITE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-780. --- > Fix test TcpClientDiscoverySelfTest.testClientNodeLeaveOneServer > - > > Key: IGNITE-780 > URL: https://issues.apache.org/jira/browse/IGNITE-780 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-4 >Reporter: Irina Vasilinets > > Test starts failing after IGNITE-714 merge. > Unmute test after fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908510#comment-14908510
]
ASF GitHub Bot commented on IGNITE-530:
---
Github user sylentprayer closed the pull request at:
https://github.com/apache/ignite/pull/102
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Lalit Kumar Jha
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1493) Fatal exception is thrown during queue instantiation when using Ignite with an HP-UX machine.
[
https://issues.apache.org/jira/browse/IGNITE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908587#comment-14908587
]
Nicholas Dzwill commented on IGNITE-1493:
-
I see that issue IGNITE-1526 is scheduled for release 1.5, is there any work
being done with regard to the usage of Unsafe in the 1.4 release? We are
hoping to get a stable version of the product to use in our HP-UX environments
in the near future.
We are also working with HP on this issue to see if can be supported by the JDK
but have made no progress on that front yet.
Thank you for any update you can give me.
> Fatal exception is thrown during queue instantiation when using Ignite with
> an HP-UX machine.
> -
>
> Key: IGNITE-1493
> URL: https://issues.apache.org/jira/browse/IGNITE-1493
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Environment: * HP-UX B.11.31 IA64W machine
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
>Reporter: Nicholas Dzwill
>Priority: Blocker
> Attachments: ErrorLog.txt, server.log
>
>
> A fatal exception is thrown during queue instantiation when using an HP-UX
> B.11.31 IA64W machine.
> The environment is as follows:
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
> The error logged is as follows:
> * Current thread (01ab2800): JavaThread "main" [_thread_in_vm, id=23,
> lwp_id=3525570, stack(4e501000,4e601000)]
> * siginfo:si_signo=SIGBUS: si_errno=0, si_code=1 (BUS_ADRALN),
> si_addr=5e038d15
>
> The exception above means there is an "invalid address alignment" (writing to
> an odd memory location) when calling the following method:
> * Class: org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream
> * Method:
> {code:borderStyle=solid}
>/** {@inheritDoc} */
> @Override public void writeInt(int v) throws IOException {
> requestFreeSize(4);
> UNSAFE.putInt(bytes, byteArrOff + off, v); // byteArrOff + off =
> 17 when this exception is thrown
> onWrite(4);
> }
> {code}
>
> Basic setup - Ignite is configured with spring and pushed to the constructor
> of a class. That class uses this instance of Ignite to instantiate an
> IgniteQueue as follows:
> {code:borderStyle=solid}
> CollectionConfiguration configuration = new CollectionConfiguration();
> configuration.setCollocated(true);
> IgniteQueue queue = ignite.queue("queue", 0, configuration);
> {code}
>
> Partial stack:
> * Instantiating the queue calls:
> **
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.compatibleConfiguration()
>
> * Which in turn calls:
> ** org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke()
> * Leading to the fatal error when calling:
> **
> org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeInt()
> The error log has been attached with the stack trace of the error. The
> server log is also attached. We are running Ignite in a variety of
> environments and this issue only appears to exist in this specific
> environment and is consistently hit in the same place with no apparent
> work-around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908531#comment-14908531
]
Lalit Kumar Jha commented on IGNITE-530:
Added code style in IntelliJ and reformatted the code along with fixes for
suggessions in comments.
For mocking twitter, using WireMock as twitter's sample statuses API also
requires OAuth keys.
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Lalit Kumar Jha
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1552) Table function doesn't work properly in SQL query
Valentin Kulichenko created IGNITE-1552: --- Summary: Table function doesn't work properly in SQL query Key: IGNITE-1552 URL: https://issues.apache.org/jira/browse/IGNITE-1552 Project: Ignite Issue Type: Bug Components: cache Reporter: Valentin Kulichenko Assignee: Sergi Vladykin Priority: Critical Fix For: ignite-1.5 IN operator replacement query described in [1] doesn't seem to work properly. Test reproducing the issue is attached. [1]https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1552) Table function doesn't work properly in SQL query
[ https://issues.apache.org/jira/browse/IGNITE-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1552: Attachment: QueryInStatementTest.java > Table function doesn't work properly in SQL query > - > > Key: IGNITE-1552 > URL: https://issues.apache.org/jira/browse/IGNITE-1552 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Sergi Vladykin >Priority: Critical > Labels: user-request > Fix For: ignite-1.5 > > Attachments: QueryInStatementTest.java > > > IN operator replacement query described in [1] doesn't seem to work properly. > Test reproducing the issue is attached. > [1] > https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1552) Table function doesn't work properly in SQL query
[ https://issues.apache.org/jira/browse/IGNITE-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1552: Description: IN operator replacement query described in [1] doesn't seem to work properly. Test reproducing the issue is attached. [1] https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations was: IN operator replacement query described in [1] doesn't seem to work properly. Test reproducing the issue is attached. [1]https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations > Table function doesn't work properly in SQL query > - > > Key: IGNITE-1552 > URL: https://issues.apache.org/jira/browse/IGNITE-1552 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Sergi Vladykin >Priority: Critical > Labels: user-request > Fix For: ignite-1.5 > > > IN operator replacement query described in [1] doesn't seem to work properly. > Test reproducing the issue is attached. > [1] > https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1553) Optimize transaction prepare step when store is enabled
Alexey Goncharuk created IGNITE-1553:
Summary: Optimize transaction prepare step when store is enabled
Key: IGNITE-1553
URL: https://issues.apache.org/jira/browse/IGNITE-1553
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: ignite-1.4
Reporter: Alexey Goncharuk
Currently entries are enlisted in a database transaction after grid transaction
is in PREPARED state. We can do this in parallel in the following fashion
(pseudo-code):
{code}
fut = tx.prepareAsync();
db.write(tx.writes());
fut.get();
try {
db.commit();
tx.commit();
}
catch (Exception e) {
tx.rollback();
}
{code}
If this approach is applied, we should be able to reduce latency for
transactions when write-through is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1553) Optimize transaction prepare step when store is enabled
[
https://issues.apache.org/jira/browse/IGNITE-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-1553:
-
Issue Type: Improvement (was: Bug)
> Optimize transaction prepare step when store is enabled
> ---
>
> Key: IGNITE-1553
> URL: https://issues.apache.org/jira/browse/IGNITE-1553
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>
> Currently entries are enlisted in a database transaction after grid
> transaction is in PREPARED state. We can do this in parallel in the following
> fashion (pseudo-code):
> {code}
> fut = tx.prepareAsync();
> db.write(tx.writes());
> fut.get();
> try {
> db.commit();
>
> tx.commit();
> }
> catch (Exception e) {
> tx.rollback();
> }
> {code}
> If this approach is applied, we should be able to reduce latency for
> transactions when write-through is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1547) NPE if using HTTP REST
Pavel Konstantinov created IGNITE-1547:
--
Summary: NPE if using HTTP REST
Key: IGNITE-1547
URL: https://issues.apache.org/jira/browse/IGNITE-1547
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
Fix For: ignite-1.5
I'm tested Ignite Console SQL feature and got NPE on node start if web agent
trying to get cache information at this moment
{code}
[13:25:56,761][SEVERE][qtp79785210-70][GridJettyRestProtocol] Failed to process
HTTP request [action=/ignite, req=(GET
/ignite?cmd=top=true=false)@1215478528
org.eclipse.jetty.server.Request@
4872bb00]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
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)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:208)
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:107)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
... 4 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1547) NPE if using HTTP REST
[
https://issues.apache.org/jira/browse/IGNITE-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1547:
---
Description:
I'm tested Ignite Console SQL feature and got NPE on node start if web agent
trying to get cache information at this moment
To reproduce:
1) open Ignite web console (console.gridgain.com)
2) open SQL page
3) start the grid (you need to build 843 branch or you can get master if 843
already merged into it)
4) refresh SQL page during node start
{code}
[13:25:56,761][SEVERE][qtp79785210-70][GridJettyRestProtocol] Failed to process
HTTP request [action=/ignite, req=(GET
/ignite?cmd=top=true=false)@1215478528
org.eclipse.jetty.server.Request@
4872bb00]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
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)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:208)
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:107)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
... 4 more
{code}
was:
I'm tested Ignite Console SQL feature and got NPE on node start if web agent
trying to get cache information at this moment
{code}
[13:25:56,761][SEVERE][qtp79785210-70][GridJettyRestProtocol] Failed to process
HTTP request [action=/ignite, req=(GET
/ignite?cmd=top=true=false)@1215478528
org.eclipse.jetty.server.Request@
4872bb00]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
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)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:208)
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:107)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
... 4 more
{code}
> NPE if using HTTP REST
> --
>
> Key: IGNITE-1547
> URL: https://issues.apache.org/jira/browse/IGNITE-1547
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
>
> I'm tested Ignite Console SQL feature and got NPE on node start if web agent
> trying to get cache information at this moment
> To reproduce:
> 1) open Ignite web console (console.gridgain.com)
> 2) open SQL page
> 3) start the grid (you need to build 843 branch or you can get master if 843
> already merged into it)
> 4) refresh SQL page during node start
> {code}
> [13:25:56,761][SEVERE][qtp79785210-70][GridJettyRestProtocol] Failed to
> process HTTP request [action=/ignite, req=(GET
> /ignite?cmd=top=true=false)@1215478528
> org.eclipse.jetty.server.Request@
> 4872bb00]
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
>
[jira] [Updated] (IGNITE-1543) SqlQuery returns empty result set when custome PortableIdMapper
[
https://issues.apache.org/jira/browse/IGNITE-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1543:
Priority: Minor (was: Critical)
> SqlQuery returns empty result set when custome PortableIdMapper
> ---
>
> Key: IGNITE-1543
> URL: https://issues.apache.org/jira/browse/IGNITE-1543
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Minor
> Fix For: ignite-1.5
>
> Attachments: ClientTest.java
>
>
> Set custom {{PortableIdMapper}} for a type. Let this mapper to return some
> predefined id for this type (like 12345).
> Then execute SQL to get all the entries of this type. The query will return
> an empty result set.
> Seems that at some point of execution SQL engine or some other part of the
> platform uses default type to id mapping ignoring given {{PotableIdMapper}}.
> To reproduce:
> - Start a server node with portable marshaller enabled;
> - run the code attached (ClientTest.java).
> Add a test to our test suites.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1547) NPE if using HTTP REST
[
https://issues.apache.org/jira/browse/IGNITE-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Novikov updated IGNITE-1547:
---
Issue Type: Sub-task (was: Bug)
Parent: IGNITE-843
> NPE if using HTTP REST
> --
>
> Key: IGNITE-1547
> URL: https://issues.apache.org/jira/browse/IGNITE-1547
> Project: Ignite
> Issue Type: Sub-task
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
>
> I'm tested Ignite Console SQL feature and got NPE on node start if web agent
> trying to get cache information at this moment
> To reproduce:
> 1) open Ignite web console (console.gridgain.com)
> 2) open SQL page
> 3) start the grid (you need to build 843 branch or you can get master if 843
> already merged into it)
> 4) refresh SQL page during node start
> {code}
> [13:25:56,761][SEVERE][qtp79785210-70][GridJettyRestProtocol] Failed to
> process HTTP request [action=/ignite, req=(GET
> /ignite?cmd=top=true=false)@1215478528
> org.eclipse.jetty.server.Request@
> 4872bb00]
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> 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)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:208)
> at
> org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:107)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1543) SqlQuery returns empty result set when custome PortableIdMapper
[
https://issues.apache.org/jira/browse/IGNITE-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1543:
Assignee: Vladimir Ozerov
> SqlQuery returns empty result set when custome PortableIdMapper
> ---
>
> Key: IGNITE-1543
> URL: https://issues.apache.org/jira/browse/IGNITE-1543
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: ignite-1.5
>
> Attachments: ClientTest.java
>
>
> Set custom {{PortableIdMapper}} for a type. Let this mapper to return some
> predefined id for this type (like 12345).
> Then execute SQL to get all the entries of this type. The query will return
> an empty result set.
> Seems that at some point of execution SQL engine or some other part of the
> platform uses default type to id mapping ignoring given {{PotableIdMapper}}.
> To reproduce:
> - Start a server node with portable marshaller enabled;
> - run the code attached (ClientTest.java).
> Add a test to our test suites.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-809) Old value can be missed for tx near cache entry
[
https://issues.apache.org/jira/browse/IGNITE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-809:
---
Assignee: Alexey Goncharuk (was: Semen Boikov)
Looks like this is failure scenario (all operations for the same key):
- put some value in cache from primary node
- start two invoke transactions: tx1 from primary node, tx2 from near node
- primary receives GridNearTxPrepareRequest for tx2, adds near node as reader,
but tx2 is not finished yet
- primary maps tx1, sees that there is reader, GridNearTxRemote is
created/committed on near node, but old value is not passed on near node
Alexey, please take a look.
> Old value can be missed for tx near cache entry
> ---
>
> Key: IGNITE-809
> URL: https://issues.apache.org/jira/browse/IGNITE-809
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Alexey Goncharuk
> Labels: failedtest
> Fix For: ignite-1.5
>
>
> GridCacheMultinodeUpdateNearEnabledSelfTest fails.
> {noformat}
> junit.framework.AssertionFailedError: Got null in processor.
> at
> org.apache.ignite.internal.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest.testInvoke(GridCacheMultinodeUpdateAbstractSelfTest.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1361)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1304)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-809) Old value can be missed for tx near cache entry
[
https://issues.apache.org/jira/browse/IGNITE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-809:
Fix Version/s: ignite-1.5
> Old value can be missed for tx near cache entry
> ---
>
> Key: IGNITE-809
> URL: https://issues.apache.org/jira/browse/IGNITE-809
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Semen Boikov
> Labels: failedtest
> Fix For: ignite-1.5
>
>
> GridCacheMultinodeUpdateNearEnabledSelfTest fails.
> {noformat}
> junit.framework.AssertionFailedError: Got null in processor.
> at
> org.apache.ignite.internal.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest.testInvoke(GridCacheMultinodeUpdateAbstractSelfTest.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1361)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1304)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-801) [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-801:
Issue Type: Sub-task (was: Bug)
Parent: IGNITE-1345
> [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
>
>
> Key: IGNITE-801
> URL: https://issues.apache.org/jira/browse/IGNITE-801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Denis Magda
> Labels: failedtest
> Fix For: ignite-1.5
>
> Attachments: ignite-801.patch
>
>
> See GG-5306
> http://94.72.60.102/viewLog.html?buildId=113217=bt6=buildResultsDiv
> {noformat}
> 2013-05-31 10:39:07
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode):
> "Attach Listener" daemon prio=10 tid=0x03a94800 nid=0x648 waiting on
> condition [0x]
>java.lang.Thread.State: RUNNABLE
> "tcp-disco-sock-reader-#2408%a940475f-1965-484a-8a43-0a1fcc3bf292" prio=10
> tid=0x7f06f8b1a000 nid=0x42d runnable [0x7f0702d84000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerInputStreamWrapper.read(GridJdkMarshallerInputStreamWrapper.java:47)
> at
> java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2308)
> at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2321)
> at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2792)
> at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:799)
> at java.io.ObjectInputStream.init(ObjectInputStream.java:299)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerObjectInputStream.init(GridJdkMarshallerObjectInputStream.java:30)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshaller.unmarshal(GridJdkMarshaller.java:115)
> at
> org.gridgain.grid.spi.discovery.tcp.GridTcpDiscoverySpi$SocketReader.body(GridTcpDiscoverySpi.java:3985)
> at org.gridgain.grid.spi.GridSpiThread.run(GridSpiThread.java:56)
> "Thread-1905" prio=10 tid=0x7f06f8268000 nid=0x428 waiting on condition
> [0x7f06e1f29000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked 0x00078a53c600 (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked 0x00078a473b60 (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "Thread-1911" prio=10 tid=0x026b1000 nid=0x420 waiting on condition
> [0x7f06e6af4000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked 0x000789b76068 (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked 0x00078a4738f8 (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "SIGTERM handler" daemon prio=10 tid=0x01ec2800 nid=0x41e in
> Object.wait() [0x7f06e8316000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> - locked 0x00078a473948 (a
> org.gridgain.grid.GridFactory$GridNamedInstance$2)
> at java.lang.Thread.join(Thread.java:1332)
> at
> java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:106)
> at
> java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
> at java.lang.Shutdown.runHooks(Shutdown.java:123)
> at java.lang.Shutdown.sequence(Shutdown.java:167)
>
[jira] [Updated] (IGNITE-803) [Test] DataStructures failover tests fail with partitioned cache
[ https://issues.apache.org/jira/browse/IGNITE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-803: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1345 > [Test] DataStructures failover tests fail with partitioned cache > > > Key: IGNITE-803 > URL: https://issues.apache.org/jira/browse/IGNITE-803 > Project: Ignite > Issue Type: Sub-task > Environment: See GG-2699 >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: failedtest > > See GG-2699 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-808) invokeAll fails with ClassCastException on unstable topology
[ https://issues.apache.org/jira/browse/IGNITE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-808: Summary: invokeAll fails with ClassCastException on unstable topology (was: [Test] GridReplicatedTxPreloadTest fails) > invokeAll fails with ClassCastException on unstable topology > > > Key: IGNITE-808 > URL: https://issues.apache.org/jira/browse/IGNITE-808 > Project: Ignite > Issue Type: Sub-task >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: failedtest > Fix For: ignite-1.5 > > > GridReplicatedTxPreloadTest fails. > See gg-7434 already fixed, but tests fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1127) Query with result size more then one page doesn't increase Query executions count metric
[ https://issues.apache.org/jira/browse/IGNITE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-1127: --- Assignee: Pavel Konstantinov (was: Andrey Gura) > Query with result size more then one page doesn't increase Query executions > count metric > - > > Key: IGNITE-1127 > URL: https://issues.apache.org/jira/browse/IGNITE-1127 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: master_d9acbd1_ignite-1127.patch > > > Queries for partitioned caches and limited page size doesn't increase > executions count metric in case if not all records was actually fetched by > client code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes
[ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-584: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1345 > Need to make sure that scan query returns consistent results on topology > changes > > > Key: IGNITE-584 > URL: https://issues.apache.org/jira/browse/IGNITE-584 > Project: Ignite > Issue Type: Sub-task >Reporter: Artem Shutak > Labels: failedtest > > Consistent results on topology changes was implemented for sql queries, but > looks like it still does not work for scan queries. > This affects 'cache set' tests since set uses scan query for set iteration > (to be unmuted on TC): > GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and > testNodeJoinsAndLeavesCollocated; > Also see todos here GridCacheSetFailoverAbstractSelfTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-80) Hangs on queue creation in multinode tests
[ https://issues.apache.org/jira/browse/IGNITE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-80: -- Assignee: Semen Boikov (was: Alexey Goncharuk) > Hangs on queue creation in multinode tests > -- > > Key: IGNITE-80 > URL: https://issues.apache.org/jira/browse/IGNITE-80 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov >Priority: Blocker > Fix For: ignite-1.5 > > > Tests hang on TC and locally: > GridCachePartitionedQueueCreateMultiNodeSelfTest, > GridCachePartitionedAtomicQueueCreateMultiNodeSelfTest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-80) Hangs on queue creation in multinode tests
[
https://issues.apache.org/jira/browse/IGNITE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907979#comment-14907979
]
Semen Boikov commented on IGNITE-80:
Now tests fail sometimes with error, looks like race with data structure cache
initialization:
{noformat}
Failure in thread: Thread [id=21, name=createQueue-8]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getCollection(DataStructuresProcessor.java:986)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.queue(DataStructuresProcessor.java:851)
at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:2900)
at
org.apache.ignite.internal.processors.cache.datastructures.partitioned.GridCachePartitionedQueueCreateMultiNodeSelfTest$1.call(GridCachePartitionedQueueCreateMultiNodeSelfTest.java:133)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}
> Hangs on queue creation in multinode tests
> --
>
> Key: IGNITE-80
> URL: https://issues.apache.org/jira/browse/IGNITE-80
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Tests hang on TC and locally:
> GridCachePartitionedQueueCreateMultiNodeSelfTest,
> GridCachePartitionedAtomicQueueCreateMultiNodeSelfTest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-627) Inconsistent value in near cache
[ https://issues.apache.org/jira/browse/IGNITE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-627: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1345 > Inconsistent value in near cache > > > Key: IGNITE-627 > URL: https://issues.apache.org/jira/browse/IGNITE-627 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov >Priority: Critical > > This scenario is possible in atomic cache with near cache enabled: > - key is updated concurrently from near and primary node > - primary node first executes update request from near node, registers it as > reader and sends GridNearAtomicUpdateResponse to near node > - then primary node executes second update, sees that there is a reader and > sends GridDhtAtomicUpdateRequest to near node > - GridDhtAtomicUpdateRequest is handled first on near node (see > GridNearAtomicCache.processDhtAtomicUpdateRequest), it tries to peek entry, > it is not created yet and it is considered as evicted, updated is skipped and > reader will be removed on primary node > - then near node handles GridNearAtomicUpdateResponse and creates entry with > incorrect value > Tests > GridCacheValueConsistencyAtomicPrimaryWriteOrderNearEnabledSelfTest.testPutRemoveConsistencyMultithreaded > and testPutConsistencyMultithreaded fail from time to time because of this > issue. > Most probably there is similar issue in transactional cache since > GridCacheValueConsistencyTransactionalNearEnabledSelfTest also fails from > time to time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1294) Assertion in TCP communication SPI: client already created
[
https://issues.apache.org/jira/browse/IGNITE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov updated IGNITE-1294:
--
Issue Type: Bug (was: Sub-task)
Parent: (was: IGNITE-1345)
> Assertion in TCP communication SPI: client already created
> --
>
> Key: IGNITE-1294
> URL: https://issues.apache.org/jira/browse/IGNITE-1294
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Denis Magda
> Fix For: ignite-1.5
>
> Attachments: ignite-1294.patch
>
>
> Observed this failure on TC in master branch:
> {code}
> [19:39:53]W: [org.apache.ignite:ignite-core]
> java.lang.AssertionError: Client already created [
> node=TcpDiscoveryNode [id=00db22a2-37de-4d41-9a81-1b3ccb7a3000,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1440434393018, loc=false,
> ver=1.4.1#19700101-sha1:, isClient=false],
> client=GridShmemCommunicationClient
> [shmem=IpcSharedMemoryClientEndpoint [inSpace=IpcSharedMemorySpace
> [opSize=262144, shmemPtr=139828001624128, shmemId=815824901, semId=696811527,
> closed=false, isReader=true, writerPid=23710, readerPid=23710,
> tokFileName=/opt/TeamcityAgent/temp/buildTmp/ignite/work/ipc/shmem/00db22a2-37de-4d41-9a81-1b3ccb7a3000-23710/gg-shmem-space-1087-23710-262144,
> closed=false], outSpace=IpcSharedMemorySpace [opSize=262144,
> shmemPtr=139828001357888, shmemId=815792132, semId=696778758, closed=false,
> isReader=false, writerPid=23710, readerPid=23710,
> tokFileName=/opt/TeamcityAgent/temp/buildTmp/ignite/work/ipc/shmem/00db22a2-37de-4d41-9a81-1b3ccb7a3000-23710/gg-shmem-space-1086-23710-262144,
> closed=false], checkIn=true, checkOut=true],
> writeBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192],
> formatter=org.apache.ignite.internal.managers.communication.GridIoManager$2@489a1849,
> super=GridAbstractCommunicationClient [lastUsed=1440434393133, reserves=0]],
> oldClient=GridTcpNioCommunicationClient [ses=GridSelectorNioSessionImpl
> [selectorIdx=0, queueSize=0, writeBuf=java.nio.DirectByteBuffer[pos=0
> lim=32768 cap=32768], readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768
> cap=32768], recovery=GridNioRecoveryDescriptor [acked=0, resendCnt=0,
> rcvCnt=2, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=00db22a2-37de-4d41-9a81-1b3ccb7a3000, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1440434393018, loc=false, ver=1.4.1#19700101-sha1:,
> isClient=false], connected=true, connectCnt=0, queueLimit=5120],
> super=GridNioSessionImpl [locAddr=/127.0.0.1:45254, rmtAddr=/127.0.0.1:53055,
> createTime=1440434393174, closeTime=0, bytesSent=26, bytesRcvd=345,
> sndSchedTime=1440434393174, lastSndTime=1440434393174,
> lastRcvTime=1440434393184, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter
> [parser=org.apache.ignite.internal.util.nio.GridDirectParser@1cc9616c,
> directMode=true], GridConnectionBytesVerifyFilter], accepted=true]],
> super=GridAbstractCommunicationClient [lastUsed=1440434393174, reserves=0]]]
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1909)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1840)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1806)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1020)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1168)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:598)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:932)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:973)
> [19:39:53]W: [org.apache.ignite:ignite-core]at
>
[jira] [Created] (IGNITE-1550) Optimize "direct" message serialization.
Vladimir Ozerov created IGNITE-1550: --- Summary: Optimize "direct" message serialization. Key: IGNITE-1550 URL: https://issues.apache.org/jira/browse/IGNITE-1550 Project: Ignite Issue Type: Task Components: general Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: ignite-1.5 *Overview* Ignite use "direct" serialization to speed up marshalling of internal classes avoiding byte array copying. This mechanism can be improved significantly on class-by-class basis reducing message size by 10-30% in different cases. *Implementation* 1) Definte the list of possible optimizations. At the very least it includes: - Var-length integer encoding; - Special cases (constants, positive-only values, low amount of significant bits, etc.); - Efficient writes of "nulls"; - Write groups of relates fields with boolean switch if they are either null or not-null at the same time. 2) Determine what to optimize. This can be done on class-by-class basis for each of ~180 messages. Better approach will be to enable tracking of written values inside DirectMessageWriter. Then we should run Ignite with differnet payloads and identify fields which are good candidates for optimization. 3) Implement each optimziation. *Risks* Backward compatibility will be broken. We must either inform users about it, or support ability to use old non-optimized protocol version somehow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-873) Failed to execute compound future reducer
[
https://issues.apache.org/jira/browse/IGNITE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-873.
-
Not reproducing anymore.
> Failed to execute compound future reducer
> -
>
> Key: IGNITE-873
> URL: https://issues.apache.org/jira/browse/IGNITE-873
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>
> # start node with load + standalone node (used cache with offheap and
> FifoEvictionPolicy)
> # wait for a seconds
> # start one more standalone node and get in its console:
> {code}
> [15:07:16] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Collection reducer: [], init=false,
> res=java.util.concurrent.atomic.AtomicMarkableReference@48ccbaf5, err=null,
> done=true, cancelled=false, err=java.lang.IllegalStateException: Already
> swapped: 1253219600, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6727)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:304)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:295)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:204)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.add(GridCompoundFuture.java:165)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.map(GridDhtGetFuture.java:203)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.init(GridDhtGetFuture.java:157)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.getDhtAsync(GridDhtCacheAdapter.java:599)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearGetRequest(GridDhtCacheAdapter.java:615)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:177)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:175)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:325)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:156)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:124)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
> 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)
> Caused by: java.lang.IllegalStateException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOffheap.onSwap(GridH2KeyValueRowOffheap.java:202)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwapUnswap(GridH2Table.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwap(GridH2Table.java:110)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onSwap(IgniteH2Indexing.java:455)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onSwap(GridQueryProcessor.java:850)
> at
>
[jira] [Updated] (IGNITE-873) Failed to execute compound future reducer
[
https://issues.apache.org/jira/browse/IGNITE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-873:
--
Assignee: (was: Pavel Konstantinov)
> Failed to execute compound future reducer
> -
>
> Key: IGNITE-873
> URL: https://issues.apache.org/jira/browse/IGNITE-873
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
>
> # start node with load + standalone node (used cache with offheap and
> FifoEvictionPolicy)
> # wait for a seconds
> # start one more standalone node and get in its console:
> {code}
> [15:07:16] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Collection reducer: [], init=false,
> res=java.util.concurrent.atomic.AtomicMarkableReference@48ccbaf5, err=null,
> done=true, cancelled=false, err=java.lang.IllegalStateException: Already
> swapped: 1253219600, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6727)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:304)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:295)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:204)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.add(GridCompoundFuture.java:165)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.map(GridDhtGetFuture.java:203)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetFuture.init(GridDhtGetFuture.java:157)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.getDhtAsync(GridDhtCacheAdapter.java:599)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearGetRequest(GridDhtCacheAdapter.java:615)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:177)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$3.apply(GridDhtAtomicCache.java:175)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:325)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:156)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:124)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
> 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)
> Caused by: java.lang.IllegalStateException: Already swapped: 1253219600
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOffheap.onSwap(GridH2KeyValueRowOffheap.java:202)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwapUnswap(GridH2Table.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwap(GridH2Table.java:110)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onSwap(IgniteH2Indexing.java:455)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onSwap(GridQueryProcessor.java:850)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.onSwap(GridCacheQueryManager.java:297)
> at
>
[jira] [Updated] (IGNITE-500) GridCacheLoadingConcurrentGridStartTest fails
[ https://issues.apache.org/jira/browse/IGNITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-500: Issue Type: Sub-task (was: Task) Parent: IGNITE-1345 > GridCacheLoadingConcurrentGridStartTest fails > - > > Key: IGNITE-500 > URL: https://issues.apache.org/jira/browse/IGNITE-500 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > Labels: user-request > Fix For: ignite-1.5 > > Attachments: ignite-500.log > > > http://apacheignite.readme.io/v1.0/discuss/550865a8e35e9c3b0083af3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-80) Hangs on queue creation in multinode tests
[ https://issues.apache.org/jira/browse/IGNITE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907981#comment-14907981 ] Semen Boikov commented on IGNITE-80: Also I see that DataStructuresProcessor.compatibleConfiguration uses 'utilityDataCache.localPeek', but localPeek will not work on client nodes, probably need fix this place. > Hangs on queue creation in multinode tests > -- > > Key: IGNITE-80 > URL: https://issues.apache.org/jira/browse/IGNITE-80 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov >Priority: Blocker > Fix For: ignite-1.5 > > > Tests hang on TC and locally: > GridCachePartitionedQueueCreateMultiNodeSelfTest, > GridCachePartitionedAtomicQueueCreateMultiNodeSelfTest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1525) Return value for cache operation can be lost with onePhaseCommit
[ https://issues.apache.org/jira/browse/IGNITE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-1525: - Description: Looks like with onePhaseCommit return value for cache operation can be lost if primary node fails, GridNearTxPrepareResponse with return value is not received, but transaction executes 'check backup' step and finishes without error. Reproduces in IgniteCachePutRetryTransactionalSelfTest.testInvoke, also added one more test to check return value IgniteCachePutRetryTransactionalSelfTest.testGetAndPut. Please unmute tests on TC when fixed. was: Looks like with onePhaseCommit return value for cache operation can be lost if primary node fails, GridNearTxPrepareResponse with return value is not received, but transaction executes 'check backup' step and finishes without error. Reproduces in IgniteCachePutRetryTransactionalSelfTest.testInvoke, also added one more test to check return value IgniteCachePutRetryTransactionalSelfTest.testGetAndPut. > Return value for cache operation can be lost with onePhaseCommit > > > Key: IGNITE-1525 > URL: https://issues.apache.org/jira/browse/IGNITE-1525 > Project: Ignite > Issue Type: Sub-task > Components: cache >Affects Versions: ignite-1.4 >Reporter: Semen Boikov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: ignite-1.5 > > > Looks like with onePhaseCommit return value for cache operation can be lost > if primary node fails, GridNearTxPrepareResponse with return value is not > received, but transaction executes 'check backup' step and finishes without > error. > Reproduces in IgniteCachePutRetryTransactionalSelfTest.testInvoke, also added > one more test to check return value > IgniteCachePutRetryTransactionalSelfTest.testGetAndPut. > Please unmute tests on TC when fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-827) [Test] GridCacheCrossCacheQuerySelfTest # testLoop and # testTwoStep were disabled
[ https://issues.apache.org/jira/browse/IGNITE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-827. - Resolution: Fixed These tests were removed. > [Test] GridCacheCrossCacheQuerySelfTest # testLoop and # testTwoStep were > disabled > -- > > Key: IGNITE-827 > URL: https://issues.apache.org/jira/browse/IGNITE-827 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridCacheCrossCacheQuerySelfTest # testLoop and # testTwoStep were disabled. > They has to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1520) IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of IgfsMetaManager#moveNonTx
[ https://issues.apache.org/jira/browse/IGNITE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky resolved IGNITE-1520. - Resolution: Won't Fix > IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of > IgfsMetaManager#moveNonTx > - > > Key: IGNITE-1520 > URL: https://issues.apache.org/jira/browse/IGNITE-1520 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > In IGNITE-586 we implenmented method IgfsMetaManager#move that performs > generic move work. Since IgfsMetaManager#renameDual has similar functionality > , we should refactor code to reuse IgfsMetaManager#move in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1520) IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of IgfsMetaManager#moveNonTx
[ https://issues.apache.org/jira/browse/IGNITE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky closed IGNITE-1520. --- > IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of > IgfsMetaManager#moveNonTx > - > > Key: IGNITE-1520 > URL: https://issues.apache.org/jira/browse/IGNITE-1520 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > In IGNITE-586 we implenmented method IgfsMetaManager#move that performs > generic move work. Since IgfsMetaManager#renameDual has similar functionality > , we should refactor code to reuse IgfsMetaManager#move in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-1520) IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of IgfsMetaManager#moveNonTx
[ https://issues.apache.org/jira/browse/IGNITE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky reopened IGNITE-1520: - > IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of > IgfsMetaManager#moveNonTx > - > > Key: IGNITE-1520 > URL: https://issues.apache.org/jira/browse/IGNITE-1520 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > In IGNITE-586 we implenmented method IgfsMetaManager#move that performs > generic move work. Since IgfsMetaManager#renameDual has similar functionality > , we should refactor code to reuse IgfsMetaManager#move in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1520) IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of IgfsMetaManager#moveNonTx
[ https://issues.apache.org/jira/browse/IGNITE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky resolved IGNITE-1520. - Resolution: Fixed Looks like the refactoring will be done in another way, do not fix. > IGFS: IgfsMetaManager#renameDual should use IgfsMetaManager#move instead of > IgfsMetaManager#moveNonTx > - > > Key: IGNITE-1520 > URL: https://issues.apache.org/jira/browse/IGNITE-1520 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > In IGNITE-586 we implenmented method IgfsMetaManager#move that performs > generic move work. Since IgfsMetaManager#renameDual has similar functionality > , we should refactor code to reuse IgfsMetaManager#move in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-868) Fix GridUpdateNotifierSelfTest.testNotifier
[ https://issues.apache.org/jira/browse/IGNITE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-868. - Resolution: Fixed Test pass now, closing. > Fix GridUpdateNotifierSelfTest.testNotifier > > > Key: IGNITE-868 > URL: https://issues.apache.org/jira/browse/IGNITE-868 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-5 >Reporter: Irina Vasilinets >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-868) Fix GridUpdateNotifierSelfTest.testNotifier
[ https://issues.apache.org/jira/browse/IGNITE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-868. --- > Fix GridUpdateNotifierSelfTest.testNotifier > > > Key: IGNITE-868 > URL: https://issues.apache.org/jira/browse/IGNITE-868 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-5 >Reporter: Irina Vasilinets >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1548) Optimize portable object header.
Vladimir Ozerov created IGNITE-1548: --- Summary: Optimize portable object header. Key: IGNITE-1548 URL: https://issues.apache.org/jira/browse/IGNITE-1548 Project: Ignite Issue Type: Task Components: general Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Priority: Blocker Fix For: ignite-1.5 Currently portable object header takes 18 bytes: 1 - object type 1 - user flag 4 - type ID 4 - hash code 4 - length 4 - raw offset. The following optimizations can be applied: 1) User flag can be easilty merged into object type. (-1 byte) 2) In most cases only length or raw-offset exists, but not both. Remove one of them and encode state into the object type. (-4 bytes) 3) Length usually fit in 1-2 bytes. Encode it with "variable bytes" algo (-2-3 bytes). As a result we will shrink header size from 18 to 10-11 bytes. Encoded states will require 6 additional object types: 104 => system, with length 105 => system, with raw offset 106 => system, with both 107, 108, 109 - the same, but for user types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
