January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3907) Define a Protobuf annotation for defining numeric IDs for types

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-3907: ------------------------------------- Instead of using a custom protobuf option we'll use a doc comment annotation, similar to what was done for ISPN-3718. > Define a Protobuf annotation for defining numeric IDs for types > --------------------------------------------------------------- > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.1.0.Final > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3907) Define a Protobuf annotation for defining numeric IDs for types

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3907: -------------------------------- Summary: Define a Protobuf annotation for defining numeric IDs for types (was: Define a Protobuf custom option for defining numeric IDs for types) > Define a Protobuf annotation for defining numeric IDs for types > --------------------------------------------------------------- > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.1.0.Final > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4092) ViewChangedEvent.getOldMembers() and getNewMembers() should never be null

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4092?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4092: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.1.0.Final Resolution: Done > ViewChangedEvent.getOldMembers() and getNewMembers() should never be null > ------------------------------------------------------------------------- > > Key: ISPN-4092 > URL: https://issues.jboss.org/browse/ISPN-4092 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Eric Bonnot > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.1.0.Final > > > Simply for more comfort at usage I'd like to have ViewChangedEvent changed, that the list-getter never return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4092) ViewChangedEvent.getOldMembers() and getNewMembers() should never be null

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4092?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4092: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1184, https://github.com/infinispan/infinispan/pull/3241 (was: https://github.com/infinispan/infinispan/pull/1184) > ViewChangedEvent.getOldMembers() and getNewMembers() should never be null > ------------------------------------------------------------------------- > > Key: ISPN-4092 > URL: https://issues.jboss.org/browse/ISPN-4092 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Eric Bonnot > Assignee: Thomas Fromm > Priority: Minor > > Simply for more comfort at usage I'd like to have ViewChangedEvent changed, that the list-getter never return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4092) ViewChangedEvent.getOldMembers() and getNewMembers() should never be null

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4092?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4092: ------------------------------------- Assignee: Tristan Tarrant (was: Thomas Fromm) > ViewChangedEvent.getOldMembers() and getNewMembers() should never be null > ------------------------------------------------------------------------- > > Key: ISPN-4092 > URL: https://issues.jboss.org/browse/ISPN-4092 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Eric Bonnot > Assignee: Tristan Tarrant > Priority: Minor > > Simply for more comfort at usage I'd like to have ViewChangedEvent changed, that the list-getter never return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5190) DefaultExecutorService throws ISE if constructed with ManagedExecutorService

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5190?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5190: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.1.0.Final Resolution: Done > DefaultExecutorService throws ISE if constructed with ManagedExecutorService > ---------------------------------------------------------------------------- > > Key: ISPN-5190 > URL: https://issues.jboss.org/browse/ISPN-5190 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.3.Final, 7.1.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.1.0.Final > > > ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" of the JEE concurrency specification. > However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5159) Make concurrent startup smooth

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5159?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5159: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1186874 > Make concurrent startup smooth > ------------------------------ > > Key: ISPN-5159 > URL: https://issues.jboss.org/browse/ISPN-5159 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > > When starting many instances in parallel, it often happens that the node does not detect its neighborhood very well and this results in many subclusters, merging views etc. > Merging two available partitions has undefined results (AFAIK). While we can expect that there are no requests to the cluster from the application ^1^, Infinispan itself uses some caches to store internal information (HotRod routing, Protobuf etc...). It would be better if the available-available merge would provide hooks for rebuilding this info. > ^1^) Being able to start the cluster with reads/writes disabled and enable them only when the cache has expected number of members would be convenient, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4992) Implement node statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4992?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4992: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1184647, https://bugzilla.redhat.com/show_bug.cgi?id=1186874 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1184647) > Implement node statistics > ------------------------- > > Key: ISPN-4992 > URL: https://issues.jboss.org/browse/ISPN-4992 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > We need to implement node statistics aggregating statistics of all caches on that particular node. Implementing class should be an MBean as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5147) Creation/configuration of caches using JON should not require a server restart

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5147?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5147: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1186874 > Creation/configuration of caches using JON should not require a server restart > ------------------------------------------------------------------------------ > > Key: ISPN-5147 > URL: https://issues.jboss.org/browse/ISPN-5147 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 7.2.0.Final > > > When creating a cache using the management interface, we want to be able to set all specific configuration and start the cache without requiring a server restart. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4991) Implement clustered cache statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4991?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4991: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1180047, https://bugzilla.redhat.com/show_bug.cgi?id=1184647, https://bugzilla.redhat.com/show_bug.cgi?id=1186874 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1180047) > Implement clustered cache statistics > ------------------------------------ > > Key: ISPN-4991 > URL: https://issues.jboss.org/browse/ISPN-4991 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > As of 7.0.0 release we implement cache statistics on a per node cache level. For Infinispan admin console we need to implement aggregate statistics for each cache across all nodes in the cluster. The implementing class should be a registered MBean and should implement similar cache statistics currently implemented by org.infinispan.interceptors.CacheMgmtInterceptor -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015