[JBoss JIRA] (ISPN-10013) Observability: Distributed tracing
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10013?page=com.atlassian.jira.plugin... ]
Tristan Tarrant reassigned ISPN-10013:
--------------------------------------
Assignee: Nistor Adrian
> Observability: Distributed tracing
> ----------------------------------
>
> Key: ISPN-10013
> URL: https://issues.jboss.org/browse/ISPN-10013
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We need to add tracing capabalities so that they can be exported/consumed by Jaeger.
> We should use the following spans:
> * container (the default span)
> * persistence (cache stores and loaders)
> * cluster (for same-cluster remoting)
> * xsite (for xsite cluster remoting)
> * security (for authenticaton/authorization)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-10013) Observability: Distributed tracing
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10013?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10013:
-----------------------------------
Status: Open (was: New)
> Observability: Distributed tracing
> ----------------------------------
>
> Key: ISPN-10013
> URL: https://issues.jboss.org/browse/ISPN-10013
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We need to add tracing capabalities so that they can be exported/consumed by Jaeger.
> We should use the following spans:
> * container (the default span)
> * persistence (cache stores and loaders)
> * cluster (for same-cluster remoting)
> * xsite (for xsite cluster remoting)
> * security (for authenticaton/authorization)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ISPN-10029) Transactional invalidation cache with shared store prone to stale reads, even with FORCE_WRITE_LOCK
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10029?page=com.atlassian.jira.plugin... ]
Ryan Emerson commented on ISPN-10029:
-------------------------------------
[~pferraro] This is fixed in `9.4.14.Final`. The fix is in `9.4.x` branch, but not `9.3.x`, hence the ticket is still unresolved and as part of our release process for `9.4.14.Final` the ticket's fix version was incorrectly incremented. [~dan.berindei] We're still waiting on the `9.3` backport when you get a chance.
> Transactional invalidation cache with shared store prone to stale reads, even with FORCE_WRITE_LOCK
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-10029
> URL: https://issues.jboss.org/browse/ISPN-10029
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.3.6.Final, 9.4.11.Final, 10.0.0.Beta3
> Reporter: Paul Ferraro
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 10.0.0.Beta4, 9.3.7.Final, 9.4.14.Final
>
> Attachments: InvalidationLockingTest.java
>
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months