2.8.1 : CacheEntryProcessor for insert/update within Transaction supported ?
Hi Team, Is the functionality to use CacheEntryProcessor for insert/update within Transaction supported ? As mentioned in this post, insert of a record using cacheentryprocessor always fails with UnregisteredBinaryTypeException if the insert is done within a transaction : http://apache-ignite-users.70518.x6.nabble.com/Right-Handling-of-UnRegisteredBinaryObjectTypeException-tp35412p35681.html regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: [2.9.1] Custom failure handler is not being invoked
Thank you Alex. I am thinking of setting SegmentationPolicy as *NOOP* and also listening to event EventType.EVT_NODE_SEGMENTED For this event I have added a listener to localListen. The listener will manage the similar work which is done by custom failure handler. Hope this is an acceptable solution for an in-memory distributed cache. Next, I want to avoid segmentation error due to network issues. I am running the ignite and the services in AWS EC2 instance. Will adding security group that allows 47100-47200 and 47500-47600 solve this issue? Thanks, Ashish -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Designing Affinity Key for more locality
Hi William, Can you describe the use case and domain model in more detail? 1. AffinityKey is used to colocate some data with other data. What do you achieve with user-id being the affinity key? 2. If you'd like to put all users for a given tenant/group to the same node for efficiency, then use tenant-id as the user affinity key. UUID is fine, no need for extra logic with ints. On Tue, Apr 27, 2021 at 5:33 AM William.L wrote: > Came across this statement in the Data Partitioning documents: > > "The affinity function determines the mapping between keys and partitions. > Each partition is identified by a number from a limited set (0 to 1023 by > default)." > > Looks like there is no point for adding another layer of mapping unless I > am > going for a smaller number. > Are there other ways in ignite to get more locality for subset of the data? > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
