[jira] [Commented] (IGNITE-12178) DEBUG logging may throw exception from toString of tx objects
[
https://issues.apache.org/jira/browse/IGNITE-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938007#comment-16938007
]
Denis Magda commented on IGNITE-12178:
--
A similar issue was reported on the user list:
http://apache-ignite-users.70518.x6.nabble.com/Exception-during-exception-handling-td29464.html
> DEBUG logging may throw exception from toString of tx objects
> -
>
> Key: IGNITE-12178
> URL: https://issues.apache.org/jira/browse/IGNITE-12178
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> See
> https://stackoverflow.com/questions/57727242/apache-ignite-failed-to-create-string-representation-of-binary-object
> {code:java}
> 0
> I am getting below exception and not able to figure out what is wrong with
> the code.
> I have simplified my pojo classes which are to be persisted to ignite cache,
> but still the complexity remains.
> All my pojos are serializable but few of them have business logic code, dao,
> application context object. These objects can't be removed. Removing these
> things from the code will require whole code refractoring.
> class org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1022)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:864)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearSingleGetResponse.toString(GridNearSingleGetResponse.java:317)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1162)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1209)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:1003)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:938)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetRequest(GridDhtCacheAdapter.java:938)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$300(GridDhtAtomicCache.java:135)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$4.apply(GridDhtAtomicCache.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$4.apply(GridDhtAtomicCache.java:252)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:189)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.toString(BinaryObjectImpl.java:920)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
>
[jira] [Commented] (IGNITE-12228) Implement an Apache Beam runner on top of Ignite compute grid?
[ https://issues.apache.org/jira/browse/IGNITE-12228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937244#comment-16937244 ] Denis Magda commented on IGNITE-12228: -- [~romain.manni-bucau] are you willing to contribute? The dev community can help you along the way. > Implement an Apache Beam runner on top of Ignite compute grid? > -- > > Key: IGNITE-12228 > URL: https://issues.apache.org/jira/browse/IGNITE-12228 > Project: Ignite > Issue Type: Wish >Reporter: Romain Manni-Bucau >Priority: Major > > Apache Ignite provides a compute grid. > It is therefore feasible to use that to execute a DAG pipeline. > Therefore implementing a Apache Beam runner executing a DAG on an ignite > cluster would be very valuable for users and would provide a very interesting > alternative to Spark, Dataflow etc...which would be very valuable when using > data from ignite itself. > Hoping it can help, here is Hazelcast Jet implementation which is not that > far even if Jet is a bit more advanced in term of DAG support: > [https://github.com/apache/beam/tree/master/runners/jet-experimental/src/main/java/org/apache/beam/runners/jet] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937242#comment-16937242 ] Denis Magda commented on IGNITE-12054: -- [~NIzhikov], let's follow your original plan by producing 2 new modules. This modularization story will take a while. > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934832#comment-16934832
]
Denis Magda commented on IGNITE-12032:
--
[~levagafonov]
If this warning is generated on the server for all types of clients (JDBC,
ODBC, thin) then I would make the message generic as _"Client disconnected
abruptly due to network connection loss or because the connection was left open
on application shutdown."_
Anyway, feel free to send a pull-request.
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Assignee: Lev Agafonov
>Priority: Minor
> Labels: newbie, usability
> Fix For: 2.8
>
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12173) Fix http links
[
https://issues.apache.org/jira/browse/IGNITE-12173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930797#comment-16930797
]
Denis Magda commented on IGNITE-12173:
--
Looks good to me, please feel free to merge.
> Fix http links
> --
>
> Key: IGNITE-12173
> URL: https://issues.apache.org/jira/browse/IGNITE-12173
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7.5
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. [Apache Ignite|https://github.com/apache]
> #
> {{[http://h2database.com/m2-repo|https://github.com/apache/ignite/blob/6e9ec03659e5f35c0f18605079fbced1e42ad130/parent/pom.xml#L233]}}
> #
> {{[http://hadoop.apache.org/docs/current/api/|https://github.com/apache/ignite/blob/6e9ec03659e5f35c0f18605079fbced1e42ad130/parent/pom.xml#L339]}}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-10862) Introduce tool to free up space on a disc of unused memory pages
[ https://issues.apache.org/jira/browse/IGNITE-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929354#comment-16929354 ] Denis Magda commented on IGNITE-10862: -- [~agoncharuk] is this a fundamental problem in our architecture? If not to know all the details it sounds like each node needs to spawn a background thread that will be cleaning disk space. > Introduce tool to free up space on a disc of unused memory pages > > > Key: IGNITE-10862 > URL: https://issues.apache.org/jira/browse/IGNITE-10862 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.7 >Reporter: Vyacheslav Daradur >Priority: Critical > Fix For: 2.8 > > > At the current time, Ignite is not able to release occupied disc space even > if a significant amount of data was removed from IgniteCache. It disturbs our > users because they can't use hardware effectively, also it increases TCO. > *Use-cases:* > Let's imagine that we have used IgniteCache with enabled PDS during the time: > - hardware disc space has been occupied during growing up of an amount > of data, e.g. 100Gb; > - then, we removed non-actual data, e.g 50Gb, which became useless for us; > - disc space stopped growing up with new data, but it was not > released, and still took 100Gb, instead of expected 50Gb; > Another use case: > - a user extracts data from IgniteCache to store it in separate > IgniteCache or another store; > - disc still is occupied and the user is not able to store data in the > different cache at the same cluster because of disc limitation; > *Possible solutions:* > Introduce some kind of mechanics which will be able to shrink data in > IgniteCache and to free up space on a disc of mapped free memory pages. > A solution should take into account possible concurrent reads and updates of > data and indexes to maintain consistency. > Maybe, it makes sense to implement a tool to be offline at the first step > that means concurrent operations will be prohibited. > Strongly recommended discussing design on dev-list with Ignite experts before > the start of implementation. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928886#comment-16928886
]
Denis Magda commented on IGNITE-12032:
--
[~levagafonov], good catch. Just to confirm, do we see these error messages on
the server node side or on the client end (JDBC, ODBC)? I'd like to adjust the
message text a bit.
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Assignee: Lev Agafonov
>Priority: Major
> Labels: newbie, usability
> Fix For: 2.8
>
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12139) RPM for 2.7.5 release built from incorrect version
[
https://issues.apache.org/jira/browse/IGNITE-12139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928884#comment-16928884
]
Denis Magda commented on IGNITE-12139:
--
[~vveider], sure, please go ahead. I think that's the only way we can fix the
issue with the released version.
> RPM for 2.7.5 release built from incorrect version
> --
>
> Key: IGNITE-12139
> URL: https://issues.apache.org/jira/browse/IGNITE-12139
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7.5
>Reporter: Jan Kupec
>Assignee: Dmitriy Pavlov
>Priority: Minor
>
> The {{apache-ignite-2.7.5}} RPM found in the [official RPM
> repository|https://ignite.apache.org/download.cgi#rpm-package] has been built
> from commit *{{c9521338}}*, which is several weeks of development away from
> the head of the {{ignite-2.7.5}} release branch (*{{be4f2a15}}*) and
> apparently contains incompatible changes.
> Is this a result of a human error or an error in the automated build system?
> Can this easily be fixed?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928009#comment-16928009
]
Denis Magda commented on IGNITE-12032:
--
[~isapego], could you please step in?
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Priority: Major
> Labels: newbie, usability
> Fix For: 2.8
>
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928005#comment-16928005 ] Denis Magda commented on IGNITE-12054: -- [~NIzhikov], [~zaleslaw], how about creating the first separate Ignite module for Spark and release it independently? The module will be in its own repository and there are might be different branches for different versions. Ignite community will support and release only the latest version of Spark integration while the users can always build an old version from one of the branches. More details are recorded on this page: https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization If three of us agree, then we can restart discussion on the dev list, do a call with [~agoncharuk] and other community members and get down to the implementation. > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Assignee: Nikolay Izhikov >Priority: Blocker > Fix For: 2.8 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IGNITE-4604) Python: basic SQL Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-4604. --- > Python: basic SQL Grid API > -- > > Key: IGNITE-4604 > URL: https://issues.apache.org/jira/browse/IGNITE-4604 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Priority: Major > > Implement basic SQL Grid API similar to the scope covered by C++ which > includes SQL queries and DML. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (IGNITE-4604) Python: basic SQL Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-4604. - Resolution: Fixed Python Thin Client has been supported for Ignite: https://apacheignite.readme.io/docs/python-thin-client > Python: basic SQL Grid API > -- > > Key: IGNITE-4604 > URL: https://issues.apache.org/jira/browse/IGNITE-4604 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Priority: Major > > Implement basic SQL Grid API similar to the scope covered by C++ which > includes SQL queries and DML. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IGNITE-4603) Python: basic Data Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-4603. --- > Python: basic Data Grid API > --- > > Key: IGNITE-4603 > URL: https://issues.apache.org/jira/browse/IGNITE-4603 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Priority: Major > > Implement basic Data Grid API similar to the scope covered by C++: > https://apacheignite-cpp.readme.io/docs/data-grid -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (IGNITE-4602) Python: module and build scripts
[ https://issues.apache.org/jira/browse/IGNITE-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-4602. - Resolution: Fixed Python Thin Client has been supported for Ignite: https://apacheignite.readme.io/docs/python-thin-client > Python: module and build scripts > > > Key: IGNITE-4602 > URL: https://issues.apache.org/jira/browse/IGNITE-4602 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Priority: Major > > Create "ignite-python" module and implement a build procedure for it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (IGNITE-4601) Python: support binary format
[ https://issues.apache.org/jira/browse/IGNITE-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-4601. - Resolution: Fixed Python Thin Client has been supported for Ignite: https://apacheignite.readme.io/docs/python-thin-client > Python: support binary format > - > > Key: IGNITE-4601 > URL: https://issues.apache.org/jira/browse/IGNITE-4601 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Priority: Major > > Python client has to support binary format natively by implementing a binary > marshaller logic directly. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IGNITE-4601) Python: support binary format
[ https://issues.apache.org/jira/browse/IGNITE-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-4601. --- > Python: support binary format > - > > Key: IGNITE-4601 > URL: https://issues.apache.org/jira/browse/IGNITE-4601 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda >Priority: Major > > Python client has to support binary format natively by implementing a binary > marshaller logic directly. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-4600. --- > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Priority: Major > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927994#comment-16927994 ] Denis Magda commented on IGNITE-4600: - [~zyc], this ticket should be considered as outdated as long as Ignite already support Python: https://apacheignite.readme.io/docs/python-thin-client Please send an email to the dev list if you'd like to enhance the existing client anyhow. I'm closing this and all dependent tickets. > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Priority: Major > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12139) RPM for 2.7.5 release built from incorrect version
[
https://issues.apache.org/jira/browse/IGNITE-12139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927992#comment-16927992
]
Denis Magda commented on IGNITE-12139:
--
[~vveider], [~avinogradov], [~dpavlov], could you please check this issue?
> RPM for 2.7.5 release built from incorrect version
> --
>
> Key: IGNITE-12139
> URL: https://issues.apache.org/jira/browse/IGNITE-12139
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7.5
>Reporter: Jan Kupec
>Assignee: Dmitriy Pavlov
>Priority: Minor
>
> The {{apache-ignite-2.7.5}} RPM found in the [official RPM
> repository|https://ignite.apache.org/download.cgi#rpm-package] has been built
> from commit *{{c9521338}}*, which is several weeks of development away from
> the head of the {{ignite-2.7.5}} release branch (*{{be4f2a15}}*) and
> apparently contains incompatible changes.
> Is this a result of a human error or an error in the automated build system?
> Can this easily be fixed?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12146) Make timeout of network operations customizable
[ https://issues.apache.org/jira/browse/IGNITE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927989#comment-16927989 ] Denis Magda commented on IGNITE-12146: -- [~isapego], could you please step in and see what can be improved here? > Make timeout of network operations customizable > --- > > Key: IGNITE-12146 > URL: https://issues.apache.org/jira/browse/IGNITE-12146 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.7.5 >Reporter: Oleg Popov >Priority: Major > Labels: cpp > > I'm performing a data migration from MariaDB to Apache Ignite and I do bulk > insertions with help of a "converter". All works fine except of appearing of > a message at the end of operations: > *Can not send message to remote host: timeout* > but all data succefully placed into Ignite cluster. > Short investigation showed that default values of network operations are too > low in my case (do data migration, remember?). Default values: > [https://github.com/apache/ignite/blob/ignite-2.7.5/modules/platforms/cpp/thin-client/src/impl/data_router.h#L61] > > It would be much better to have an option to customize these values through > "IgniteClientConfiguration" (the python client has such option?). -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12149) apacheignite/web-agent:2.7.0 /2.6.0 both the images looks like corrupted.
[
https://issues.apache.org/jira/browse/IGNITE-12149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927987#comment-16927987
]
Denis Magda commented on IGNITE-12149:
--
[~kuaw26], [~greg.stachnick], could you please have a look at the issue?
> apacheignite/web-agent:2.7.0 /2.6.0 both the images looks like corrupted.
> --
>
> Key: IGNITE-12149
> URL: https://issues.apache.org/jira/browse/IGNITE-12149
> Project: Ignite
> Issue Type: Bug
>Reporter: Gaurav Agnihotri
>Priority: Blocker
>
> apacheignite/web-agent:2.7.0 /2.6.0 both the images looks like corrupted.
> giving error {{Failed to find agent property file: default.properties}} &
> {{You are using an older version of the agent. Please reload agent}}
> {{}}
>
> Log trace :-
> [2019-09-09 04:54:11,869][INFO ][main][AgentLauncher] Starting Apache Ignite
> Web Console Agent...
> [2019-09-09 04:54:12,482][WARN ][main][AgentLauncher] Failed to find agent
> property file: default.properties
>
> Agent configuration:
> User's security tokens : xyyF
> URI to Ignite node REST server: http://10.x.x.x:8080
> URI to Ignite Console server : http://frontend.web-console.svc.cluster.local
> Path to agent property file : default.properties
> Path to JDBC drivers folder : ./jdbc-drivers
> Demo mode : enabled
>
> [2019-09-09 04:54:13,566][INFO ][main][AgentLauncher] Connecting to:
> http://frontend.web-console.svc.cluster.local
> [2019-09-09 04:54:14,179][INFO ][EventThread][AgentLauncher] Connection
> established.
> [2019-09-09 04:54:14,373][ERROR][EventThread][AgentLauncher] You are using an
> older version of the agent. Please reload agent
> {{```}}
> Is there any working Image available?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12107) Docs: request setting IGNITE_HOME to permanent location in Docker
[ https://issues.apache.org/jira/browse/IGNITE-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919812#comment-16919812 ] Denis Magda commented on IGNITE-12107: -- [~Artem Budnikov], thanks a lot, excellent! Closing the ticket. > Docs: request setting IGNITE_HOME to permanent location in Docker > - > > Key: IGNITE-12107 > URL: https://issues.apache.org/jira/browse/IGNITE-12107 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.7.6 > > > Update Ignite Docker and Kubernetes documentation stating that IGNITE_HOME, > as well as WAL and persistent store directories, must point to the volumes > that are not erased or destroyed on restarts. Please refer to this thread for > more details: > http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IGNITE-12107) Docs: request setting IGNITE_HOME to permanent location in Docker
[ https://issues.apache.org/jira/browse/IGNITE-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-12107. > Docs: request setting IGNITE_HOME to permanent location in Docker > - > > Key: IGNITE-12107 > URL: https://issues.apache.org/jira/browse/IGNITE-12107 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.7.6 > > > Update Ignite Docker and Kubernetes documentation stating that IGNITE_HOME, > as well as WAL and persistent store directories, must point to the volumes > that are not erased or destroyed on restarts. Please refer to this thread for > more details: > http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12103) Change the default ignite work directory once again to avoid writing to ~/work
[
https://issues.apache.org/jira/browse/IGNITE-12103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919809#comment-16919809
]
Denis Magda commented on IGNITE-12103:
--
[~ilyak], sorry my bad. Just submitted the review.
> Change the default ignite work directory once again to avoid writing to ~/work
> --
>
> Key: IGNITE-12103
> URL: https://issues.apache.org/jira/browse/IGNITE-12103
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.7.6
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While testing 2.7.6-RC1 it came up that we no longer write data to
> /tmp/ignite/work, which is good, but now we would instead write to
> /home/username/work, which is bad. ~/work is a generic directory not linked
> to Ignite in any obvious way, and users will be puzzled by its appearance
> with possibilities of data loss or, even worse, their own documents loss if
> they happen to have something in Work dir and it gets clobbered/removed by
> accident.
> I suggest changing this default once more, to use either
> /home/username/ignite/{work,logs,etc} or ./ignite/{work,logs,etc} by
> leveraging user.dir property pointing to current working dir.
> Please note that user.dir has its own problems since it is supposed to not be
> changeable after JVM is up, but some code still tries to change it.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12103) Change the default ignite work directory once again to avoid writing to ~/work
[
https://issues.apache.org/jira/browse/IGNITE-12103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918941#comment-16918941
]
Denis Magda commented on IGNITE-12103:
--
[~ilyak], I left a minor comment in PR. The rest is good, thanks.
> Change the default ignite work directory once again to avoid writing to ~/work
> --
>
> Key: IGNITE-12103
> URL: https://issues.apache.org/jira/browse/IGNITE-12103
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.7.6
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While testing 2.7.6-RC1 it came up that we no longer write data to
> /tmp/ignite/work, which is good, but now we would instead write to
> /home/username/work, which is bad. ~/work is a generic directory not linked
> to Ignite in any obvious way, and users will be puzzled by its appearance
> with possibilities of data loss or, even worse, their own documents loss if
> they happen to have something in Work dir and it gets clobbered/removed by
> accident.
> I suggest changing this default once more, to use either
> /home/username/ignite/{work,logs,etc} or ./ignite/{work,logs,etc} by
> leveraging user.dir property pointing to current working dir.
> Please note that user.dir has its own problems since it is supposed to not be
> changeable after JVM is up, but some code still tries to change it.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12107) Docs: request setting IGNITE_HOME to permanent location in Docker
Denis Magda created IGNITE-12107: Summary: Docs: request setting IGNITE_HOME to permanent location in Docker Key: IGNITE-12107 URL: https://issues.apache.org/jira/browse/IGNITE-12107 Project: Ignite Issue Type: Bug Components: documentation Reporter: Denis Magda Fix For: 2.7.6 Update Ignite Docker and Kubernetes documentation stating that IGNITE_HOME, as well as WAL and persistent store directories, must point to the volumes that are not erased or destroyed on restarts. Please refer to this thread for more details: http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12106) Rework ignite binary metadata exception for ease of troubleshooting
Denis Magda created IGNITE-12106:
Summary: Rework ignite binary metadata exception for ease of
troubleshooting
Key: IGNITE-12106
URL: https://issues.apache.org/jira/browse/IGNITE-12106
Project: Ignite
Issue Type: Bug
Components: cache, persistence
Affects Versions: 2.7.5, 2.7.6
Reporter: Denis Magda
Fix For: 2.7.6
An exception of this kind happens regularly and its message doesn't suggest why
it took place and how to fix the issue:
{noformat}
Cannot find metadata for object with compact footer: 2097659979
{noformat}
See this thread for more details:
http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html
As a solution, let's rework this exception to ensure that the way like that
"Ignite work directory might be cleared on restarts. Ensure that IGNITE_HOME
doesn't point to a temp folder or any other folder that is destroyed/erased on
restarts. Presently, IGNITE_HOME points to..."
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-12101) IgniteQueue.removeAll throws NPE
[
https://issues.apache.org/jira/browse/IGNITE-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-12101:
-
Component/s: data structures
> IgniteQueue.removeAll throws NPE
>
>
> Key: IGNITE-12101
> URL: https://issues.apache.org/jira/browse/IGNITE-12101
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: Denis Magda
>Priority: Major
>
> See more details here:
> https://stackoverflow.com/questions/57473783/ignite-2-5-ignitequeue-removeall-throwing-npe
> {noformat}
> 2019-08-09 18:18:39,241 ERROR [Inbound-Main-Pool-13] [TransactionId:
> e5b5bfe3-5246-4d54-a4d6-acd550240e13 Request ID - 27845] [ APP=Server,
> ACTION=APP_PROCESS, USER=tsgops ] ProcessWorkflowProcessor - Error while
> processing CLIENT process
> class org.apache.ignite.IgniteException: Failed to serialize object
> [typeName=LinkedList]
>at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
>
>at
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueAdapter$QueueIterator.remove(GridCacheQueueAdapter.java:687)
>
>at
> java.util.AbstractCollection.removeAll(AbstractCollection.java:376)
>at
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueProxy.removeAll(GridCacheQueueProxy.java:180)
>
>at
> com.me.app.service.support.APPOrderProcessIgniteQueueService.removeAll(APPOrderProcessIgniteQueueService.java:63)
>
>at
> com.me.app.service.support.APPOrderContextProcessInputManager.removeAllFromCurrentProcessing(APPOrderContextProcessInputManager.java:201)
>
>at
> com.me.app.service.support.APPOrderContextProcessInputManager.lambda$removeAll$3(APPOrderContextProcessInputManager.java:100)
>
>at java.lang.Iterable.forEach(Iterable.java:75)
>at
> com.me.app.service.support.APPOrderContextProcessInputManager.removeAll(APPOrderContextProcessInputManager.java:100)
>
>at
> com.me.app.service.support.APPOrderContextProcessInputManager.removeAll(APPOrderContextProcessInputManager.java:90)
>
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.processOrders(ProcessWorkflowProcessor.java:602)
>
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$13(ProcessWorkflowProcessor.java:405)
>
>at java.util.HashMap.forEach(HashMap.java:1289)
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$14(ProcessWorkflowProcessor.java:368)
>
>at java.util.HashMap.forEach(HashMap.java:1289)
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$15(ProcessWorkflowProcessor.java:354)
>
>at java.util.HashMap.forEach(HashMap.java:1289)
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$16(ProcessWorkflowProcessor.java:345)
>
>at java.util.HashMap.forEach(HashMap.java:1289)
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.lambda$executeProcess$17(ProcessWorkflowProcessor.java:337)
>
>at java.util.HashMap.forEach(HashMap.java:1289)
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.executeProcess(ProcessWorkflowProcessor.java:330)
>
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.executeProcess(ProcessWorkflowProcessor.java:302)
>
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.lambda$processProcessFromQueue$6(ProcessWorkflowProcessor.java:282)
>
>at
> com.me.app.locking.support.IgniteLockingService.execute(IgniteLockingService.java:39)
>
>at
> com.me.app.locking.support.IgniteLockingService.execute(IgniteLockingService.java:68)
>
>at
> com.me.app.processor.support.ProcessWorkflowProcessor.processProcessFromQueue(ProcessWorkflowProcessor.java:281)
>
>at
> com.me.app.facade.listener.support.APPProcessEventListener.listen(APPProcessEventListener.java:49)
>
>at
> com.me.app.facade.listener.support.APPProcessEventListener.listen(APPProcessEventListener.java:19)
>
>at
> com.me.app.common.listener.support.AbstractEventListener.onMessage(AbstractEventListener.java:44)
>
>at
> com.me.app.common.listener.support.AbstractEventListener$$FastClassBySpringCGLIB$$f1379f74.invoke()
>
>at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>at
>
[jira] [Created] (IGNITE-12101) IgniteQueue.removeAll throws NPE
Denis Magda created IGNITE-12101:
Summary: IgniteQueue.removeAll throws NPE
Key: IGNITE-12101
URL: https://issues.apache.org/jira/browse/IGNITE-12101
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Denis Magda
See more details here:
https://stackoverflow.com/questions/57473783/ignite-2-5-ignitequeue-removeall-throwing-npe
{noformat}
2019-08-09 18:18:39,241 ERROR [Inbound-Main-Pool-13] [TransactionId:
e5b5bfe3-5246-4d54-a4d6-acd550240e13 Request ID - 27845] [ APP=Server,
ACTION=APP_PROCESS, USER=tsgops ] ProcessWorkflowProcessor - Error while
processing CLIENT process
class org.apache.ignite.IgniteException: Failed to serialize object
[typeName=LinkedList]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
at
org.apache.ignite.internal.processors.datastructures.GridCacheQueueAdapter$QueueIterator.remove(GridCacheQueueAdapter.java:687)
at
java.util.AbstractCollection.removeAll(AbstractCollection.java:376)
at
org.apache.ignite.internal.processors.datastructures.GridCacheQueueProxy.removeAll(GridCacheQueueProxy.java:180)
at
com.me.app.service.support.APPOrderProcessIgniteQueueService.removeAll(APPOrderProcessIgniteQueueService.java:63)
at
com.me.app.service.support.APPOrderContextProcessInputManager.removeAllFromCurrentProcessing(APPOrderContextProcessInputManager.java:201)
at
com.me.app.service.support.APPOrderContextProcessInputManager.lambda$removeAll$3(APPOrderContextProcessInputManager.java:100)
at java.lang.Iterable.forEach(Iterable.java:75)
at
com.me.app.service.support.APPOrderContextProcessInputManager.removeAll(APPOrderContextProcessInputManager.java:100)
at
com.me.app.service.support.APPOrderContextProcessInputManager.removeAll(APPOrderContextProcessInputManager.java:90)
at
com.me.app.processor.support.ProcessWorkflowProcessor.processOrders(ProcessWorkflowProcessor.java:602)
at
com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$13(ProcessWorkflowProcessor.java:405)
at java.util.HashMap.forEach(HashMap.java:1289)
at
com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$14(ProcessWorkflowProcessor.java:368)
at java.util.HashMap.forEach(HashMap.java:1289)
at
com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$15(ProcessWorkflowProcessor.java:354)
at java.util.HashMap.forEach(HashMap.java:1289)
at
com.me.app.processor.support.ProcessWorkflowProcessor.lambda$null$16(ProcessWorkflowProcessor.java:345)
at java.util.HashMap.forEach(HashMap.java:1289)
at
com.me.app.processor.support.ProcessWorkflowProcessor.lambda$executeProcess$17(ProcessWorkflowProcessor.java:337)
at java.util.HashMap.forEach(HashMap.java:1289)
at
com.me.app.processor.support.ProcessWorkflowProcessor.executeProcess(ProcessWorkflowProcessor.java:330)
at
com.me.app.processor.support.ProcessWorkflowProcessor.executeProcess(ProcessWorkflowProcessor.java:302)
at
com.me.app.processor.support.ProcessWorkflowProcessor.lambda$processProcessFromQueue$6(ProcessWorkflowProcessor.java:282)
at
com.me.app.locking.support.IgniteLockingService.execute(IgniteLockingService.java:39)
at
com.me.app.locking.support.IgniteLockingService.execute(IgniteLockingService.java:68)
at
com.me.app.processor.support.ProcessWorkflowProcessor.processProcessFromQueue(ProcessWorkflowProcessor.java:281)
at
com.me.app.facade.listener.support.APPProcessEventListener.listen(APPProcessEventListener.java:49)
at
com.me.app.facade.listener.support.APPProcessEventListener.listen(APPProcessEventListener.java:19)
at
com.me.app.common.listener.support.AbstractEventListener.onMessage(AbstractEventListener.java:44)
at
com.me.app.common.listener.support.AbstractEventListener$$FastClassBySpringCGLIB$$f1379f74.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:721)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
at
com.me.app.common.aop.aspect.MetricsTrackingAspect.trackMetrics(MetricsTrackingAspect.java:142)
at
[jira] [Commented] (IGNITE-12096) Ignite memory metrics incorrect on cache usage contraction
[
https://issues.apache.org/jira/browse/IGNITE-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914551#comment-16914551
]
Denis Magda commented on IGNITE-12096:
--
Collin, how about this metric that is designed to return the actual size of a
region - DataRegionMetricsMXBean.getOffheapUsedSize?
It's available since Ignite 2.5:
https://issues.apache.org/jira/browse/IGNITE-8078
Plus, we might need to restart a discussion here if the metric doesn't suit
your needs:
http://apache-ignite-developers.2346864.n4.nabble.com/Memory-usage-per-cache-td28470.html
> Ignite memory metrics incorrect on cache usage contraction
> --
>
> Key: IGNITE-12096
> URL: https://issues.apache.org/jira/browse/IGNITE-12096
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Colin Cassidy
>Priority: Critical
>
> When using the Ignite metrics API to measure available memory, the usage
> figures appear to be accurate while memory is being consumed - but when
> memory is freed the metrics do not drop. They appear to report that memory
> has not been freed up, even though it has.
> Reproducer below. This affects Ignite 2.7+.
> {{}}{{import org.apache.ignite.failure.NoOpFailureHandler; }}
> {{import org.junit.Test; }}
> {{public class MemoryTest2 { }}
> {{ private static final String CACHE_NAME = "cache"; }}
> {{ private static final String DEFAULT_MEMORY_REGION = "Default_Region"; }}
> {{ private static final long MEM_SIZE = 100L * 1024 * 1024; }}
> {{ @Test }}
> {{ public void testOOM() throws InterruptedException { }}
> {{ try (Ignite ignite = startIgnite("IgniteMemoryMonitorTest1")) { }}
> {{ fillDataRegion(ignite); }}
> {{ CacheConfiguration cfg = new }}
> {{CacheConfiguration<>(CACHE_NAME); }}
> {{ cfg.setStatisticsEnabled(true); }}
> {{ IgniteCache cache = }}
> {{ignite.getOrCreateCache(cfg); }}
> {{ // Clear all entries from the cache to free up memory }}
> {{ memUsed(ignite); }}
> {{ cache.clear(); }}
> {{ cache.removeAll(); }}
> {{ cache.put("Key", "Value"); }}
> {{ memUsed(ignite); }}
> {{ cache.destroy(); }}
> {{ Thread.sleep(5000); }}
> {{ // Should now report close to 0% but reports 59% still }}
> {{ memUsed(ignite); }}
> {{ } }}
> {{ } }}
> {{ }}
> {{ private Ignite startIgnite(String instanceName) { }}
> {{ IgniteConfiguration cfg = new IgniteConfiguration(); }}
> {{ cfg.setIgniteInstanceName(instanceName); }}
> {{ cfg.setDataStorageConfiguration(createDataStorageConfiguration());
> }}
> {{ cfg.setFailureHandler(new NoOpFailureHandler()); }}
> {{ return Ignition.start(cfg); }}
> {{ } }}
> {{ private DataStorageConfiguration createDataStorageConfiguration() { }}
> {{ return new DataStorageConfiguration() }}
> {{ .setDefaultDataRegionConfiguration( }}
> {{ new DataRegionConfiguration() }}
> {{ .setName(DEFAULT_MEMORY_REGION) }}
> {{ .setInitialSize(MEM_SIZE) }}
> {{ .setMaxSize(MEM_SIZE) }}
> {{ .setMetricsEnabled(true)); }}
> {{ } }}
> {{ private void fillDataRegion(Ignite ignite) { }}
> {{ byte[] megabyte = new byte[1024 * 1024]; }}
> {{ IgniteCache cache = }}
> {{ ignite.getOrCreateCache(CACHE_NAME); }}
> {{ for (int i = 0; i < 50; i++) { }}
> {{ cache.put(i, megabyte); }}
> {{ memUsed(ignite); }}
> {{ } }}
> {{ } }}
> {{ private void memUsed(Ignite ignite) { }}
> {{ DataRegionConfiguration defaultDataRegionCfg = }}
> {{ignite.configuration() }}
> {{ .getDataStorageConfiguration() }}
> {{ .getDefaultDataRegionConfiguration(); }}
> {{ String regionName = defaultDataRegionCfg.getName(); }}
> {{ DataRegionMetrics metrics = ignite.dataRegionMetrics(regionName); }}
> {{ float usedMem = metrics.getPagesFillFactor() * }}
> {{metrics.getTotalAllocatedPages() * metrics.getPageSize(); }}
> {{ float pctUsed = 100 * usedMem / defaultDataRegionCfg.getMaxSize();
> }}
> {{ System.out.println("Memory used: " + pctUsed + "%"); }}
> {{ } }}
> {{} }}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12096) Ignite memory metrics incorrect on cache usage contraction
[
https://issues.apache.org/jira/browse/IGNITE-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914311#comment-16914311
]
Denis Magda commented on IGNITE-12096:
--
I'm not sure that the recommended way for the used space calculation. Memory
cleaning can be deferred until the compaction process kicks off:
https://apacheignite.readme.io/docs/memory-defragmentation
Try to adjust the way you do the calculation and see if there is any change:
https://apacheignite.readme.io/docs/memory-metrics#section-memory-usage-calculation
But I still believe that we need to way for next compaction round to purge
deleted entries from memory. [~DmitriyGovorukhin] does it sound correct?
> Ignite memory metrics incorrect on cache usage contraction
> --
>
> Key: IGNITE-12096
> URL: https://issues.apache.org/jira/browse/IGNITE-12096
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Colin Cassidy
>Priority: Critical
>
> When using the Ignite metrics API to measure available memory, the usage
> figures appear to be accurate while memory is being consumed - but when
> memory is freed the metrics do not drop. They appear to report that memory
> has not been freed up, even though it has.
> Reproducer below. This affects Ignite 2.7+.
> {{}}{{import org.apache.ignite.failure.NoOpFailureHandler; }}
> {{import org.junit.Test; }}
> {{public class MemoryTest2 { }}
> {{ private static final String CACHE_NAME = "cache"; }}
> {{ private static final String DEFAULT_MEMORY_REGION = "Default_Region"; }}
> {{ private static final long MEM_SIZE = 100L * 1024 * 1024; }}
> {{ @Test }}
> {{ public void testOOM() throws InterruptedException { }}
> {{ try (Ignite ignite = startIgnite("IgniteMemoryMonitorTest1")) { }}
> {{ fillDataRegion(ignite); }}
> {{ CacheConfiguration cfg = new }}
> {{CacheConfiguration<>(CACHE_NAME); }}
> {{ cfg.setStatisticsEnabled(true); }}
> {{ IgniteCache cache = }}
> {{ignite.getOrCreateCache(cfg); }}
> {{ // Clear all entries from the cache to free up memory }}
> {{ memUsed(ignite); }}
> {{ cache.clear(); }}
> {{ cache.removeAll(); }}
> {{ cache.put("Key", "Value"); }}
> {{ memUsed(ignite); }}
> {{ cache.destroy(); }}
> {{ Thread.sleep(5000); }}
> {{ // Should now report close to 0% but reports 59% still }}
> {{ memUsed(ignite); }}
> {{ } }}
> {{ } }}
> {{ }}
> {{ private Ignite startIgnite(String instanceName) { }}
> {{ IgniteConfiguration cfg = new IgniteConfiguration(); }}
> {{ cfg.setIgniteInstanceName(instanceName); }}
> {{ cfg.setDataStorageConfiguration(createDataStorageConfiguration());
> }}
> {{ cfg.setFailureHandler(new NoOpFailureHandler()); }}
> {{ return Ignition.start(cfg); }}
> {{ } }}
> {{ private DataStorageConfiguration createDataStorageConfiguration() { }}
> {{ return new DataStorageConfiguration() }}
> {{ .setDefaultDataRegionConfiguration( }}
> {{ new DataRegionConfiguration() }}
> {{ .setName(DEFAULT_MEMORY_REGION) }}
> {{ .setInitialSize(MEM_SIZE) }}
> {{ .setMaxSize(MEM_SIZE) }}
> {{ .setMetricsEnabled(true)); }}
> {{ } }}
> {{ private void fillDataRegion(Ignite ignite) { }}
> {{ byte[] megabyte = new byte[1024 * 1024]; }}
> {{ IgniteCache cache = }}
> {{ ignite.getOrCreateCache(CACHE_NAME); }}
> {{ for (int i = 0; i < 50; i++) { }}
> {{ cache.put(i, megabyte); }}
> {{ memUsed(ignite); }}
> {{ } }}
> {{ } }}
> {{ private void memUsed(Ignite ignite) { }}
> {{ DataRegionConfiguration defaultDataRegionCfg = }}
> {{ignite.configuration() }}
> {{ .getDataStorageConfiguration() }}
> {{ .getDefaultDataRegionConfiguration(); }}
> {{ String regionName = defaultDataRegionCfg.getName(); }}
> {{ DataRegionMetrics metrics = ignite.dataRegionMetrics(regionName); }}
> {{ float usedMem = metrics.getPagesFillFactor() * }}
> {{metrics.getTotalAllocatedPages() * metrics.getPageSize(); }}
> {{ float pctUsed = 100 * usedMem / defaultDataRegionCfg.getMaxSize();
> }}
> {{ System.out.println("Memory used: " + pctUsed + "%"); }}
> {{ } }}
> {{} }}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12068) puzzling select result
[ https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909423#comment-16909423 ] Denis Magda commented on IGNITE-12068: -- [~JerryKwan] should be available in the first weeks of September. See this thread for more details: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-6-Time-Scope-and-Release-manager-td42944.html > puzzling select result > -- > > Key: IGNITE-12068 > URL: https://issues.apache.org/jira/browse/IGNITE-12068 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7.5 > Environment: System version: CentOS Linux release 7.6.1810 (Core) > Apache Ignite version: apache-ignite-2.7.5-1.noarch >Reporter: JerryKwan >Assignee: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > select using the first primary key only returns one record, but it should > return more records. > The following is how to reproduce this problem > 1, create a table using > CREATE TABLE IF NOT EXISTS Person( > id int, > city_id int, > name varchar, > age int, > company varchar, > PRIMARY KEY (id, city_id) > ); > 2, insert some records > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3); > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4); > INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4); > 3, query using 'select * from Person' show all of the records, expected > [http://www.passimage.in/i/03da31c8f23cf64580d5.png] > 4, query using 'select * from Person where id=1', only get one record, NOT > expected > [http://www.passimage.in/i/f5491491a70c5d796823.png] > 5, query using 'select * from Person where city_id=4' get two records, > expected > [http://www.passimage.in/i/ff0ee4f5e882983d779d.png] > Why 'select * from Person where id=1', only get one record? and how to fix > this? Is there any special operations/configurations to do? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12068) puzzling select result
[ https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-12068: - Fix Version/s: 2.7.6 > puzzling select result > -- > > Key: IGNITE-12068 > URL: https://issues.apache.org/jira/browse/IGNITE-12068 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7.5 > Environment: System version: CentOS Linux release 7.6.1810 (Core) > Apache Ignite version: apache-ignite-2.7.5-1.noarch >Reporter: JerryKwan >Priority: Blocker > Fix For: 2.7.6 > > > select using the first primary key only returns one record, but it should > return more records. > The following is how to reproduce this problem > 1, create a table using > CREATE TABLE IF NOT EXISTS Person( > id int, > city_id int, > name varchar, > age int, > company varchar, > PRIMARY KEY (id, city_id) > ); > 2, insert some records > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3); > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4); > INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4); > 3, query using 'select * from Person' show all of the records, expected > [http://www.passimage.in/i/03da31c8f23cf64580d5.png] > 4, query using 'select * from Person where id=1', only get one record, NOT > expected > [http://www.passimage.in/i/f5491491a70c5d796823.png] > 5, query using 'select * from Person where city_id=4' get two records, > expected > [http://www.passimage.in/i/ff0ee4f5e882983d779d.png] > Why 'select * from Person where id=1', only get one record? and how to fix > this? Is there any special operations/configurations to do? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12068) puzzling select result
[ https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907991#comment-16907991 ] Denis Magda commented on IGNITE-12068: -- Raising to a blocker. Let's make it to 2.7.6. > puzzling select result > -- > > Key: IGNITE-12068 > URL: https://issues.apache.org/jira/browse/IGNITE-12068 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7.5 > Environment: System version: CentOS Linux release 7.6.1810 (Core) > Apache Ignite version: apache-ignite-2.7.5-1.noarch >Reporter: JerryKwan >Priority: Blocker > > select using the first primary key only returns one record, but it should > return more records. > The following is how to reproduce this problem > 1, create a table using > CREATE TABLE IF NOT EXISTS Person( > id int, > city_id int, > name varchar, > age int, > company varchar, > PRIMARY KEY (id, city_id) > ); > 2, insert some records > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3); > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4); > INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4); > 3, query using 'select * from Person' show all of the records, expected > [http://www.passimage.in/i/03da31c8f23cf64580d5.png] > 4, query using 'select * from Person where id=1', only get one record, NOT > expected > [http://www.passimage.in/i/f5491491a70c5d796823.png] > 5, query using 'select * from Person where city_id=4' get two records, > expected > [http://www.passimage.in/i/ff0ee4f5e882983d779d.png] > Why 'select * from Person where id=1', only get one record? and how to fix > this? Is there any special operations/configurations to do? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12068) puzzling select result
[ https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-12068: - Priority: Blocker (was: Critical) > puzzling select result > -- > > Key: IGNITE-12068 > URL: https://issues.apache.org/jira/browse/IGNITE-12068 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7.5 > Environment: System version: CentOS Linux release 7.6.1810 (Core) > Apache Ignite version: apache-ignite-2.7.5-1.noarch >Reporter: JerryKwan >Priority: Blocker > > select using the first primary key only returns one record, but it should > return more records. > The following is how to reproduce this problem > 1, create a table using > CREATE TABLE IF NOT EXISTS Person( > id int, > city_id int, > name varchar, > age int, > company varchar, > PRIMARY KEY (id, city_id) > ); > 2, insert some records > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3); > INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4); > INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4); > 3, query using 'select * from Person' show all of the records, expected > [http://www.passimage.in/i/03da31c8f23cf64580d5.png] > 4, query using 'select * from Person where id=1', only get one record, NOT > expected > [http://www.passimage.in/i/f5491491a70c5d796823.png] > 5, query using 'select * from Person where city_id=4' get two records, > expected > [http://www.passimage.in/i/ff0ee4f5e882983d779d.png] > Why 'select * from Person where id=1', only get one record? and how to fix > this? Is there any special operations/configurations to do? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12057) Persistence files are stored to temp dir
[ https://issues.apache.org/jira/browse/IGNITE-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-12057: - Fix Version/s: (was: 2.8) 2.7.6 > Persistence files are stored to temp dir > > > Key: IGNITE-12057 > URL: https://issues.apache.org/jira/browse/IGNITE-12057 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Anton Kalashnikov >Priority: Critical > Fix For: 2.7.6 > > > h2. Description > Check this thread: > [https://stackoverflow.com/questions/56951913/ignite-persistent-schema-tables-disappeared-sometimes/56977212#56977212] > This prospect almost dropped us because the company could figure out why > persistence files disappear upon restarts. They turned off WARN logging level > and could see our warning saying that the files are written to such a > directory. > I've updated Ignite docs: > [https://apacheignite.readme.io/docs/distributed-persistent-store#section-persistence-path-management] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-12032:
-
Fix Version/s: 2.7.6
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Priority: Major
> Labels: newbie, usability
> Fix For: 2.7.6
>
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (IGNITE-6611) Optionally disable binary metadata for type
[
https://issues.apache.org/jira/browse/IGNITE-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-6611:
Fix Version/s: 3.0
> Optionally disable binary metadata for type
> ---
>
> Key: IGNITE-6611
> URL: https://issues.apache.org/jira/browse/IGNITE-6611
> Project: Ignite
> Issue Type: Task
> Components: binary
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 3.0
>
>
> We need to introduce special metadata mode for type - without metadata. This
> way we will have a kind of "flexible" type with no restrictions. This will be
> especially useful for SQL-related types where schema changes are possible
> (e.g. ADD COLUMN -> DROP COLUMN).
> Public part should be exposed to:
> 1) {{BinaryTypeConfiguration}}
> 2) {{BinaryType}} - add a flag here.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-6611) Optionally disable binary metadata for type
[
https://issues.apache.org/jira/browse/IGNITE-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903383#comment-16903383
]
Denis Magda commented on IGNITE-6611:
-
This is to be addressed in Ignite 3.0 that will go with a new API and the
storage format separated from the serialization approach.
> Optionally disable binary metadata for type
> ---
>
> Key: IGNITE-6611
> URL: https://issues.apache.org/jira/browse/IGNITE-6611
> Project: Ignite
> Issue Type: Task
> Components: binary
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Priority: Major
>
> We need to introduce special metadata mode for type - without metadata. This
> way we will have a kind of "flexible" type with no restrictions. This will be
> especially useful for SQL-related types where schema changes are possible
> (e.g. ADD COLUMN -> DROP COLUMN).
> Public part should be exposed to:
> 1) {{BinaryTypeConfiguration}}
> 2) {{BinaryType}} - add a flag here.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903210#comment-16903210 ] Denis Magda commented on IGNITE-12054: -- Raised to the BLOCKER as long as our Data Frames integration doesn't work with the latest Spark version. > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Priority: Blocker > Fix For: 2.7.6 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-12054: - Priority: Blocker (was: Major) > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.7.5 >Reporter: Denis Magda >Priority: Blocker > Fix For: 2.7.6 > > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12054) Upgrade Spark module to 2.4
Denis Magda created IGNITE-12054: Summary: Upgrade Spark module to 2.4 Key: IGNITE-12054 URL: https://issues.apache.org/jira/browse/IGNITE-12054 Project: Ignite Issue Type: Task Components: spark Affects Versions: 2.7.5 Reporter: Denis Magda Fix For: 2.7.6 Users can't use APIs that are already available in Spark 2.4: https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as a separate module that can support multiple Spark versions. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-11953) BTree corruption caused by byte array values
[
https://issues.apache.org/jira/browse/IGNITE-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-11953:
-
Fix Version/s: (was: 2.8)
2.7.6
> BTree corruption caused by byte array values
>
>
> Key: IGNITE-11953
> URL: https://issues.apache.org/jira/browse/IGNITE-11953
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.7.6
>
>
> In some cases for caches with cache group, we can get BTree corruption
> exception.
> {code}
> 09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected.
> Will be handled accordingly to configured handler [hnd=CustomFailureHandler
> [ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR,
> err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing
> a transaction has produced runtime exception]]class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427,
> val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770,
> cacheId=-420893003]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1811)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1620)
> at
>
[jira] [Commented] (IGNITE-12033) .NET: Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903193#comment-16903193
]
Denis Magda commented on IGNITE-12033:
--
[~ptupitsyn], let's fix it in Java instead?
> .NET: Callbacks from striped pool due to async/await may hang cluster
> -
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .net
> Fix For: 2.7.6
>
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
> The code is very simple:
> {code}
> Console.WriteLine("PutAsync");
> await cache.PutAsync(1, "Test");
> Console.WriteLine("Replace");
> cache.Replace(1, "Testing"); // Hangs here
> Console.WriteLine("Wait");
> await Task.Delay(Timeout.Infinite);
> {code}
> async/await should absolutely not allow any client code to be run from
> stripes.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (IGNITE-12033) .Net callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-12033:
-
Fix Version/s: 2.7.6
> .Net callbacks from striped pool due to async/await may hang cluster
>
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .net
> Fix For: 2.7.6
>
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
> The code is very simple:
> {code}
> Console.WriteLine("PutAsync");
> await cache.PutAsync(1, "Test");
> Console.WriteLine("Replace");
> cache.Replace(1, "Testing"); // Hangs here
> Console.WriteLine("Wait");
> await Task.Delay(Timeout.Infinite);
> {code}
> async/await should absolutely not allow any client code to be run from
> stripes.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-8229) Warning: Ignoring query projection because it's executed over LOCAL cache
[
https://issues.apache.org/jira/browse/IGNITE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896538#comment-16896538
]
Denis Magda commented on IGNITE-8229:
-
Community is going to discontinue LOCAL caches with Ignite 3.0 release. Don't
see any reason to enhance this component in Ignite of version 2.x
> Warning: Ignoring query projection because it's executed over LOCAL cache
> --
>
> Key: IGNITE-8229
> URL: https://issues.apache.org/jira/browse/IGNITE-8229
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Aleksandr Tceluiko
>Priority: Major
>
> Every scan query get warning:
> [13:26:25 WRN] Ignoring query projection because it's
> executed over LOCAL cache (only local node will be queried):
> GridCacheQueryAdapter [type=SCAN, clsName=null, clause=null,
> filter=o.a.i.i.processors.platform.cache.PlatformCacheEntryF
> ilterImpl@7629939a, transform=null, part=null, incMeta=false,
> metrics=GridCacheQueryMetricsAdapter [minTime=9223372036854775807, maxTime=0,
> sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false,
> prj=o.a.i.i.cluster.ClusterGroupAdapter@708472f7, keepBinary=true,
> subjId=null, taskHash=0]
>
> Valentin Kulichenko wrote:
> {quote}This looks like a bug as there is no way to provide cluster group for
> a query in the latest versions.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (IGNITE-8229) Warning: Ignoring query projection because it's executed over LOCAL cache
[
https://issues.apache.org/jira/browse/IGNITE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda resolved IGNITE-8229.
-
Resolution: Won't Fix
> Warning: Ignoring query projection because it's executed over LOCAL cache
> --
>
> Key: IGNITE-8229
> URL: https://issues.apache.org/jira/browse/IGNITE-8229
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Aleksandr Tceluiko
>Priority: Major
>
> Every scan query get warning:
> [13:26:25 WRN] Ignoring query projection because it's
> executed over LOCAL cache (only local node will be queried):
> GridCacheQueryAdapter [type=SCAN, clsName=null, clause=null,
> filter=o.a.i.i.processors.platform.cache.PlatformCacheEntryF
> ilterImpl@7629939a, transform=null, part=null, incMeta=false,
> metrics=GridCacheQueryMetricsAdapter [minTime=9223372036854775807, maxTime=0,
> sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false,
> prj=o.a.i.i.cluster.ClusterGroupAdapter@708472f7, keepBinary=true,
> subjId=null, taskHash=0]
>
> Valentin Kulichenko wrote:
> {quote}This looks like a bug as there is no way to provide cluster group for
> a query in the latest versions.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Closed] (IGNITE-8229) Warning: Ignoring query projection because it's executed over LOCAL cache
[
https://issues.apache.org/jira/browse/IGNITE-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-8229.
---
> Warning: Ignoring query projection because it's executed over LOCAL cache
> --
>
> Key: IGNITE-8229
> URL: https://issues.apache.org/jira/browse/IGNITE-8229
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Aleksandr Tceluiko
>Priority: Major
>
> Every scan query get warning:
> [13:26:25 WRN] Ignoring query projection because it's
> executed over LOCAL cache (only local node will be queried):
> GridCacheQueryAdapter [type=SCAN, clsName=null, clause=null,
> filter=o.a.i.i.processors.platform.cache.PlatformCacheEntryF
> ilterImpl@7629939a, transform=null, part=null, incMeta=false,
> metrics=GridCacheQueryMetricsAdapter [minTime=9223372036854775807, maxTime=0,
> sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false,
> prj=o.a.i.i.cluster.ClusterGroupAdapter@708472f7, keepBinary=true,
> subjId=null, taskHash=0]
>
> Valentin Kulichenko wrote:
> {quote}This looks like a bug as there is no way to provide cluster group for
> a query in the latest versions.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-2176:
---
Assignee: Alexey Goncharuk (was: Yakov Zhdanov)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.8
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
>
[jira] [Updated] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2176:
Priority: Blocker (was: Critical)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Yakov Zhdanov
>Priority: Blocker
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
>
[jira] [Updated] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2176:
Fix Version/s: 2.8
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: 2.8
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
>
[jira] [Created] (IGNITE-11942) IGFS and Hadoop Accelerator Discontinuation
Denis Magda created IGNITE-11942: Summary: IGFS and Hadoop Accelerator Discontinuation Key: IGNITE-11942 URL: https://issues.apache.org/jira/browse/IGNITE-11942 Project: Ignite Issue Type: Task Reporter: Denis Magda Fix For: 2.8 The community has voted for the following decision: * IGFS and In-Memory Hadoop Accelerator components are to be discontinued and no longer supported by the community * The existing source code of IGFS and In-Memory Hadoop Accelerator is to be removed from Ignite master. Before that, a special branch like "ignite-igfs-and-hadoop-accelerator" to be forked off the master in order to preserve the sources in Git history for those who might need it. The voting thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42405.html Once the changes are made for Ignite 2.8, please contact Denis Magda to update a public documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-8873) Optimize cache scans with enabled persistence.
[
https://issues.apache.org/jira/browse/IGNITE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reopened IGNITE-8873:
-
[~ascherbakov], [~agoncharuk],
It's great to see that memory warmup is to be supported for the
persistence-based deployments. But I would encourage us to move forward and
reconsider the API from the usability standpoint.
As an end user, I don't understand how to use {code:java}loadPartition{code}
method:
* How do I know which partition to preload? Should that be partition 5, 27 or
876? Basically, how do I make a decision if a subset of the data has to be
brought to RAM?
* What if I want to reload the whole table which is the most common requirement
I've heard of? I'll be forced to have the calls like that:
{code:java}
foreach partition
loadPartition(partition)
{code}
Please let me know what you think about the following API that solves those
usability points:
* {code:java}IgniteCache.loadCache{code} -> loads the whole table. Disregard
the cases that it might not fit in RAM. Our users are smart. If there is not
enough RAM then they can get more RAM space.
* {code:java}IgniteCache.loadCache(predicate){code} -> for the scenarios when
the system is designed in a way that RAM keeps a subset of data. For instance,
users can load records for the last 5 days or for specific bank accounts.
As for the {code:java}loadPartition{code} it doesn't look like a method that
has to be at the public API level.
> Optimize cache scans with enabled persistence.
> --
>
> Key: IGNITE-8873
> URL: https://issues.apache.org/jira/browse/IGNITE-8873
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> Currently cache scans with enabled persistence involve link resolution, which
> can lead to radom disk access resulting in bad performace on SAS disks.
> One possibility is to preload cache data pages to remove slow random disk
> access.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11919) Change message format for incompatible fields' types changes
[
https://issues.apache.org/jira/browse/IGNITE-11919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-11919:
-
Description:
Follow this discussion thread to find out the reason for the change:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-stops-working-suddenly-during-dev-td42207.html
It's suggested to apply the following format:
{code}
ERROR: Type 'ClassName/TypeName' has a different/incorrect type
for field 'FieldName'. Expected 'type1' but 'type2' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required.
{code}
That's an example of how it will look like:
{code}
ERROR: Type 'Person' has a different/incorrect type
for field 'salary'. Expected 'double' but 'string' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required.
{code}
was:
Follow this discussion thread to find out the reason for the change:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-stops-working-suddenly-during-dev-td42207.html
It's suggested to apply the following format:
_ERROR: Type 'ClassName/TypeName' has a different/incorrect type
for field 'FieldName'. Expected 'type1' but 'type2' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required._
That's an example of how it will look like:
_ERROR: Type 'Person' has a different/incorrect type
for field 'salary'. Expected 'double' but 'string' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required._
> Change message format for incompatible fields' types changes
>
>
> Key: IGNITE-11919
> URL: https://issues.apache.org/jira/browse/IGNITE-11919
> Project: Ignite
> Issue Type: Task
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 2.8
>
>
> Follow this discussion thread to find out the reason for the change:
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-stops-working-suddenly-during-dev-td42207.html
> It's suggested to apply the following format:
> {code}
> ERROR: Type 'ClassName/TypeName' has a different/incorrect type
> for field 'FieldName'. Expected 'type1' but 'type2' was provided. Field
> type's modification is unsupported, clean {root_path}/marshaller directory
> if the type change is required.
> {code}
> That's an example of how it will look like:
> {code}
> ERROR: Type 'Person' has a different/incorrect type
> for field 'salary'. Expected 'double' but 'string' was provided. Field
> type's modification is unsupported, clean {root_path}/marshaller directory
> if the type change is required.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11919) Change message format for incompatible fields' types changes
Denis Magda created IGNITE-11919:
Summary: Change message format for incompatible fields' types
changes
Key: IGNITE-11919
URL: https://issues.apache.org/jira/browse/IGNITE-11919
Project: Ignite
Issue Type: Task
Reporter: Denis Magda
Fix For: 2.8
Follow this discussion thread to find out the reason for the change:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-stops-working-suddenly-during-dev-td42207.html
It's suggested to apply the following format:
_ERROR: Type 'ClassName/TypeName' has a different/incorrect type
for field 'FieldName'. Expected 'type1' but 'type2' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required._
That's an example of how it will look like:
_ERROR: Type 'Person' has a different/incorrect type
for field 'salary'. Expected 'double' but 'string' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11771) Kubernetes discovery support for non-ready pods
[ https://issues.apache.org/jira/browse/IGNITE-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863308#comment-16863308 ] Denis Magda commented on IGNITE-11771: -- [~shroman], sorry my bad. Sure, please disregard that suggestion. > Kubernetes discovery support for non-ready pods > --- > > Key: IGNITE-11771 > URL: https://issues.apache.org/jira/browse/IGNITE-11771 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Balazs Peterfi >Assignee: Denis Magda >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > I have a use case where Ignite is running in embedded mode and on start-up > there is a time consuming task to warm-up the cache. During that time > Kubernetes sees the pods as not ready due to the loading, thus the current > implementation doesn't return them as potential members. Eventually they > would become ready and see each-other but by then it would be a split-brain > situation. > The idea is to return IPs not only for "ready" pods but for "not ready" ones > as well in case the discovery client is configured that way. See more details > here: > [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#endpointsubset-v1-core] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11771) Kubernetes discovery support for non-ready pods
[ https://issues.apache.org/jira/browse/IGNITE-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862464#comment-16862464 ] Denis Magda commented on IGNITE-11771: -- [~shroman], could you please incorporate a minor change? I left a note in Github. Please feel free to merge after that. > Kubernetes discovery support for non-ready pods > --- > > Key: IGNITE-11771 > URL: https://issues.apache.org/jira/browse/IGNITE-11771 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Balazs Peterfi >Assignee: Denis Magda >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > I have a use case where Ignite is running in embedded mode and on start-up > there is a time consuming task to warm-up the cache. During that time > Kubernetes sees the pods as not ready due to the loading, thus the current > implementation doesn't return them as potential members. Eventually they > would become ready and see each-other but by then it would be a split-brain > situation. > The idea is to return IPs not only for "ready" pods but for "not ready" ones > as well in case the discovery client is configured that way. See more details > here: > [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#endpointsubset-v1-core] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11758) Python thin: a lot of documentation files without license header
[ https://issues.apache.org/jira/browse/IGNITE-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821328#comment-16821328 ] Denis Magda commented on IGNITE-11758: -- [~isapego], if these docs are similar to javadoc then should we care about the license? I've checked our binaries distributions and generated javadocs don't have the license header. Sorry if I'm missing anything. > Python thin: a lot of documentation files without license header > > > Key: IGNITE-11758 > URL: https://issues.apache.org/jira/browse/IGNITE-11758 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Major > Fix For: 2.8 > > > There are a lot of .rst documentation files in modules/platforms/python/docs/ > that does not contain license header. We need either delete them if they are > auto generated or add headers to them if they are not. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11758) Python thin: a lot of documentation files without license header
[ https://issues.apache.org/jira/browse/IGNITE-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820293#comment-16820293 ] Denis Magda commented on IGNITE-11758: -- 1. [~Melnichuk], we don't need to keep a copy of the docs in `modules/platforms/python/docs/source` as long as the readme hosts them. All of the documentation changes have to take place on readme. In GitHub repo is more than enough to have README.md which is already there. 2. As far as I understand, if we remove `docs` from the repo then this won't be an issue anymore. > Python thin: a lot of documentation files without license header > > > Key: IGNITE-11758 > URL: https://issues.apache.org/jira/browse/IGNITE-11758 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Major > Fix For: 2.8 > > > There are a lot of .rst documentation files in modules/platforms/python/docs/ > that does not contain license header. We need either delete them if they are > auto generated or add headers to them if they are not. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11487) Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
[ https://issues.apache.org/jira/browse/IGNITE-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786150#comment-16786150 ] Denis Magda commented on IGNITE-11487: -- [~ezhuravl], [~vozerov], please share more details explaining how to document this parameter the best way. [~Artem Budnikov], could you please take over? This should be a short paragraph here: https://apacheignite-sql.readme.io/docs/performance-and-debugging > Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property > - > > Key: IGNITE-11487 > URL: https://issues.apache.org/jira/browse/IGNITE-11487 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11487) Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
[ https://issues.apache.org/jira/browse/IGNITE-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-11487: - Priority: Critical (was: Major) > Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property > - > > Key: IGNITE-11487 > URL: https://issues.apache.org/jira/browse/IGNITE-11487 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11487) Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
[ https://issues.apache.org/jira/browse/IGNITE-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-11487: Assignee: Artem Budnikov (was: Prachi Garg) > Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property > - > > Key: IGNITE-11487 > URL: https://issues.apache.org/jira/browse/IGNITE-11487 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-11155.
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768631#comment-16768631
]
Denis Magda commented on IGNITE-11155:
--
Ah, I see, you mean that the exception will be thrown as soon as the JVM
process gets started. Understood, closing the ticket.
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda resolved IGNITE-11155.
--
Resolution: Fixed
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-11155:
-
Attachment: image.png
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767608#comment-16767608
]
Denis Magda commented on IGNITE-11155:
--
How about RuntimeMXBean solution? Check this thread:
https://stackoverflow.com/questions/1490869/how-to-get-vm-arguments-from-inside-of-java-application
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767594#comment-16767594
]
Denis Magda commented on IGNITE-11155:
--
[~dpavlov], let's do one step and make an even better improvement. I was asking
the following question myself - look, why do we let a node to start and then
fail if the parameters are missing? Why don't we check the JDK version and
parameters as soon as Ignition.start is called. If the parameters are missed
then we will through an exception right away.
Could you please do that? It's much more user-friendly.
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reopened IGNITE-11155:
--
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763917#comment-16763917
]
Denis Magda commented on IGNITE-11155:
--
[~dpavlov], please change the text to the following:
"Please add the following parameters to JVM startup settings and restart the
application:
{parameters"
Plus, I think the reference to the docs is redundant, let's exclude it from the
source code. The docs and sections can be changed.
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Attachments: start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11252) Docs: Index corruption recovery procedure
Denis Magda created IGNITE-11252: Summary: Docs: Index corruption recovery procedure Key: IGNITE-11252 URL: https://issues.apache.org/jira/browse/IGNITE-11252 Project: Ignite Issue Type: Task Components: documentation Affects Versions: 2.7 Reporter: Denis Magda Assignee: Prachi Garg Fix For: 2.8 We need to document a recovery procedure if an index corruption happens. Refer to this thread for details and examples of the exception dumped to the logs if the issue occurs: http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-index-corruption-issue-gt-unrecoverable-cluster-td39869.html # Recovering from an index corruption ## Applicable if It is known that an index of a cache is corrupted, but the main data (partition files and WAL) is fine. Show code snippets of possible examples. Find via the references shared in the dev list discussion. ## Steps to recover 1. Stop the node 2. Delete index.bin of the affected caches (path is db//cache-/index.bin) 3. Start the node - Note: At this point the node is active in the cluster but don’t have indexes. It means that it serves SQL queries but their performance can be low. Avoid running SQL queries on large tables at this point 4. Wait for message “Finished indexes rebuilding for cache ” in the Ignite log # Recovering from a persistent storage corruption ## Applicable if A part of the persistent storage (partition files, checkpoint markers or WAL) was corrupted and there is no other way to recover it, but there are healthy copies of all data on other nodes. ## Steps to recover 1. Stop the node 2. Delete all persistence files of the node (best to clear Ignite working directory, storage directory, WAL and WAL archive directories) 3. Make sure consistentId is explicitly set in the configuration of the node - If it isn’t, lookup the generated consistentId using control.sh and set it explicitly in the config or via IGNITE_CONSISTENT_ID (2.8+ only) 4. Start the node 5. Wait for messages for all caches -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
Denis Magda created IGNITE-11216:
Summary: Ignite.sh fails on Mac OS and Linux - Java 11
Key: IGNITE-11216
URL: https://issues.apache.org/jira/browse/IGNITE-11216
Project: Ignite
Issue Type: Task
Affects Versions: 2.7
Reporter: Denis Magda
Ignite.sh fails on Mac OS Mojave with the following JDK version:
java version "11.0.2" 2019-01-15 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
The same issue is reproduced on Linux and the workaround is discussed here:
https://issues.apache.org/jira/browse/IGNITE-3
The exception is as follows:
{noformat}
/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh: line
40: [: -eq: unary operator expected
./ignite.sh: line 152: [: -eq: unary operator expected
./ignite.sh: line 157: [: -gt: unary operator expected
./ignite.sh: line 170: [: -eq: unary operator expected
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Exception in thread "main" java.lang.ExceptionInInitializerError
at
org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
at
org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
at
org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class is
unavailable.
at
org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
at
org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
... 4 more
Caused by: java.lang.IllegalAccessException: class
org.apache.ignite.internal.util.GridUnsafe cannot access class
jdk.internal.misc.SharedSecrets (in module java.base) because module java.base
does not export jdk.internal.misc to unnamed module @4f83df68
at
java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
at
java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
at java.base/java.lang.reflect.Method.invoke(Method.java:558)
at
org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
... 5 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-11113) JVM 9-11 startup parameters have to be mentioned in every section of getting started
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-3. > JVM 9-11 startup parameters have to be mentioned in every section of getting > started > > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > > Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] > have to be mentioned in callout blocks of every section in the getting > started guide [2] where it's explained how to start a node with ignite.sh or > launch an application. > The user has to know how to: > * Fix ignite.sh/ignite.bat to make them workable > * What to do in an IDEA like IntellijIdean and Eclipse to make examples and > apps workable > [1] > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11113) JVM 9-11 startup parameters have to be mentioned in every section of getting started
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758696#comment-16758696 ] Denis Magda commented on IGNITE-3: -- [~Artem Budnikov], the JAVA_HOME workaround worked for me. Thanks! > JVM 9-11 startup parameters have to be mentioned in every section of getting > started > > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > > Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] > have to be mentioned in callout blocks of every section in the getting > started guide [2] where it's explained how to start a node with ignite.sh or > launch an application. > The user has to know how to: > * Fix ignite.sh/ignite.bat to make them workable > * What to do in an IDEA like IntellijIdean and Eclipse to make examples and > apps workable > [1] > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10887) .NET: Align .Net docs with Java
[ https://issues.apache.org/jira/browse/IGNITE-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756881#comment-16756881 ] Denis Magda commented on IGNITE-10887: -- Expiration and eviction policies are not aligned with Java counterparts as well: https://apacheignite-net.readme.io/docs/eviction-policies https://apacheignite-net.readme.io/docs/expiry-policies In Java we explain how it works for the new off-heap memory and on-heap Java cache, while .Net docs are based on Ignite 1.x memory architecture. > .NET: Align .Net docs with Java > --- > > Key: IGNITE-10887 > URL: https://issues.apache.org/jira/browse/IGNITE-10887 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Priority: Critical > Fix For: 2.8 > > > It seems that the .Net docs are a bit outdated compared to Java ones. > Need to align .Net and Java docs. .Net pages which are not specific to the > platform should be replaced with a simple link to the Java docs. The docs > that have .Net-specific things (e.g. code examples) should be reworked. > The pages with issues > - Performnace Tips page > (https://apacheignite-net.readme.io/docs/performance-tips) > - Off-heap memory (https://apacheignite-net.readme.io/docs/off-heap-memory) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10887) .NET: Align .Net docs with Java
[ https://issues.apache.org/jira/browse/IGNITE-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-10887: - Priority: Critical (was: Major) > .NET: Align .Net docs with Java > --- > > Key: IGNITE-10887 > URL: https://issues.apache.org/jira/browse/IGNITE-10887 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Priority: Critical > Fix For: 2.8 > > > It seems that the .Net docs are a bit outdated compared to Java ones. > Need to align .Net and Java docs. .Net pages which are not specific to the > platform should be replaced with a simple link to the Java docs. The docs > that have .Net-specific things (e.g. code examples) should be reworked. > The pages with issues > - Performnace Tips page > (https://apacheignite-net.readme.io/docs/performance-tips) > - Off-heap memory (https://apacheignite-net.readme.io/docs/off-heap-memory) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10887) .NET: Align .Net docs with Java
[ https://issues.apache.org/jira/browse/IGNITE-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-10887: - Fix Version/s: 2.8 > .NET: Align .Net docs with Java > --- > > Key: IGNITE-10887 > URL: https://issues.apache.org/jira/browse/IGNITE-10887 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Priority: Major > Fix For: 2.8 > > > It seems that the .Net docs are a bit outdated compared to Java ones. > Need to align .Net and Java docs. .Net pages which are not specific to the > platform should be replaced with a simple link to the Java docs. The docs > that have .Net-specific things (e.g. code examples) should be reworked. > The pages with issues > - Performnace Tips page > (https://apacheignite-net.readme.io/docs/performance-tips) > - Off-heap memory (https://apacheignite-net.readme.io/docs/off-heap-memory) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11113) JVM 9-11 startup parameters have to be mentioned in every section of getting started
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3: - Reporter: Denis Magda (was: Artem Budnikov) > JVM 9-11 startup parameters have to be mentioned in every section of getting > started > > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Priority: Blocker > > Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] > have to be mentioned in callout blocks of every section in the getting > started guide [2] where it's explained how to start a node with ignite.sh or > launch an application. > The user has to know how to: > * Fix ignite.sh/ignite.bat to make them workable > * What to do in an IDEA like IntellijIdean and Eclipse to make examples and > apps workable > [1] > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11113) JVM 9-11 startup parameters have to be mentioned in every section of getting started
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-3: Assignee: Artem Budnikov > JVM 9-11 startup parameters have to be mentioned in every section of getting > started > > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Blocker > > Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] > have to be mentioned in callout blocks of every section in the getting > started guide [2] where it's explained how to start a node with ignite.sh or > launch an application. > The user has to know how to: > * Fix ignite.sh/ignite.bat to make them workable > * What to do in an IDEA like IntellijIdean and Eclipse to make examples and > apps workable > [1] > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11113) JVM 9-11 startup parameters have to be mentioned in every section of getting started
Denis Magda created IGNITE-3: Summary: JVM 9-11 startup parameters have to be mentioned in every section of getting started Key: IGNITE-3 URL: https://issues.apache.org/jira/browse/IGNITE-3 Project: Ignite Issue Type: Task Components: documentation Reporter: Artem Budnikov Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] have to be mentioned in callout blocks of every section in the getting started guide [2] where it's explained how to start a node with ignite.sh or launch an application. The user has to know how to: * Fix ignite.sh/ignite.bat to make them workable * What to do in an IDEA like IntellijIdean and Eclipse to make examples and apps workable [1] https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10991) SET STREAMING ALLOW_OVERWRITE DataStreamer fails to finish
[
https://issues.apache.org/jira/browse/IGNITE-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-10991:
Assignee: Vladimir Ozerov
> SET STREAMING ALLOW_OVERWRITE DataStreamer fails to finish
> --
>
> Key: IGNITE-10991
> URL: https://issues.apache.org/jira/browse/IGNITE-10991
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Vladimir Ozerov
>Priority: Major
> Attachments: CacheSqlStreamingAllowOverwriteTest.java
>
>
> Please see attached test. Repeatedly overwriting same cache entries over and
> over in streaming mode with ALLOW_OVERWRITE ON will cause either:
> {code}
> java.sql.BatchUpdateException: Failed to INSERT some keys because they are
> already in cache [keys=[2054...]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1052)
> ... 1 more
> {code}
> or
> {code}
> WARNING: Exception during batch send on streamed connection close
> java.sql.BatchUpdateException: class
> org.apache.ignite.IgniteCheckedException: Data streamer has been closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1016)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Expecter behavior - no failures, all records overwritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10991) SET STREAMING ALLOW_OVERWRITE DataStreamer fails to finish
[
https://issues.apache.org/jira/browse/IGNITE-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-10991:
-
Fix Version/s: 2.8
> SET STREAMING ALLOW_OVERWRITE DataStreamer fails to finish
> --
>
> Key: IGNITE-10991
> URL: https://issues.apache.org/jira/browse/IGNITE-10991
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Attachments: CacheSqlStreamingAllowOverwriteTest.java
>
>
> Please see attached test. Repeatedly overwriting same cache entries over and
> over in streaming mode with ALLOW_OVERWRITE ON will cause either:
> {code}
> java.sql.BatchUpdateException: Failed to INSERT some keys because they are
> already in cache [keys=[2054...]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1052)
> ... 1 more
> {code}
> or
> {code}
> WARNING: Exception during batch send on streamed connection close
> java.sql.BatchUpdateException: class
> org.apache.ignite.IgniteCheckedException: Data streamer has been closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1016)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Expecter behavior - no failures, all records overwritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-10533) Web Console: Images outdated on web site.
[ https://issues.apache.org/jira/browse/IGNITE-10533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-10533. > Web Console: Images outdated on web site. > - > > Key: IGNITE-10533 > URL: https://issues.apache.org/jira/browse/IGNITE-10533 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Kuznetsov >Assignee: Denis Magda >Priority: Major > > For example see: https://apacheignite-tools.readme.io/docs/ignite-web-console -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10533) Web Console: Images outdated on web site.
[ https://issues.apache.org/jira/browse/IGNITE-10533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740858#comment-16740858 ] Denis Magda commented on IGNITE-10533: -- Looks good thanks! > Web Console: Images outdated on web site. > - > > Key: IGNITE-10533 > URL: https://issues.apache.org/jira/browse/IGNITE-10533 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Kuznetsov >Assignee: Denis Magda >Priority: Major > > For example see: https://apacheignite-tools.readme.io/docs/ignite-web-console -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10867) Document work-around JDK upgrade against command-line parsing bug on Windows
[ https://issues.apache.org/jira/browse/IGNITE-10867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-10867: - Priority: Critical (was: Major) > Document work-around JDK upgrade against command-line parsing bug on Windows > > > Key: IGNITE-10867 > URL: https://issues.apache.org/jira/browse/IGNITE-10867 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 >Reporter: Ilya Kasnacheev >Assignee: Prachi Garg >Priority: Critical > Labels: windows > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10867) Document work-around JDK upgrade against command-line parsing bug on Windows
[ https://issues.apache.org/jira/browse/IGNITE-10867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-10867: Assignee: Prachi Garg (was: Denis Magda) > Document work-around JDK upgrade against command-line parsing bug on Windows > > > Key: IGNITE-10867 > URL: https://issues.apache.org/jira/browse/IGNITE-10867 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 >Reporter: Ilya Kasnacheev >Assignee: Prachi Garg >Priority: Major > Labels: windows > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
[ https://issues.apache.org/jira/browse/IGNITE-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734725#comment-16734725 ] Denis Magda commented on IGNITE-10846: -- Please update the following sentence. _Pros: WAL archiving helps in data rebalancing when a node goes offline for a short period of time._ -> WAL archiving helps to speed up data rebalancing in cases when a new node joins the cluster or an old one reconnects after a short downtime" [~Artem Budnikov], please do a final review. > Improve docs for "Disabling WAL Archiving" > -- > > Key: IGNITE-10846 > URL: https://issues.apache.org/jira/browse/IGNITE-10846 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Prachi Garg >Priority: Critical > Fix For: 2.8 > > > Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10853) Docker Hub repository doesn't point to official GitHub repository
[ https://issues.apache.org/jira/browse/IGNITE-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731407#comment-16731407 ] Denis Magda commented on IGNITE-10853: -- [~vveider], could you please help with the following issue on the Docker side? [~Artem Budnikov], please help to correct the docs whenever is required. > Docker Hub repository doesn't point to official GitHub repository > - > > Key: IGNITE-10853 > URL: https://issues.apache.org/jira/browse/IGNITE-10853 > Project: Ignite > Issue Type: Bug > Components: build, documentation, platforms >Reporter: Philipp Gillé >Priority: Major > Attachments: 2018-12-30 apache ignite docker hub 2.PNG, 2018-12-30 > apache ignite docker hub.PNG > > > According to the documentation > (https://apacheignite.readme.io/docs/docker-deployment) the official Docker > Hub repository is https://hub.docker.com/r/apacheignite/ignite. But the > source repository (the GitHub repository where the Dockerfile is) points to > https://github.com/ntikhonov/ignite, which is not the official Apache Ignite > GitHub repository. See the attached image for this. > You do have a Dockerfile in your official repository, see > https://github.com/apache/ignite/tree/7989173b4d64a681fd08b7d7bcda2d26559941ae/docker/apache-ignite. > And apparently your build process pushes the Docker image to the Docker Hub, > so the image on the Docker Hub is actually *correct*. > *But* there are multiple problems with this: > 1. When looking at the Dockerfile via the Docker Hub web interface > (https://hub.docker.com/r/apacheignite/ignite/dockerfile), it's the wrong > Dockerfile! See the attached image for this > 2. People might be mislead into thinking that > https://github.com/ntikhonov/ignite is the official Ignite GitHub repository > if they overlook that it's a fork > 3. https://github.com/ntikhonov/ignite master branch is 2445 commits behind > the official master. Currently it seems that the Docker Hub automatic > building is deactivated, but if it gets activated (for building Docker > images on each GitHub repo push) an old / wrong Docker image will be created > on Docker Hub and it will stay wrong until your CI service pushes the correct > one > Related: > - The Docker image was created in IGNITE-1046 > - The Docker image is supposed to be turned into an official Docker image in > IGNITE-7190, but the PR has been open for one year already and seems to be > abandoned -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10853) Docker Hub repository doesn't point to official GitHub repository
[ https://issues.apache.org/jira/browse/IGNITE-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-10853: Assignee: Peter Ivanov > Docker Hub repository doesn't point to official GitHub repository > - > > Key: IGNITE-10853 > URL: https://issues.apache.org/jira/browse/IGNITE-10853 > Project: Ignite > Issue Type: Bug > Components: build, documentation, platforms >Reporter: Philipp Gillé >Assignee: Peter Ivanov >Priority: Major > Attachments: 2018-12-30 apache ignite docker hub 2.PNG, 2018-12-30 > apache ignite docker hub.PNG > > > According to the documentation > (https://apacheignite.readme.io/docs/docker-deployment) the official Docker > Hub repository is https://hub.docker.com/r/apacheignite/ignite. But the > source repository (the GitHub repository where the Dockerfile is) points to > https://github.com/ntikhonov/ignite, which is not the official Apache Ignite > GitHub repository. See the attached image for this. > You do have a Dockerfile in your official repository, see > https://github.com/apache/ignite/tree/7989173b4d64a681fd08b7d7bcda2d26559941ae/docker/apache-ignite. > And apparently your build process pushes the Docker image to the Docker Hub, > so the image on the Docker Hub is actually *correct*. > *But* there are multiple problems with this: > 1. When looking at the Dockerfile via the Docker Hub web interface > (https://hub.docker.com/r/apacheignite/ignite/dockerfile), it's the wrong > Dockerfile! See the attached image for this > 2. People might be mislead into thinking that > https://github.com/ntikhonov/ignite is the official Ignite GitHub repository > if they overlook that it's a fork > 3. https://github.com/ntikhonov/ignite master branch is 2445 commits behind > the official master. Currently it seems that the Docker Hub automatic > building is deactivated, but if it gets activated (for building Docker > images on each GitHub repo push) an old / wrong Docker image will be created > on Docker Hub and it will stay wrong until your CI service pushes the correct > one > Related: > - The Docker image was created in IGNITE-1046 > - The Docker image is supposed to be turned into an official Docker image in > IGNITE-7190, but the PR has been open for one year already and seems to be > abandoned -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10845) Ignite Production Readiness Section Enhancement
Denis Magda created IGNITE-10845: Summary: Ignite Production Readiness Section Enhancement Key: IGNITE-10845 URL: https://issues.apache.org/jira/browse/IGNITE-10845 Project: Ignite Issue Type: Task Components: documentation Reporter: Denis Magda Assignee: Prachi Garg Fix For: 2.8 Enhance Ignite production readiness section with points from here: https://www.gridgain.com/resources/blog/checklist-assembling-your-first-apacher-ignitetm-cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7132) Investigate and document Ignite Persistence usage in Docker
[ https://issues.apache.org/jira/browse/IGNITE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7132: Priority: Minor (was: Major) > Investigate and document Ignite Persistence usage in Docker > --- > > Key: IGNITE-7132 > URL: https://issues.apache.org/jira/browse/IGNITE-7132 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Minor > Fix For: 2.8 > > > Inspired by the following talk: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-in-docker-Native-Persistence-td18426.html > The aim is to investigate how is better to deploy Ignite persistence in > Docker. Probably with the usage of Docker volumes: > https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume > Once the configuration option is clear the following documentation needs to > be updated: > https://apacheignite.readme.io/docs/docker-deployment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-1188) We need to document Visor Cmd
[ https://issues.apache.org/jira/browse/IGNITE-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-1188. --- > We need to document Visor Cmd > - > > Key: IGNITE-1188 > URL: https://issues.apache.org/jira/browse/IGNITE-1188 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko >Priority: Major > > We need to give a list of Visor Commands. > Describe interactive and batch modes. > Give several examples of most useful commands. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7351) Create a page for continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7351: Fix Version/s: (was: 2.7) > Create a page for continuous queries > > > Key: IGNITE-7351 > URL: https://issues.apache.org/jira/browse/IGNITE-7351 > Project: Ignite > Issue Type: Task > Components: documentation, site >Reporter: Denis Magda >Priority: Major > > Create a page for continuous queries putting it under Features menu on the > site. This capability is a strong distinguisher from relational databases > that do not support continuous notifications and processing built around them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721768#comment-16721768 ] Denis Magda commented on IGNITE-6526: - Artem, I know you've been updating the capacity planning page. Is this a duplicate ticket? Please close if needed. > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-6526: --- Assignee: Artem Budnikov (was: Denis Magda) > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6526: Fix Version/s: (was: 2.7) 2.8 > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8137) Explain how to see SQL schema and table structure in Ignite
[
https://issues.apache.org/jira/browse/IGNITE-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-8137:
Fix Version/s: (was: 2.8)
> Explain how to see SQL schema and table structure in Ignite
> ---
>
> Key: IGNITE-8137
> URL: https://issues.apache.org/jira/browse/IGNITE-8137
> Project: Ignite
> Issue Type: New Feature
> Components: documentation
>Reporter: Denis Magda
>Priority: Major
>
> Presently, Ignite doesn't ship {{SHOW TABLE}} command. Thus, it's not clear
> how to get tables and schema structures in Ignite.
> Until this command is not supported we have to explain that:
> * Many tools use JDBC and ODBC metadata related parameters can pull that
> information out of there and present it to an end user. For instance, SQLline
> utilizes {{!table}} command that gets data from JDBC metadata methods.
> DBeaver utilizes the same approach.
> * Let's create {{Database Administration}} section under SQL reference
> (https://apacheignite-sql.readme.io/docs/sql-reference-overview) and
> presently list approaches supported by various tools (sqlline, dbeaver, etc)
> and how to get the same information from the drivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8003) Dead documentation interface element
[ https://issues.apache.org/jira/browse/IGNITE-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8003: Fix Version/s: 2.8 > Dead documentation interface element > > > Key: IGNITE-8003 > URL: https://issues.apache.org/jira/browse/IGNITE-8003 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.4 >Reporter: Peter Ivanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > Attachments: Screen_Shot_2018_03_15_at_11_43_07.png > > > Most of the tables in lists of artifacts (for example on Downloads page) have > strange interface element settling down to the right, which does nothing (see > [^Screen_Shot_2018_03_15_at_11_43_07.png]). > I guess it should be either removed or fixed, whatever designation it has. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8091) Create Ignite monitoring guide describing metrics and monitoring facilities
[ https://issues.apache.org/jira/browse/IGNITE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8091: Fix Version/s: (was: 2.8) > Create Ignite monitoring guide describing metrics and monitoring facilities > --- > > Key: IGNITE-8091 > URL: https://issues.apache.org/jira/browse/IGNITE-8091 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Priority: Major > Labels: iep-6 > > Ignite doesn't have a single documentation section which would aggregate all > the metrics the project has. There are random documentation pages spread out > across data grid, memory, persistence and other topics. > The new section will include the following: > * How to gather metrics (JMX, logs, APIs) > * Detailed metrics coverage for memory, persistence, rebalancing, compute, > etc. Consider IGNITE-8078 and IGNITE-8077 > * Monitoring tools > * How to integrate with 3rd party tools. > Use a draft of a monitoring guide as a reference: > https://docs.google.com/document/d/1yl7XoiWWPg_XGhwZJUg9Mm3muEApefoMiNLxEUxggV4/edit# -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9406: Fix Version/s: (was: 2.7) 2.8 > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
