September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10582) Dependency on ANTLR 2.7 can be safely removed as it is no longer used

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10582?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10582: --------------------------------- Status: Open (was: New) > Dependency on ANTLR 2.7 can be safely removed as it is no longer used > --------------------------------------------------------------------- > > Key: ISPN-10582 > URL: https://issues.jboss.org/browse/ISPN-10582 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Beta1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10317) Non-blocking PendingLockManager

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10317?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10317: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR2 Resolution: Done > Non-blocking PendingLockManager > ------------------------------- > > Key: ISPN-10317 > URL: https://issues.jboss.org/browse/ISPN-10317 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Transactions > Reporter: Pedro Ruivo > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.CR2 > > > {{PendingLockManager}} can block user threads for a local write/lock command. > Remote commands aren't affected by this. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10561) Upgrade to Jackson Databind 2.9.9.3

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10561?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10561: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to Jackson Databind 2.9.9.3 > ----------------------------------- > > Key: ISPN-10561 > URL: https://issues.jboss.org/browse/ISPN-10561 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Affects Versions: 9.4.16.Final, 10.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR2, 9.4.17.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10511) ServerNG Docs: Clustering

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10511?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10511: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7288 > ServerNG Docs: Clustering > ------------------------- > > Key: ISPN-10511 > URL: https://issues.jboss.org/browse/ISPN-10511 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > As an admin, I need to choose cluster transport protocol (UDP or TCP) > As an admin, I need to choose a cluster discovery protocol (PING) > As an admin, I want to encrypt network traffic between nodes -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10571) CORS usability issues

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10571?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10571: ------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7286 > CORS usability issues > --------------------- > > Key: ISPN-10571 > URL: https://issues.jboss.org/browse/ISPN-10571 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > > * OPTIONS is currently only handled by CORS for the pre-flight. Regular OPTIONS requests throw an error. > * By default, localhost is not allowed > * Specifying origin with '*' (all origins allowed) is not working -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10571) CORS usability issues

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10571?page=com.atlassian.jira.plugin... ] Work on ISPN-10571 started by Gustavo Fernandes. ------------------------------------------------ > CORS usability issues > --------------------- > > Key: ISPN-10571 > URL: https://issues.jboss.org/browse/ISPN-10571 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > > * OPTIONS is currently only handled by CORS for the pre-flight. Regular OPTIONS requests throw an error. > * By default, localhost is not allowed > * Specifying origin with '*' (all origins allowed) is not working -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10286) Segmented Store can get stuck with bulk write

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10286?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10286. --------------------------------- Resolution: Done > Segmented Store can get stuck with bulk write > --------------------------------------------- > > Key: ISPN-10286 > URL: https://issues.jboss.org/browse/ISPN-10286 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.CR2, 9.4.17.Final, 10.0.0.Beta4 > > > The code was refactored in ComposedSegmentedLoadWriteStore to be more non blocking friendly. Unfortunately due to how groupBy and flatMap interact it is possible for the bulkUpdate to never complete. > FlatMap by default sets a parallelism level of 128. this means it will request 128 groups from groupBy, but unfortunately if there are more than 128 groups, it will never complete as groupBy must publish all groups before a single one can complete. Thus any time we use flatMap after a groupBy we must either set the parallelism level to Integer.MAX_VALUE or to an explicit value if we know how many groups at max there will be. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10286) Segmented Store can get stuck with bulk write

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10286?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10286: ------------------------------ Fix Version/s: 9.4.17.Final > Segmented Store can get stuck with bulk write > --------------------------------------------- > > Key: ISPN-10286 > URL: https://issues.jboss.org/browse/ISPN-10286 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.CR2, 9.4.17.Final > > > The code was refactored in ComposedSegmentedLoadWriteStore to be more non blocking friendly. Unfortunately due to how groupBy and flatMap interact it is possible for the bulkUpdate to never complete. > FlatMap by default sets a parallelism level of 128. this means it will request 128 groups from groupBy, but unfortunately if there are more than 128 groups, it will never complete as groupBy must publish all groups before a single one can complete. Thus any time we use flatMap after a groupBy we must either set the parallelism level to Integer.MAX_VALUE or to an explicit value if we know how many groups at max there will be. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10286) Segmented Store can get stuck with bulk write

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10286?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10286: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/7024, https://github.com/infinispan/infinispan/pull/7285 (was: https://github.com/infinispan/infinispan/pull/7024, https://issues.jboss.org/browse/ISPN-10286) > Segmented Store can get stuck with bulk write > --------------------------------------------- > > Key: ISPN-10286 > URL: https://issues.jboss.org/browse/ISPN-10286 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.CR2, 9.4.17.Final > > > The code was refactored in ComposedSegmentedLoadWriteStore to be more non blocking friendly. Unfortunately due to how groupBy and flatMap interact it is possible for the bulkUpdate to never complete. > FlatMap by default sets a parallelism level of 128. this means it will request 128 groups from groupBy, but unfortunately if there are more than 128 groups, it will never complete as groupBy must publish all groups before a single one can complete. Thus any time we use flatMap after a groupBy we must either set the parallelism level to Integer.MAX_VALUE or to an explicit value if we know how many groups at max there will be. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10581) Segmented Store can get stuck with bulk write

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10581: ----------------------------------- Summary: Segmented Store can get stuck with bulk write Key: ISPN-10581 URL: https://issues.jboss.org/browse/ISPN-10581 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 10.0.0.Alpha3 Reporter: Will Burns Assignee: Will Burns Fix For: 10.0.0.Beta4, 10.0.0.CR2 The code was refactored in ComposedSegmentedLoadWriteStore to be more non blocking friendly. Unfortunately due to how groupBy and flatMap interact it is possible for the bulkUpdate to never complete. FlatMap by default sets a parallelism level of 128. this means it will request 128 groups from groupBy, but unfortunately if there are more than 128 groups, it will never complete as groupBy must publish all groups before a single one can complete. Thus any time we use flatMap after a groupBy we must either set the parallelism level to Integer.MAX_VALUE or to an explicit value if we know how many groups at max there will be. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019