[JBoss JIRA] (ISPN-11261) GlobalConfigurationManager should use blocking threads when starting caches
by Will Burns (Jira)
Will Burns created ISPN-11261:
---------------------------------
Summary: GlobalConfigurationManager should use blocking threads when starting caches
Key: ISPN-11261
URL: https://issues.redhat.com/browse/ISPN-11261
Project: Infinispan
Issue Type: Sub-task
Components: Core
Reporter: Will Burns
Assignee: Will Burns
Fix For: 11.0.0.Alpha1
The GlobalConfigurationMangerImpl starts caches via a thread pool. Currently this thread pool is the configured non blocking thread pool. We should move this instead to the blocking thread pool until ISPN-9744 can be fixed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-11260) Improve navigability for docs on infinispan.org
by Donald Naro (Jira)
Donald Naro created ISPN-11260:
----------------------------------
Summary: Improve navigability for docs on infinispan.org
Key: ISPN-11260
URL: https://issues.redhat.com/browse/ISPN-11260
Project: Infinispan
Issue Type: Enhancement
Components: Documentation
Reporter: Donald Naro
Assignee: Donald Naro
Update version drop-down menu for docs. Ex: from the 9.4.x User Guide, select 10.1.x from the version drop-down, get a 404. It should take you to the index page instead.
Also from older documentation versions page, add link to index for 10.x+ alongside javadocs, schema.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-11259) Remove Hash implementation from CacheJoinInfo
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-11259:
-----------------------------------
Summary: Remove Hash implementation from CacheJoinInfo
Key: ISPN-11259
URL: https://issues.redhat.com/browse/ISPN-11259
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 11.0.0.Alpha1
{{CacheJoinInfo}} still sends the configured {{Hash}} implementation over the wire, however this is no longer configurable and MurmurHash3 is used throughout our code. Therefore, we can remove this from the payload as it's a constant.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-11258) Proto Compatibility check should not fail on unknown OS
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11258?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11258:
--------------------------------
Fix Version/s: 10.1.2.Final
11.0.0.Alpha1
> Proto Compatibility check should not fail on unknown OS
> -------------------------------------------------------
>
> Key: ISPN-11258
> URL: https://issues.redhat.com/browse/ISPN-11258
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 10.1.1.Final, 11.0.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.1.2.Final, 11.0.0.Alpha1
>
>
> Currently the proto schema compatibility check will fail if Infinispan is built on an OS that we do not have a protolock binary for. Instead, we should skip the check and warn the user. This will not affect our protobuf schema compatibility, as the check will still be performed on our CI builds.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-11258) Proto Compatibility check should not fail on unknown OS
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11258?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11258:
--------------------------------
Status: Open (was: New)
> Proto Compatibility check should not fail on unknown OS
> -------------------------------------------------------
>
> Key: ISPN-11258
> URL: https://issues.redhat.com/browse/ISPN-11258
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 10.1.1.Final, 11.0.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.1.2.Final, 11.0.0.Alpha1
>
>
> Currently the proto schema compatibility check will fail if Infinispan is built on an OS that we do not have a protolock binary for. Instead, we should skip the check and warn the user. This will not affect our protobuf schema compatibility, as the check will still be performed on our CI builds.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month