September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10668) Expiration reaper should log the number of entries removed

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10668?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10668: ------------------------------ Fix Version/s: 10.0.0.CR3 9.4.17.Final > Expiration reaper should log the number of entries removed > ---------------------------------------------------------- > > Key: ISPN-10668 > URL: https://issues.jboss.org/browse/ISPN-10668 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.CR3, 9.4.17.Final > > > To track the expiration process the reaper should log messages which show the number of expired and removed entry per cache additional to the start/stop and duration which can be seen at this point -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10696) Cluster Expiration reaper limits parallel expirations too much

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10696?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10696: ------------------------------ Fix Version/s: 10.0.0.CR3 (was: 10.0.0.Final) > Cluster Expiration reaper limits parallel expirations too much > -------------------------------------------------------------- > > Key: ISPN-10696 > URL: https://issues.jboss.org/browse/ISPN-10696 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.CR3, 9.4.17.Final > > > The expiration reaper today currently limits the expiration to only allow 5 pending expiration commands at once. It also doesn't submit more expirations until those 5 complete. We should do the following changes: > # Increase the limit, possibly to 100? > # Allow for extra expiration commands to be invoked as the others are complete, instead of waiting for all of them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10668) Expiration reaper should log the number of entries removed

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10668?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10668: ------------------------------ Status: Open (was: New) > Expiration reaper should log the number of entries removed > ---------------------------------------------------------- > > Key: ISPN-10668 > URL: https://issues.jboss.org/browse/ISPN-10668 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > > To track the expiration process the reaper should log messages which show the number of expired and removed entry per cache additional to the start/stop and duration which can be seen at this point -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10668) Expiration reaper should log the number of entries removed

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10668?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10668: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7374 > Expiration reaper should log the number of entries removed > ---------------------------------------------------------- > > Key: ISPN-10668 > URL: https://issues.jboss.org/browse/ISPN-10668 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > > To track the expiration process the reaper should log messages which show the number of expired and removed entry per cache additional to the start/stop and duration which can be seen at this point -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10696) Cluster Expiration reaper limits parallel expirations too much

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10696?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10696: ------------------------------ Status: Open (was: New) > Cluster Expiration reaper limits parallel expirations too much > -------------------------------------------------------------- > > Key: ISPN-10696 > URL: https://issues.jboss.org/browse/ISPN-10696 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Final, 9.4.17.Final > > > The expiration reaper today currently limits the expiration to only allow 5 pending expiration commands at once. It also doesn't submit more expirations until those 5 complete. We should do the following changes: > # Increase the limit, possibly to 100? > # Allow for extra expiration commands to be invoked as the others are complete, instead of waiting for all of them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10696) Cluster Expiration reaper limits parallel expirations too much

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10696?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10696: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7374 > Cluster Expiration reaper limits parallel expirations too much > -------------------------------------------------------------- > > Key: ISPN-10696 > URL: https://issues.jboss.org/browse/ISPN-10696 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Final, 9.4.17.Final > > > The expiration reaper today currently limits the expiration to only allow 5 pending expiration commands at once. It also doesn't submit more expirations until those 5 complete. We should do the following changes: > # Increase the limit, possibly to 100? > # Allow for extra expiration commands to be invoked as the others are complete, instead of waiting for all of them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10668) Expiration reaper should log the number of entries removed

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10668?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10668: ------------------------------ Summary: Expiration reaper should log the number of entries removed (was: Expiration reaper should log (DEBUG?) the number of entries expired and removed) > Expiration reaper should log the number of entries removed > ---------------------------------------------------------- > > Key: ISPN-10668 > URL: https://issues.jboss.org/browse/ISPN-10668 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > > To track the expiration process the reaper should log messages which show the number of expired and removed entry per cache additional to the start/stop and duration which can be seen at this point -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10696) Cluster Expiration reaper limits parallel expirations too much

by Will Burns (Jira)

Will Burns created ISPN-10696: --------------------------------- Summary: Cluster Expiration reaper limits parallel expirations too much Key: ISPN-10696 URL: https://issues.jboss.org/browse/ISPN-10696 Project: Infinispan Issue Type: Bug Affects Versions: 10.0.0.CR2 Reporter: Will Burns Fix For: 10.0.0.Final, 9.4.17.Final The expiration reaper today currently limits the expiration to only allow 5 pending expiration commands at once. It also doesn't submit more expirations until those 5 complete. We should do the following changes: # Increase the limit, possibly to 100? # Allow for extra expiration commands to be invoked as the others are complete, instead of waiting for all of them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10669) MurmurHash3 should have a special case for WrappedBytes

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10669?page=com.atlassian.jira.plugin... ] Will Burns commented on ISPN-10669: ----------------------------------- Just to note, only WrappedBytes is used as key. The other implementation `ProtobufValueWrapper` is only used as a value and thus isn't hashed using murmur hash. > MurmurHash3 should have a special case for WrappedBytes > ------------------------------------------------------- > > Key: ISPN-10669 > URL: https://issues.jboss.org/browse/ISPN-10669 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.CR3 > > > {{MurmurHash3.hashCode(Object)}} has a special case for {{WrappedBytesArray}}, but not for other implementations of {{WrappedBytes}} like {{ProtobufValueWrapper}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10695) Standardize the transport stack for the test suite

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10695?page=com.atlassian.jira.plugin... ] Diego Lovison reassigned ISPN-10695: ------------------------------------ Assignee: Diego Lovison > Standardize the transport stack for the test suite > -------------------------------------------------- > > Key: ISPN-10695 > URL: https://issues.jboss.org/browse/ISPN-10695 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > Fix For: 10.0.0.CR2 > > > By default the current stack is UDP but serverNG is using a different property name. > In this case, the QA will believe that all test suite is running under UDP when it is not. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 September 2019