[JBoss JIRA] (ISPN-9932) Avoid creating MarshallableEntry instances if no CacheWriter enabled
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9932?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9932:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> Avoid creating MarshallableEntry instances if no CacheWriter enabled
> --------------------------------------------------------------------
>
> Key: ISPN-9932
> URL: https://issues.jboss.org/browse/ISPN-9932
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha3
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> The (Dist)CacheWriterIntercepter is enabled if any loader/store is configured. The problem, is that the interceptor assumes that a CacheWriter is always configured. However, it is possible that only a CacheLoader has been configured, in which case when a write command visits the interceptor, MarshallableEntry instances are created unnecessarily in order to call the various PersistenceManager write operations.
> To avoid unnecessary allocations and the marshalling of key/value/metadata that is never stored, we should ensure that calls to PersistenceManager write methods are only called if a CacheWriter is actually configured.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-9962) Feature-packs should optionally depend on jdk-unsupported and sun.jdk
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9962?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9962:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> Feature-packs should optionally depend on jdk-unsupported and sun.jdk
> ---------------------------------------------------------------------
>
> Key: ISPN-9962
> URL: https://issues.jboss.org/browse/ISPN-9962
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1
>
>
> Currently our feature-packs depend on both "sun.jdk" and "jdk.unsupported" in an inconsistent manner. For the latest versions of Wildfly, we need to use the latter, whilst for older ones we need to use the former. Therefore, for all modules that require access to unsupported classes, we must provide an optional dependency on both of the above modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of WildFly
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9964:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> Logging incompatibility when deploying modules on older versions of WildFly
> ---------------------------------------------------------------------------
>
> Key: ISPN-9964
> URL: https://issues.jboss.org/browse/ISPN-9964
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-9968) JCacheStateAwarenessIT failure due to infinispan-remote dependency
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9968?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9968:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> JCacheStateAwarenessIT failure due to infinispan-remote dependency
> ------------------------------------------------------------------
>
> Key: ISPN-9968
> URL: https://issues.jboss.org/browse/ISPN-9968
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 10.0.0.Beta1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1
>
>
> ISPN-9554 introduced a dependency on {{infinispan-remote}} on the server/integration/testsuite that results in classes not being loaded as expected. We should remove this dependency and find an alternative solution for ISPN-9554.
> JCacheStateAwarenessIT failure cause:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Logger implementation class org.infinispan.jcache.logging.Log_$logger has no matching constructor
> at org.jboss.logging.Logger$1.run(Logger.java:2562) ~[?:?]
> at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2529) ~[?:?]
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2516) ~[?:?]
> at org.infinispan.commons.logging.LogFactory.getLog(LogFactory.java:18) ~[?:?]
> at org.infinispan.jcache.AbstractJCachingProvider.<clinit>(AbstractJCachingProvider.java:23) ~[?:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:?]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:?]
> at java.lang.Class.newInstance(Class.java:442) ~[?:?]
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) ~[?:?]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-9660) Histogram stats
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9660?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9660:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, 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 (was: Sprint 10.0.0.Alpha1, 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)
> Histogram stats
> ---------------
>
> Key: ISPN-9660
> URL: https://issues.jboss.org/browse/ISPN-9660
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Affects Versions: 9.4.0.Final
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.Final
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-9699) Cluster member owning no data
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9699:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, 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 (was: Sprint 10.0.0.Alpha1, 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)
> Cluster member owning no data
> -----------------------------
>
> Key: ISPN-9699
> URL: https://issues.jboss.org/browse/ISPN-9699
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 9.4.1.Final
> Reporter: Thomas Segismont
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1
>
>
> Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment.
> If you want a node to own no data at all, you could set this property on all declared caches. But this wouldn't work for internal caches anyway (locks, counters).
> It would be nice to have a global switch.
> This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster:
> * there would be no data loss
> * the cluster would be back in healthy state faster as no data would be moved around.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-9498) Index filesystem paths in server should point to data directory
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9498?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9498:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> Index filesystem paths in server should point to data directory
> ---------------------------------------------------------------
>
> Key: ISPN-9498
> URL: https://issues.jboss.org/browse/ISPN-9498
> Project: Infinispan
> Issue Type: Bug
> Components: Indexing, OpenShift, Server
> Affects Versions: 9.4.0.CR1, 9.3.3.Final
> Reporter: Galder Zamarreño
> Assignee: Tristan Tarrant
> Priority: Major
>
> Certain indexing configurations result in using filesystem as index storage.
> When running such configurations in a server environment, filesystem path should be somewhere within the server's data directory. This is the natural place for such data.
> When running in OpenShift, server's data folder can be backed by a persistent volume. This means that the fileystem volume survives after restarts.
> Plugging server's data directory is already happening for [file-store|https://github.com/infinispan/infinispan/blob/master/server/in...] and [rocksdb-store|https://github.com/infinispan/infinispan/blob/master/server...].
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-4915) Support flags for REST endpoint
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-4915?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-4915:
-----------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: DataGrid Sprint #34, DataGrid Sprint #35)
> Support flags for REST endpoint
> -------------------------------
>
> Key: ISPN-4915
> URL: https://issues.jboss.org/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, 8 months
[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/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 (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)
> State transfer should preserve the creation timestamp of entries
> ----------------------------------------------------------------
>
> Key: ISPN-4075
> URL: https://issues.jboss.org/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, 8 months
[JBoss JIRA] (ISPN-6161) [Remote query] Indexes should be created only for annotated message types
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/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 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> [Remote query] Indexes should be created only for annotated message types
> -------------------------------------------------------------------------
>
> Key: ISPN-6161
> URL: https://issues.jboss.org/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, 8 months