January 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9622) Replace GlobalMarshaller with protobuf based marshaller

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9622?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9622: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Replace GlobalMarshaller with protobuf based marshaller > ------------------------------------------------------- > > Key: ISPN-9622 > URL: https://issues.jboss.org/browse/ISPN-9622 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The internal marshaller should be responsible for serializing all internal objects sent between infinispan nodes. For user objects it should delegate to the configured user marshaller (jboss-marshaller based for now) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9623) Create Protobuf based user marshaller

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9623?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9623: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Create Protobuf based user marshaller > ------------------------------------- > > Key: ISPN-9623 > URL: https://issues.jboss.org/browse/ISPN-9623 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > With the internal and persistence marshaller being protobuf based, we should also provide a user marshaller implementation that utilises protostream. Users should be able to configure annotated pojos or MessageMarshaller implementations for their objects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9631) REST API should return 503 Service Unavailable if store's becomes unavailable

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9631?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9631: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > REST API should return 503 Service Unavailable if store's becomes unavailable > ----------------------------------------------------------------------------- > > Key: ISPN-9631 > URL: https://issues.jboss.org/browse/ISPN-9631 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present. > AbstractOperations::createResponseException should be modified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9624) Deprecate StreamingMarshaller interface

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9624?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9624: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Deprecate StreamingMarshaller interface > --------------------------------------- > > Key: ISPN-9624 > URL: https://issues.jboss.org/browse/ISPN-9624 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The StreamingMarshaller interface is no longer fit for purpose once we move away from jboss-marshalling as the ObjectOutput abstraction does not fit with non-serialization based marshallers. We should provide a simpler interface that simply allows reading/writing objects to a provided stream. This interface should then be exposed via the InitializationContext to store implementations. > {code:java} > @ThreadSafe > public interface StreamAwareMarshaller extends Marshaller { > /** > * Marshall an object to the {@link OutputStream} > * > * @param o the object to write to the {@link OutputStream} > * @param out the {@link OutputStream} to write the object to > * @throws IOException if the object cannot be marshalled to the {@link OutputStream} due to some I/O error > */ > void writeObject(Object o, OutputStream out) throws IOException; > /** > * Unmarshall an object from the {@link InputStream} > * > * @param in the {@link InputStream} to unmarshall an object from > * @return the unmarshalled object instance > * @throws IOException if unmarshalling cannot complete due to some I/O error > * @throws ClassNotFoundException if the class of the object trying to unmarshall is not found > */ > Object readObject(InputStream in) throws ClassNotFoundException, IOException; > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9632) PersistenceManager should be able to start if store's are unavailable

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9632?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9632: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > PersistenceManager should be able to start if store's are unavailable > --------------------------------------------------------------------- > > Key: ISPN-9632 > URL: https://issues.jboss.org/browse/ISPN-9632 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently it is necessary for a store to become available before `connection-attempts` are exceeded, otherwise cache startup fails. It should be possible for the PM to still start without the store being available, with the store's unavailability logged and operations requiring persistence still throwing StoreUnavailableException messages unless `SKIP_CACHE_STORE`/`SKIP_CACHE_LOAD` flags are present. > Cache startup should still fail if preload=true as this behaviour is not possible if the store is unavailable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9657) Multimap jar is not OSGi compliant

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9657?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9657: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Multimap jar is not OSGi compliant > ---------------------------------- > > Key: ISPN-9657 > URL: https://issues.jboss.org/browse/ISPN-9657 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.0.Final > Reporter: Alain Picard > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.6.Final > > > Due to issues related to using the embedded jar (see [here|https://developer.jboss.org/message/986042#986042], when switching to individual jars, the multimap jar (infinispan-multimap-9.4.0.Final.jar) doesn't provide a valid OSGi manifest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9640) Reduce verbosity of hotrod cache configurations

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9640?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9640: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Reduce verbosity of hotrod cache configurations > ----------------------------------------------- > > Key: ISPN-9640 > URL: https://issues.jboss.org/browse/ISPN-9640 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently when defining a cache configuration via `RemoteCacheManagerAdmin::createCache` and `XMLStringConfiguration` it's necessary for the xml to include the `<infinispan><cache-container>..<infinispan/><cache-container/>` elements. This is unnecessarily verbose, and it should be possible for a user to simply provide the cache config XML, e.g. `<distributed-cache name="example"/>` -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9659) Document the Docker image and how to use it in Kubernetes/OpenShift

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9659?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9659: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Document the Docker image and how to use it in Kubernetes/OpenShift > ------------------------------------------------------------------- > > Key: ISPN-9659 > URL: https://issues.jboss.org/browse/ISPN-9659 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Beta1 > > > Expand/modernize https://blog.infinispan.org/2016/08/running-infinispan-cluster-on-kuberne... and push it to the main docs. > Also document how to run the simple tutorials against this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9699: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > 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: 10.0.0.Beta1, 9.4.6.Final > > > 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.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9700) Expose x-site stats with spring-boot actuator

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9700?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9700: ---------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha3) > Expose x-site stats with spring-boot actuator > --------------------------------------------- > > Key: ISPN-9700 > URL: https://issues.jboss.org/browse/ISPN-9700 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Minor > Fix For: 10.0.0.Beta1 > > > Expose to spring boot actuator x-site metrics -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2019