[JBoss JIRA] (ISPN-5391) Use @MetaInfServices in infinispan-directory-provider module
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-5391:
-----------------------------------
Summary: Use @MetaInfServices in infinispan-directory-provider module
Key: ISPN-5391
URL: https://issues.jboss.org/browse/ISPN-5391
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying
Affects Versions: 7.2.0.CR1
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 7.2.0.Final
Files src/main/resources/META-INF/services/org.infinispan.hibernate.search.spi.CacheManagerService and src/main/resources/META-INF/services/org.infinispan.hibernate.search.impl.AsyncDeleteExecutorService should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ISPN-2145) No descriptions for invalid jgroups configuration files
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-2145?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-2145:
------------------------------------
Fix Version/s: 7.2.0.Final
(was: 7.2.0.CR1)
> No descriptions for invalid jgroups configuration files
> -------------------------------------------------------
>
> Key: ISPN-2145
> URL: https://issues.jboss.org/browse/ISPN-2145
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.1.2.FINAL, 7.0.0.CR1
> Environment: Any
> Reporter: Dmitry Udalov
> Assignee: Tristan Tarrant
> Fix For: 7.2.0.Final
>
>
> Can't find error's description for invalid jgroups configuration files. Shuffling elements of the file (why not!) makes it invalid, but log-files only report the existence of the error and you have to debug it to figure out the problem. It would be easier if the class JGroupsTransport also reports the exception, not just a generic message in blocks like
> } catch (Exception e) {
> log.errorCreatingChannelFromConfigFile(cfg);
> throw new CacheException(e);
> }
> As a result log-file contains a lot of generic messages without explaining the problem, which in my case was quite helpful:
> java.lang.Exception: events [GET_DIGEST SET_DIGEST FIND_INITIAL_MBRS FIND_ALL_VIEWS ] are required by GMS, but not provided by any of the protocols below it
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ISPN-3891) Tune for batching without transactions
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-3891:
------------------------------------
Fix Version/s: 7.2.0.Final
(was: 7.2.0.CR1)
> Tune for batching without transactions
> --------------------------------------
>
> Key: ISPN-3891
> URL: https://issues.jboss.org/browse/ISPN-3891
> Project: Infinispan
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Sanne Grinovero
> Fix For: 7.2.0.Final
>
>
> The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured.
> Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-3835:
------------------------------------
Fix Version/s: 7.2.0.Final
(was: 7.2.0.CR1)
> Index Update command is processed before the registry listener is triggered
> ---------------------------------------------------------------------------
>
> Key: ISPN-3835
> URL: https://issues.jboss.org/browse/ISPN-3835
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 6.0.0.Final
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Priority: Critical
> Labels: 64QueryBlockers
> Fix For: 7.2.0.Final
>
>
> When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet.
> Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event.
> This leads to index update commands to be lost (with a stacktrace logged)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months