[jira] [Commented] (IGNITE-12147) Thin client: Partitions response doesn't contain caches for which affinity awareness is not applicable
[ https://issues.apache.org/jira/browse/IGNITE-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930969#comment-16930969 ] Igor Sapego commented on IGNITE-12147: -- Ok, tests pass so everything looks good. > Thin client: Partitions response doesn't contain caches for which affinity > awareness is not applicable > -- > > Key: IGNITE-12147 > URL: https://issues.apache.org/jira/browse/IGNITE-12147 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-23 > Time Spent: 0.5h > Remaining Estimate: 0h > > Partitions response never contains caches for which affinity awareness is not > applicable (unlike specified by the protocol) even if information for these > caches was explicitly requested. > .NET thin client also fails while processing messages for caches without > partitions information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12147) Thin client: Partitions response doesn't contain caches for which affinity awareness is not applicable
[ https://issues.apache.org/jira/browse/IGNITE-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930916#comment-16930916 ] Igor Sapego commented on IGNITE-12147: -- Looks good to me. I've run additional tests on TC though - let's see if the Win suites passing too. > Thin client: Partitions response doesn't contain caches for which affinity > awareness is not applicable > -- > > Key: IGNITE-12147 > URL: https://issues.apache.org/jira/browse/IGNITE-12147 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-23 > Time Spent: 0.5h > Remaining Estimate: 0h > > Partitions response never contains caches for which affinity awareness is not > applicable (unlike specified by the protocol) even if information for these > caches was explicitly requested. > .NET thin client also fails while processing messages for caches without > partitions information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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-12122) Remove setIncludeEventTypes from GridAbstractTest.
[
https://issues.apache.org/jira/browse/IGNITE-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930720#comment-16930720
]
Ignite TC Bot commented on IGNITE-12122:
{panel:title=Branch: [pull/6825/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4600914buildTypeId=IgniteTests24Java8_RunAll]
> Remove setIncludeEventTypes from GridAbstractTest.
> --
>
> Key: IGNITE-12122
> URL: https://issues.apache.org/jira/browse/IGNITE-12122
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Attachments: flamegraph-18988.svg
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Simple cache.put() hot threads measurements shows that
> GridCacheEventManager::addEvent consumes about 7% of overall time, i suggest
> to remove this events from GridAbstractTest::getConfiguration and stores only
> for really requiring tests.
--
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=16930702#comment-16930702 ] Oleg Popov commented on IGNITE-12146: - Igor Sapego I had already done it before creation of this request. I increased the DEFAULT_IO_TIMEOUT to 60 and the error message was gone. But it is not a convinient way to change the constant every time, that is why I created this issue. PS. I don't use Ignite anymore, feel free to close the issue. > 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-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.
[
https://issues.apache.org/jira/browse/IGNITE-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930700#comment-16930700
]
Ignite TC Bot commented on IGNITE-12027:
{panel:title=Branch: [pull/6738/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4602165buildTypeId=IgniteTests24Java8_RunAll]
> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
> at
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap =
> ctx.topology().partitionMap(false);}} is null.
--
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=16930659#comment-16930659 ] Igor Sapego commented on IGNITE-12146: -- [~livelace], are you sure that this is a rootcause of your issue? You can easily check it by simply changing DEFALT_IO_TIMEOUT constant to something bigger like 20, rebuilding Ignite and check, if the issue persists. Just to be sure that we are fixing a right issue. > 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-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=16930654#comment-16930654
]
Igor Sapego commented on IGNITE-12032:
--
You can start investigating this issue from ClientListenerProcessor if you feel
like contributing. This is where all the handling related to ODBC, JDBC thin
and Thin Clients happens.
> 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.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=16930651#comment-16930651
]
Igor Sapego commented on IGNITE-12032:
--
I agree, we need to fix this. Setting the priority to minor though, as this
does not seem like something that may break user application. Looks like a good
issue for a newbie too. [~levagafonov], would you like to try and fix it
yourself maybe? I've seen your email on devlist stating that you would like to
contribute Ignite.
> 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.2#803003)
[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
]
Igor Sapego updated IGNITE-12032:
-
Priority: Minor (was: Major)
> 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.2#803003)
[jira] [Created] (IGNITE-12174) NPE during expiration of spatial data when durable memory is active
Jan Schäfer created IGNITE-12174:
Summary: NPE during expiration of spatial data when durable memory
is active
Key: IGNITE-12174
URL: https://issues.apache.org/jira/browse/IGNITE-12174
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 2.7.5
Environment: Ignite 2.7.5
* ignite-core
* ignite-indexing
* ignite-geospatial
Durable memory activated
Geospatial indexing in use
Reporter: Jan Schäfer
Attachments: IgniteBug.java
I get a NullPointerException when I restart my Ignite instance with durable
memory activated and geospatial data in use:
{code:java}
SEVERE: Critical system error detected. Will be handled accordingly to
configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]SEVERE:
Critical system error detected. Will be handled accordingly to configured
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]java.lang.NullPointerException at
org.apache.ignite.internal.processors.query.h2.opt.GridH2SpatialIndex.remove(GridH2SpatialIndex.java:249)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2SpatialIndex.removex(GridH2SpatialIndex.java:263)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.remove(GridH2Table.java:525)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:801)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2557)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:435)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:2736)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:2713)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.remove(GridCacheOffheapManager.java:2131)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:663)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:4441)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onExpired(GridCacheMapEntry.java:4134)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:4056)
at
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:61)
at
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:52)
at
org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapManager.java:2413)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.java:2343)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:980)
at
org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:207)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:150)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
Minimal reproducing code sample is attached:
# start IgniteBug one time
# wait some seconds
# start IgniteBug a second time
# see NullPointerException from above
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930631#comment-16930631 ] Dmitriy Pavlov commented on IGNITE-5355: [~lexa], I would not name it as a top-1 priority, better to say: It is nice to have. BTW, Release notes field is already available in the JIRA, so if someone contributes such tool - it is convenient and needed investment into release automation. If we don't have this kind of tool, we can release Ignite without it. Which is why I was asking about if you want to finalize this ticket or we can close it (as incomplete/won't fix/fixed). If you're interested, probably it's worth to start a new discussion about this tool and share the intent to do/finalize it. We can understand the vision of all community members > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev >Priority: Major > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided
[ https://issues.apache.org/jira/browse/IGNITE-11976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930621#comment-16930621 ] kcheng.mvp commented on IGNITE-11976: - TeamCity is green : https://ci.ignite.apache.org/viewLog.html?buildId=4599188=IgniteTests24Java8_BuildApacheIgnite=buildResultsDiv_IgniteTests24Java8=pull%2F6868%2Fhead > @SpringResource is silently ignored if no Spring context is provided > > > Key: IGNITE-11976 > URL: https://issues.apache.org/jira/browse/IGNITE-11976 > Project: Ignite > Issue Type: Improvement > Components: spring >Affects Versions: 2.7 >Reporter: Stanislav Lukyanov >Assignee: kcheng.mvp >Priority: Major > Labels: newbie > > @SpringResource annotation is silently ignored and the annotated field is > null if Spring context. > For @SpringResource to work the node needs to be started with > IgniteSpring::start instead of Ignition::start, but the user may not know > that. > Need to add a warning for this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-9836) Invalid check of ea java versions
[
https://issues.apache.org/jira/browse/IGNITE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930612#comment-16930612
]
Peter Ivanov commented on IGNITE-9836:
--
Leaved comments in PR.
> Invalid check of ea java versions
> -
>
> Key: IGNITE-9836
> URL: https://issues.apache.org/jira/browse/IGNITE-9836
> Project: Ignite
> Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On check of '1.8.0_192-ea' java version in ignite.sh the next messages in
> console are printed:
> {code:java}
> ./include/functions.sh: line 81: [: -lt: unary operator expected
> ./ignite.sh: line 61:
> /home/vsisko/Downloads/distr/bin/include/build-classpath.sh: No such file or
> directory
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (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:all-tabpanel
]
Peter Ivanov reassigned IGNITE-12139:
-
Assignee: Dmitriy Pavlov (was: Peter Ivanov)
> 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] [Updated] (IGNITE-12172) [IEP-35] OpenCensusMetricExporterSpiTest isn't added to any test suite
[
https://issues.apache.org/jira/browse/IGNITE-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-12172:
-
Labels: IEP-35 (was: )
> [IEP-35] OpenCensusMetricExporterSpiTest isn't added to any test suite
> --
>
> Key: IGNITE-12172
> URL: https://issues.apache.org/jira/browse/IGNITE-12172
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
>
> {{OpenCensusMetricExporterSpiTest}} isn't added to any test suite. As result
> tests do not run on TC.
--
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=16930528#comment-16930528
]
Peter Ivanov commented on IGNITE-12139:
---
[ignite-2.7.5|https://ci.ignite.apache.org/viewLog.html?buildId=4601798=Releases_ApacheIgniteMain_ReleaseBuild=artifacts#%2Frelease-2.7.5-rc5.zip!%2Fpackages]
is rebuilt with proper hash.
[~dpavlov] — can you resign and reupload packages, please?
> 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: Peter Ivanov
>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] [Updated] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core
[
https://issues.apache.org/jira/browse/IGNITE-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-10554:
Priority: Critical (was: Major)
> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.8
>
>
> We use PowerShell script to update post-build event in the target project and
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
>
>
>
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
>
>
>
>
>
>
> copyToOutput="true" />
>
>
> {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
> in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to
> the output folder.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core
[
https://issues.apache.org/jira/browse/IGNITE-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-10554:
Description:
We use PowerShell script to update post-build event in the target project and
copy jar files to target directory during build.
However, this no longer works with .NET Core.
nuspec file should be updated with new format, see example from
https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
{code}
ContentFilesExample
1.0.0
nuget
nuget
false
A content v2 example package.
contentv2 contentFiles
https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
in .NET Core 3.0:
??The dotnet build command now copies NuGet dependencies for your application
from the NuGet cache to the build output folder??
In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR files
are resolved.
In 3.0 this does not work anymore, we should find a way to copy JAR files to
the output folder.
was:
We use PowerShell script to update post-build event in the target project and
copy jar files to target directory during build.
However, this no longer works with .NET Core.
nuspec file should be updated with new format, see example from
https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
{code}
ContentFilesExample
1.0.0
nuget
nuget
false
A content v2 example package.
contentv2 contentFiles
.NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.8
>
>
> We use PowerShell script to update post-build event in the target project and
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
>
>
>
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
>
>
>
>
>
>
> copyToOutput="true" />
>
>
> {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
> in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to
> the output folder.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12173) Fix http links
[
https://issues.apache.org/jira/browse/IGNITE-12173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930512#comment-16930512
]
Peter Ivanov commented on IGNITE-12173:
---
[~dmagda], please review.
> 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] [Created] (IGNITE-12173) Fix http links
Peter Ivanov created IGNITE-12173:
-
Summary: 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
Fix For: 2.8
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] [Created] (IGNITE-12172) [IEP-35] OpenCensusMetricExporterSpiTest isn't added to any test suite
Andrey Gura created IGNITE-12172:
Summary: [IEP-35] OpenCensusMetricExporterSpiTest isn't added to
any test suite
Key: IGNITE-12172
URL: https://issues.apache.org/jira/browse/IGNITE-12172
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Gura
Fix For: 2.8
{{OpenCensusMetricExporterSpiTest}} isn't added to any test suite. As result
tests do not run on TC.
--
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=16930492#comment-16930492
]
Peter Ivanov commented on IGNITE-12139:
---
[~dpavlov], I do not know what happened, thus — there is nothing to prevent yet.
Possibly the process it self was ignored or overridden in some points.
> 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: Peter Ivanov
>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-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=16930489#comment-16930489
]
Dmitriy Pavlov commented on IGNITE-12139:
-
[~vveider], [~dmagda] should we somehow update/fix release process to avoid
such issues in the future?
> 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: Peter Ivanov
>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] [Assigned] (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:all-tabpanel
]
Peter Ivanov reassigned IGNITE-12139:
-
Assignee: Peter Ivanov (was: Dmitriy Pavlov)
> 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: Peter Ivanov
>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-12168) [ML] Flaky ML example tests
[ https://issues.apache.org/jira/browse/IGNITE-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930475#comment-16930475 ] Aleksey Zinoviev commented on IGNITE-12168: --- [~Pavlukhin] Many thanks, waited for feedback from user > [ML] Flaky ML example tests > --- > > Key: IGNITE-12168 > URL: https://issues.apache.org/jira/browse/IGNITE-12168 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Time Spent: 20m > Remaining Estimate: 0h > > Discussed here > [http://apache-ignite-developers.2346864.n4.nabble.com/After-IGNITE-12148-the-Examples-suite-has-unstable-tests-td43469.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12142) Ignite ignores that on-heap store is disabled when putting values through near cache
[
https://issues.apache.org/jira/browse/IGNITE-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930442#comment-16930442
]
Bartłomiej Stefański commented on IGNITE-12142:
---
[~DmitriyGovorukhin], [~agoncharuk] did you get a chance to look into this?
Please let me know if you need more info.
> Ignite ignores that on-heap store is disabled when putting values through
> near cache
>
>
> Key: IGNITE-12142
> URL: https://issues.apache.org/jira/browse/IGNITE-12142
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7, 2.7.5
>Reporter: Bartłomiej Stefański
>Priority: Major
>
> I have an Ignite cluster that consists of two nodes:
> * @n0 - server node
> * @n1 - client node
> Installed PARTITIONED cache {{myCache}} on both of them. Cache has near cache
> on client node and disabled on-heap caching on server.
> Server configuration:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
>
> {code}
> Client configuration:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>
>
>
>
>
>
>
>
>
>
> {code}
> I have noticed (using visor) strange cache state after putting 20k entries to
> that cache through client node (@n1):
> {code}
> +==+
> | Node ID8(@), IP | CPUs | Heap Used | CPU Load | Up Time|
> Size (Primary / Backup)| Hi/Mi/Rd/Wr |
> +==+
> | 99E64885(@n0), 172.17.0.1 | 4| 2.56 %| 0.50 % | 00:02:47.615 |
> Total: 4 (4 / 0) | Hi: 0 |
> | | | | | |
> Heap: 2 (2 / ) | Mi: 0 |
> | | | | | |
> Off-Heap: 2 (2 / 0) | Rd: 0 |
> | | | | | |
> Off-Heap Memory: | Wr: 0 |
> +---+--+---+--+--+---+-+
> | FE7BEE4F(@n1), 172.17.0.1 | 4| 3.89 %| 3.10 % | 00:02:37.269 |
> Total: 1000 (1000 / 0)| Hi: 0 |
> | | | | | |
> Heap: 1000 (1000 / ) | Mi: 0 |
> | | | | | |
> Off-Heap: 0 (0 / 0) | Rd: 0 |
> | | | | | |
> Off-Heap Memory: 0 | Wr: 0 |
> +--+
> {code}
> Why Ignite stores entries on heap space on server node? If I put 20k entries
> through server node then server on-heap space is not used:
> {code}
> +==+
> | Node ID8(@), IP | CPUs | Heap Used | CPU Load | Up Time|
> Size (Primary / Backup)| Hi/Mi/Rd/Wr |
> +==+
> | 9C1D895B(@n0), 172.17.0.1 | 4| 1.68 %| 0.43 % | 00:15:44.149 |
> Total: 2 (2 / 0) | Hi: 0 |
>
[jira] [Commented] (IGNITE-12171) Remove the MetricRegistry.remove(String name) method.
[
https://issues.apache.org/jira/browse/IGNITE-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930426#comment-16930426
]
Amelchev Nikita commented on IGNITE-12171:
--
[~agura] Thank you. I'll close the issue as won't fix
> Remove the MetricRegistry.remove(String name) method.
> -
>
> Key: IGNITE-12171
> URL: https://issues.apache.org/jira/browse/IGNITE-12171
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I suggest removing the unused {{MetricRegistry.remove(String name)}} method
> due to we can remove a subset of metrics using the
> {{GridMetricManager.remove(String regName)}} method with notifying mechanism.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-12171) Remove the MetricRegistry.remove(String name) method.
[
https://issues.apache.org/jira/browse/IGNITE-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita resolved IGNITE-12171.
--
Resolution: Won't Fix
> Remove the MetricRegistry.remove(String name) method.
> -
>
> Key: IGNITE-12171
> URL: https://issues.apache.org/jira/browse/IGNITE-12171
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I suggest removing the unused {{MetricRegistry.remove(String name)}} method
> due to we can remove a subset of metrics using the
> {{GridMetricManager.remove(String regName)}} method with notifying mechanism.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12171) Remove the MetricRegistry.remove(String name) method.
[
https://issues.apache.org/jira/browse/IGNITE-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930419#comment-16930419
]
Andrey Gura commented on IGNITE-12171:
--
Will done as part of IGNITE-11927 issue. Metric registries will be immutable.
See also dev-list topic
http://apache-ignite-developers.2346864.n4.nabble.com/IEP-35-Metrics-management-in-Ignite-td43243.html
> Remove the MetricRegistry.remove(String name) method.
> -
>
> Key: IGNITE-12171
> URL: https://issues.apache.org/jira/browse/IGNITE-12171
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I suggest removing the unused {{MetricRegistry.remove(String name)}} method
> due to we can remove a subset of metrics using the
> {{GridMetricManager.remove(String regName)}} method with notifying mechanism.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-12171) Remove the MetricRegistry.remove(String name) method.
[
https://issues.apache.org/jira/browse/IGNITE-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-12171:
-
Labels: IEP-35 (was: )
> Remove the MetricRegistry.remove(String name) method.
> -
>
> Key: IGNITE-12171
> URL: https://issues.apache.org/jira/browse/IGNITE-12171
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I suggest removing the unused {{MetricRegistry.remove(String name)}} method
> due to we can remove a subset of metrics using the
> {{GridMetricManager.remove(String regName)}} method with notifying mechanism.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12171) Remove the MetricRegistry.remove(String name) method.
Amelchev Nikita created IGNITE-12171:
Summary: Remove the MetricRegistry.remove(String name) method.
Key: IGNITE-12171
URL: https://issues.apache.org/jira/browse/IGNITE-12171
Project: Ignite
Issue Type: Task
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
Fix For: 2.8
I suggest removing the unused {{MetricRegistry.remove(String name)}} method due
to we can remove a subset of metrics using the
{{GridMetricManager.remove(String regName)}} method with notifying mechanism.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12170) DOC: Advanced security should be better documented
Andrey Aleksandrov created IGNITE-12170: --- Summary: DOC: Advanced security should be better documented Key: IGNITE-12170 URL: https://issues.apache.org/jira/browse/IGNITE-12170 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.7.5 Reporter: Andrey Aleksandrov Fix For: 2.8 [https://apacheignite.readme.io/docs/advanced-security#section-enable-authentication] After applying the example, in the server log you can see: [12:44:11] Security status [authentication=off, tls/ssl=off] After that, I was able to connect the client without any username/password. So looks like we should add into documentation the information about how it works. I checked that it worked with thin clients and web console. But for user it can be not clear that authentication between nodes doesn' work out of the boxes. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12168) [ML] Flaky ML example tests
[ https://issues.apache.org/jira/browse/IGNITE-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930388#comment-16930388 ] Ivan Pavlukhin commented on IGNITE-12168: - [~zaleslaw], should the ticket be resolved as PR is merged? Could you please do it? > [ML] Flaky ML example tests > --- > > Key: IGNITE-12168 > URL: https://issues.apache.org/jira/browse/IGNITE-12168 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Time Spent: 20m > Remaining Estimate: 0h > > Discussed here > [http://apache-ignite-developers.2346864.n4.nabble.com/After-IGNITE-12148-the-Examples-suite-has-unstable-tests-td43469.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12169) Dockerfile: Thin Client and REST API ports are not exposed
[ https://issues.apache.org/jira/browse/IGNITE-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12169: Fix Version/s: 2.8 > Dockerfile: Thin Client and REST API ports are not exposed > -- > > Key: IGNITE-12169 > URL: https://issues.apache.org/jira/browse/IGNITE-12169 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.8 > > > Expose Thin Client (10800) and REST API (8080) ports in Dockerfiles (both > apache-ignite and apache-ignite-net) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (IGNITE-12169) Dockerfile: Thin Client and REST API ports are not exposed
[ https://issues.apache.org/jira/browse/IGNITE-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-12169. - Reviewer: Peter Ivanov Resolution: Fixed > Dockerfile: Thin Client and REST API ports are not exposed > -- > > Key: IGNITE-12169 > URL: https://issues.apache.org/jira/browse/IGNITE-12169 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > > Expose Thin Client (10800) and REST API (8080) ports in Dockerfiles (both > apache-ignite and apache-ignite-net) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12169) Dockerfile: Thin Client and REST API ports are not exposed
[ https://issues.apache.org/jira/browse/IGNITE-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12169: Ignite Flags: (was: Docs Required,Release Notes Required) > Dockerfile: Thin Client and REST API ports are not exposed > -- > > Key: IGNITE-12169 > URL: https://issues.apache.org/jira/browse/IGNITE-12169 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > > Expose Thin Client (10800) and REST API (8080) ports in Dockerfiles (both > apache-ignite and apache-ignite-net) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12169) Dockerfile: Thin Client and REST API ports are not exposed
[ https://issues.apache.org/jira/browse/IGNITE-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930375#comment-16930375 ] Pavel Tupitsyn commented on IGNITE-12169: - Merged to master: 16caa76f6e703ed5bc04eaa7e9fd702686e1e238 > Dockerfile: Thin Client and REST API ports are not exposed > -- > > Key: IGNITE-12169 > URL: https://issues.apache.org/jira/browse/IGNITE-12169 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > > Expose Thin Client (10800) and REST API (8080) ports in Dockerfiles (both > apache-ignite and apache-ignite-net) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12169) Dockerfile: Thin Client and REST API ports are not exposed
Pavel Tupitsyn created IGNITE-12169: --- Summary: Dockerfile: Thin Client and REST API ports are not exposed Key: IGNITE-12169 URL: https://issues.apache.org/jira/browse/IGNITE-12169 Project: Ignite Issue Type: Bug Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Expose Thin Client (10800) and REST API (8080) ports in Dockerfiles (both apache-ignite and apache-ignite-net) -- This message was sent by Atlassian Jira (v8.3.2#803003)
