[JBoss JIRA] (ISPN-10678) Cluster Expiration Reaper should only expire primary owned entries
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10678?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-10678:
------------------------------
Summary: Cluster Expiration Reaper should only expire primary owned entries (was: Cluster Expiration should only expire primary owned entries)
> Cluster Expiration Reaper should only expire primary owned entries
> ------------------------------------------------------------------
>
> Key: ISPN-10678
> URL: https://issues.jboss.org/browse/ISPN-10678
> Project: Infinispan
> Issue Type: Enhancement
> Components: Expiration
> Affects Versions: 9.4.16.Final, 10.0.0.CR2
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.0.0.Final, 9.4.17.Final
>
>
> Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (ISPN-10678) Cluster Expiration Reaper should only expire primary owned entries
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10678?page=com.atlassian.jira.plugin... ]
Will Burns commented on ISPN-10678:
-----------------------------------
To clarify this change only includes making changes for the expiration reaper to only reap primary owned entries. On access is still done by any owner when it finds the entry expired.
> Cluster Expiration Reaper should only expire primary owned entries
> ------------------------------------------------------------------
>
> Key: ISPN-10678
> URL: https://issues.jboss.org/browse/ISPN-10678
> Project: Infinispan
> Issue Type: Enhancement
> Components: Expiration
> Affects Versions: 9.4.16.Final, 10.0.0.CR2
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.0.0.Final, 9.4.17.Final
>
>
> Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (ISPN-10508) Docs: ServerNG Getting Started
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10508?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10508:
-------------------------------
Sprint: DataGrid Sprint #33 (was: DataGrid Sprint #33, DataGrid Sprint #34)
> Docs: ServerNG Getting Started
> ------------------------------
>
> Key: ISPN-10508
> URL: https://issues.jboss.org/browse/ISPN-10508
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Getting started content for ServerNG.
> As a user, I need to:
> - understand requirements and supported platforms
> - download the server distribution or pull the image
> - add a user (auth by default)
> - start a single instance, create a cache, put/get new entry
> - start a second instance on the same network and verify clustering
> - stop servers gracefully
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (ISPN-10508) Docs: ServerNG Getting Started
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10508?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10508:
-------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #35 (was: DataGrid Sprint #33)
> Docs: ServerNG Getting Started
> ------------------------------
>
> Key: ISPN-10508
> URL: https://issues.jboss.org/browse/ISPN-10508
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Getting started content for ServerNG.
> As a user, I need to:
> - understand requirements and supported platforms
> - download the server distribution or pull the image
> - add a user (auth by default)
> - start a single instance, create a cache, put/get new entry
> - start a second instance on the same network and verify clustering
> - stop servers gracefully
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (IPROTO-63) writeObject throws IllegalArgumentException with oneof label
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/IPROTO-63?page=com.atlassian.jira.plugin.... ]
Nistor Adrian updated IPROTO-63:
--------------------------------
Fix Version/s: 4.3.0.Alpha14
(was: 4.3.0.Alpha13)
> writeObject throws IllegalArgumentException with oneof label
> ------------------------------------------------------------
>
> Key: IPROTO-63
> URL: https://issues.jboss.org/browse/IPROTO-63
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Reporter: Ryan Emerson
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.3.0.Alpha14, 4.3.0.Final
>
>
> The below schema results in the following exception:
> Schema:
> {code:java}
> message EntryVersion {
> oneof version {
> NumericVersion numeric = 1;
> ClusteredVersion clustered = 2;
> }
> // optional NumericVersion numeric = 1;
> // optional ClusteredVersion clustered = 2;
> }
> message NumericVersion {
> required int64 version = 1;
> }
> message ClusteredVersion {
> required int64 version = 1;
> required int32 topology = 2;
> }
> {code}
> Exception:
> {code:java}
> java.lang.IllegalArgumentException: Declared field type is not a message or an enum : numeric
> {code}
> It seems this is caused because the type for the field "numeric" is null in the associated FieldDescriptor object that is retrieved in the [writeObject impl|https://github.com/infinispan/protostream/blob/master/core/src/main/...].
> If the oneof label is replaced with the commented optional fields, the marshallers work as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months