Re: Unsubcribe
please send an empty message to: user-unsubscr...@ignite.apache.org to unsubscribe yourself from the list. On 2021/11/23 2:29 上午, kelum madusanka wrote: Please unsubcribe
Re: Windows installation
That's all right. thank you. On 2021/11/22 10:27 下午, Pavel Tupitsyn wrote: Yes, Ignite can be deployed on Windows. We run our full test suite both on Windows and Linux.
Unsubcribe
Please unsubcribe
Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start
Hi Sergey!
Seems that the root cause of your problem is possible corruption of data
page
Caused by: java.lang.IllegalStateException: Item not found: 3
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.AbstractDataPageIO.findIndirectItemIndex(AbstractDataPageIO.java:476)
and it happened twice, not during expiration cleanup, but also during
rebalance eviction. But your scenario looks quite usual and couldn't cause
such problems.
I've found similar existing ticket
https://issues.apache.org/jira/browse/IGNITE-11400
but assignee couldn't reproduce the error.
Could you please provide more information about what had happened on your
cluster before and about cache configuration? Do you use expiration on
persistent caches? Any details can be useful for the problem localization.
Denis Chudov
Software Engineer, Moscow
+7 905 5775239
https://www.gridgain.com
Powered by Apache® Ignite™
On Thu, Nov 18, 2021 at 2:25 PM Sergey Korotkov
wrote:
> Hello,
>
> We have troubles with the CorruptedTreeException: B+Tree is corrupted
> during the node start after cluster restart. Looks like the caches with
> the Expiry Policy configured are source of the problems.
>
> I have attached the log from the problem node. The exact steps with
> timestamps are as folows. Before the deactivation cluster works fine
> about 5 days
>
> 2021-11-08 10:54:44 cluster deactivate request
>
> 2021-11-08 10:59:33 cluster deactivated
>
> 2021-11-08 11:02:30 stop all nodes
>
> 2021-11-08 11:02:39 start all nodes
>
> 2021-11-08 11:03:14 auto-activation start
>
> 2021-11-08 11:03:16 cluster activated
>
> 2021-11-08 11:03:21 'B+Tree is corrupted' exception in
> GridCacheTtlManager.expire() on one of the nodes (see the
> 10.12.86.29-ignite-2021-11-08.0.log):
>
> [2021-11-08 11:03:21,820][ERROR][ttl-cleanup-worker-#215][ROOT]{}
> Critical system error detected. Will be handled accordingly to
> configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false,
> timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree
> is corrupted [pages(groupId, pageId)=[], msg=Runtime failure on bounds:
> [lower=null, upper=PendingRow []
>
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[], msg=Runtime failure on
> bounds: [lower=null, upper=PendingRow []]]
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6139)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1133)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1100)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1095)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapManager.java:3076)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.java:3023)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:1255)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:246)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.lambda$body$0(GridCacheSharedTtlCleanupManager.java:193)
> at
>
> java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1769)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:192)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by:
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
> java.lang.IllegalStateException: Item not found: 3
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findLowerUnbounded(BPlusTree.java:1079)
> at
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1118)
> ... 11 common frames omitted
> Caused by:
>
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
> java.lang.IllegalStateException: Item not found: 3
> at
>
> org.apache.ignite.internal.processo
Re: BinaryObjectException
Thin client before version 2.9 throws an exception when there is more than one scheme with the same type name and compact footers are enabled. The scheme is a set of field names of the object, so, using only one scheme per type (if it's possible in your case) will solve the problem. If you don't want to update Ignite server, you can update only thin client, it will also solve the problem. пн, 22 нояб. 2021 г. в 12:57, Naveen Kumar : > Thanks Alex.. > Here it says it throws this exception when ignite does not find this record > In our case, data exists and it get resolved if we do a node restart > > And, any work-around we have to fix this issue with current version > ignite 2.8.1 > > Thanks > > On Mon, Nov 22, 2021 at 12:20 PM Alex Plehanov > wrote: > >> Hello! >> >> Most probably it's related to ticket [1] that is fixed in 2.9 release. >> >> [1]: https://issues.apache.org/jira/browse/IGNITE-13192 >> >> пн, 22 нояб. 2021 г. в 03:11, Naveen Kumar : >> >>> Hi All >>> >>> We are using 2.8.1 >>> At times, we do get this BinaryObjectException while calling GETs thru >>> thin client, we dont see any errors or exceptions on node logs, this only >>> be seen on the cline tside. >>> what could be the potential reason for this >>> >>> Attached the exact error message >>> >>> >>> >>> >>> Thanks >>> >>> -- >>> Thanks & Regards, >>> Naveen Bandaru >>> >> > > -- > Thanks & Regards, > Naveen Bandaru >
Re: Affinity function with thin clients
You can use define one or more cache templates [1] with a custom affinity function (or any other setting) on the server side, then create caches using the template from the thin client. [1] https://ignite.apache.org/docs/latest/configuring-caches/configuration-overview#cache-templates On Mon, Nov 22, 2021 at 5:56 PM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > I think you’ll either have to configure that on the server side or in a > thick-client. > > > On 22 Nov 2021, at 14:42, R. Subhash Babu wrote: > > > > Hi Igniters, > > > > I am trying to create a cache using a thin client > (ClientCacheConfiguration) and trying to see how I can > > > > 1) provide affinity function > > 2) restrict the number of partitions of the cache > > > > Any possible approach please? > > > > Thanks > > Subhash > > >
Re: Affinity function with thin clients
I think you’ll either have to configure that on the server side or in a thick-client. > On 22 Nov 2021, at 14:42, R. Subhash Babu wrote: > > Hi Igniters, > > I am trying to create a cache using a thin client (ClientCacheConfiguration) > and trying to see how I can > > 1) provide affinity function > 2) restrict the number of partitions of the cache > > Any possible approach please? > > Thanks > Subhash
Affinity function with thin clients
Hi Igniters, I am trying to create a cache using a thin client (ClientCacheConfiguration) and trying to see how I can 1) provide affinity function 2) restrict the number of partitions of the cache Any possible approach please? Thanks Subhash
Re: Windows installation
Yes, Ignite can be deployed on Windows. We run our full test suite both on Windows and Linux. On Mon, Nov 22, 2021 at 4:25 PM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > I’d say Windows is used more often for development than production, but > yes, it works. > > On 22 Nov 2021, at 13:12, yong...@laposte.net wrote: > > Can I install Ignite in Windows server? Thanks. > > > >
Re: Windows installation
I’d say Windows is used more often for development than production, but yes, it works. > On 22 Nov 2021, at 13:12, yong...@laposte.net wrote: > > Can I install Ignite in Windows server? Thanks.
Windows installation
Can I install Ignite in Windows server? Thanks.
Re: Unable to join using thick client when authentication is enabled
Hi,
I created a ticket about this problem:
https://issues.apache.org/jira/browse/IGNITE-15969
пт, 19 нояб. 2021 г. в 22:46, Shishkov Ilya :
> Hi,
> I've reproduced it for 2.11. In case of turned on authentication, thick
> clients won't connect until you enable persistence for them. Because thick
> clients have no persistence, you can use it like a workaround. Certainly,
> it looks like a bug.
>
> пт, 19 нояб. 2021 г. в 16:42, Ganguly Gundeboina >:
>
>> Hi Stephen,
>>
>> Same already tried, but it's giving below error even though we have
>> enabled persistence.
>>
>> #
>>
>> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
>> SYSTEM_CRITICAL_OPERATION_TIMEOUT
>>
>> [18:03:39] Message queue limit is set to 0 which may lead to potential
>> OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due
>> to message queues growth on sender and receiver sides.
>>
>> [18:03:49] Security status [authentication=on, sandbox=off, tls/ssl=off]
>>
>> Nov 19, 2021 6:03:50 PM org.apache.ignite.logger.java.JavaLogger error
>>
>> SEVERE: Exception during start processors, node will be stopped and close
>> connections
>>
>> class org.apache.ignite.IgniteCheckedException: Authentication can be
>> enabled only for cluster with enabled persistence. Check the
>> DataRegionConfiguration
>>
>> at
>> org.apache.ignite.internal.processors.authentication.IgniteAuthenticationProcessor.startProcessor(IgniteAuthenticationProcessor.java:166)
>>
>> at
>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1259)
>>
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2141)
>>
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1787)
>>
>> at
>> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1172)
>>
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:668)
>>
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:590)
>>
>> at org.apache.ignite.Ignition.start(Ignition.java:328)
>>
>> at
>> com.jio.digitalapi.edif.util.operations.CacheSizes.main(CacheSizes.java:52)
>>
>>
>>
>> Nov 19, 2021 6:03:50 PM org.apache.ignite.logger.java.JavaLogger error
>>
>> SEVERE: Got exception while starting (will rollback startup routine).
>>
>> class org.apache.ignite.IgniteCheckedException: Authentication can be
>> enabled only for cluster with enabled persistence. Check the
>> DataRegionConfiguration
>>
>> at
>> org.apache.ignite.internal.processors.authentication.IgniteAuthenticationProcessor.startProcessor(IgniteAuthenticationProcessor.java:166)
>>
>>
>>
>>
>> String[] ipAddrArray = igniteNodeIpAddress.split(",", -1);
>> System.*setProperty*("java.net.preferIPv4Stack", "true");
>> IgniteConfiguration cfg = new IgniteConfiguration();
>> cfg.setPeerClassLoadingEnabled(true);
>> cfg.setClientMode(true);
>> cfg.setAuthenticationEnabled(true);
>> String random = (UUID.*randomUUID*().getMostSignificantBits() + ""
>> ).toString().replace("-", "");
>> String igniteFullInstaneName = igniteInstanceName + random;
>> cfg.setIgniteInstanceName(igniteFullInstaneName);
>> cfg.setDiscoverySpi((new TcpDiscoverySpi().setJoinTimeout(240)
>> .setIpFinder((new TcpDiscoveryVmIpFinder()).setAddresses(Arrays.
>> *asList*(ipAddrArray);
>> Ignition.*start*(cfg);
>> ###
>>
>>
>> Regards,
>> Gangaiah
>>
>> On Fri, Nov 19, 2021 at 5:14 PM Stephen Darlington <
>> stephen.darling...@gridgain.com> wrote:
>>
>>> Thick clients don’t need to authenticate, but they do need to have the
>>> same authentication settings as the server nodes, i.e., set
>>> IgniteConfiguration#setAuthenticationEnabled(true).
>>>
>>> On 19 Nov 2021, at 11:28, Ganguly Gundeboina
>>> wrote:
>>>
>>> Hi Pavel,
>>>
>>> Yes, we have enabled authentication on server nodes only.
>>>
>>> We could provide user credentials for thin clients, so thin clients are
>>> able to connect to the cluster after setting username and password at
>>> client side.
>>>
>>> But not able to set user credentials for thik clients, So we have to
>>> disable authentication on server nodes, otherwise thick clients are not
>>> able to connect.
>>>
>>> Regards,
>>> Gangaiah
>>>
>>> On Fri, Nov 19, 2021 at 1:06 PM Pavel Tupitsyn
>>> wrote:
>>>
Hi Gangaiah,
Before 2.11, there was no requirement to have an equal security
processor on all nodes.
It was added as part of [1].
Overall, I think it is a good idea to have security on all nodes
configured in the same way.
Do you have it enabled only on server nodes?
[1] https://issues.apache.org/jira/browse/IGNITE-14335
On Fri, Nov 19, 2021 at 9:42 AM Gang
Re: BinaryObjectException
Thanks Alex.. Here it says it throws this exception when ignite does not find this record In our case, data exists and it get resolved if we do a node restart And, any work-around we have to fix this issue with current version ignite 2.8.1 Thanks On Mon, Nov 22, 2021 at 12:20 PM Alex Plehanov wrote: > Hello! > > Most probably it's related to ticket [1] that is fixed in 2.9 release. > > [1]: https://issues.apache.org/jira/browse/IGNITE-13192 > > пн, 22 нояб. 2021 г. в 03:11, Naveen Kumar : > >> Hi All >> >> We are using 2.8.1 >> At times, we do get this BinaryObjectException while calling GETs thru >> thin client, we dont see any errors or exceptions on node logs, this only >> be seen on the cline tside. >> what could be the potential reason for this >> >> Attached the exact error message >> >> >> >> >> Thanks >> >> -- >> Thanks & Regards, >> Naveen Bandaru >> > -- Thanks & Regards, Naveen Bandaru
