[JBoss JIRA] (ISPN-9801) ClusterTopologyManagerImpl hangs when restarting a node with FORK
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-9801?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-9801:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> ClusterTopologyManagerImpl hangs when restarting a node with FORK
> -----------------------------------------------------------------
>
> Key: ISPN-9801
> URL: https://issues.redhat.com/browse/ISPN-9801
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.Alpha1, 9.4.3.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1
>
>
> When a server is restarted with `kill -9` or similar, both the old node and the new one can be in the JGroups view for a while. Normally this shouldn't be a problem, but sometimes the new node doesn't receive the {{HeartBeatCommand}} and the coordinator cannot process any new view updates.
> {noformat}
> 14:29:19,981 INFO (jgroups-12,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE]
> 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [ClusterTopologyManagerImpl] Updating cluster members for all the caches. New list is [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE]
> 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [JGroupsTransport] Test-NodeA sending request 9 to all: org.infinispan.topology.HeartBeatCommand@1163beb6
> 14:29:19,986 TRACE (jgroups-6,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeC: SuccessfulResponse(null)
> 14:29:19,987 TRACE (jgroups-9,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeD: SuccessfulResponse(null)
> 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [TCP_NIO2] Test-NodeE: received message batch of 1 messages from Test-NodeA
> 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: message Test-NodeA::39 was added to queue (not yet server)
> 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: received Test-NodeA#38
> 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: delivering Test-NodeA#38
> # not actually delivered :)
> 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [MFC] Test-NodeA used 5 credits, 1999995 remaining
> 14:29:20,149 INFO (ForkThread-1,ForkChannelRestartTest:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE]
> 14:29:21,119 DEBUG (testng-Test-1:[]) [ForkChannelRestartTest] Stopping channel Test-NodeB
> 14:29:23,319 INFO (VERIFY_SUSPECT.TimerThread-32,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|5] (4) [Test-NodeA, Test-NodeC, Test-NodeD, Test-NodeE]
> 14:29:23,320 TRACE (remote-thread-Test-NodeA-p2-t1:[]) [MultiTargetRequest] Target Test-NodeB of request 9 left the cluster view
> {noformat}
> So far, it looks like it's a JGroups bug similar to JGRP-2294, but we need to investigate further.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11170?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11170:
------------------------------------------
Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38)
> Infinispan directory does not work with pre-declared indexed entities
> ---------------------------------------------------------------------
>
> Key: ISPN-11170
> URL: https://issues.redhat.com/browse/ISPN-11170
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.2.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 9.4.18.Final, 10.1.2.Final
>
>
> This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started.
> This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10723) JMX registration cleanup
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10723?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10723:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> JMX registration cleanup
> ------------------------
>
> Key: ISPN-10723
> URL: https://issues.redhat.com/browse/ISPN-10723
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.CR1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> - all jmx registration should happen via CacheManagerJmxRegistration/CacheJmxRegistration - we should not have other classes using JmxUtil.buildJmxDomain
> - there are very few legitimate direct usages of JmxUtil.lookupMBeanServer; all else must go
> - some registrations are not currently ResourceDMBeans; these need to be converted
> - use of registerExternalMBean should be converted to registerMBean
> - avoid performing the unregistration manually. Components registered with registerMBean will be unregistered automatically
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10544) Remove dependencies on java.beans module
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10544?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10544:
------------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Remove dependencies on java.beans module
> -----------------------------------------
>
> Key: ISPN-10544
> URL: https://issues.redhat.com/browse/ISPN-10544
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 10.0.0.CR1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.CR2
>
>
> Some Infinispan morning fitness to shed off java beans module
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10534) ProtoStreamMarshaller.getSerializationContext fails with unclear message
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10534?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10534:
------------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> ProtoStreamMarshaller.getSerializationContext fails with unclear message
> ------------------------------------------------------------------------
>
> Key: ISPN-10534
> URL: https://issues.redhat.com/browse/ISPN-10534
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 9.4.16.Final, 10.0.0.CR1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.CR2, 9.4.17.Final
>
>
> The marshaller could be null for many reasons, so a clearer error message is needed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-6161) [Remote query] Indexes should be created only for annotated message types
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-6161?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-6161:
-----------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> [Remote query] Indexes should be created only for annotated message types
> -------------------------------------------------------------------------
>
> Key: ISPN-6161
> URL: https://issues.redhat.com/browse/ISPN-6161
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Modify behaviour of indexing for protobuf entities: Current behaviour is: if the message types is not annotated then we index all its fields; if some fields are annotated then index those fields only. New behaviour: index only the annotated fields.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-4075?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-4075:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> State transfer should preserve the creation timestamp of entries
> ----------------------------------------------------------------
>
> Key: ISPN-4075
> URL: https://issues.redhat.com/browse/ISPN-4075
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1, 10.0.0.Final
>
>
> State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended.
> The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-4915) Support flags for REST endpoint
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-4915?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-4915:
-----------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Support flags for REST endpoint
> -------------------------------
>
> Key: ISPN-4915
> URL: https://issues.redhat.com/browse/ISPN-4915
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Reporter: Tristan Tarrant
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: hackathon
> Fix For: 10.0.0.CR3
>
>
> For protocol symmetry, we should add support for the operation flags (e.g. SKIP_CACHE_LOAD, SKIP_INDEXING, etc) on the REST operations using some form of custom header
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months