February 2020 - infinispan-issues

[JBoss JIRA] (ISPN-11200) Doc Productization: Cache Authorization

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11200?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11200: ------------------------------- Sprint: DataGrid Sprint #40 > Doc Productization: Cache Authorization > --------------------------------------- > > Key: ISPN-11200 > URL: https://issues.redhat.com/browse/ISPN-11200 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > RHDG 8.0 cache authorization -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11228) 10.1.x Docs: Cross-Site Repl

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11228?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11228. ------------------------------ > 10.1.x Docs: Cross-Site Repl > ---------------------------- > > Key: ISPN-11228 > URL: https://issues.redhat.com/browse/ISPN-11228 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.2.Final > > > Update cross-site replication docs for 10.1.x. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10836) Docs Productization: Marshalling

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10836?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10836. ------------------------------ > Docs Productization: Marshalling > -------------------------------- > > Key: ISPN-10836 > URL: https://issues.redhat.com/browse/ISPN-10836 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > Productize content for marshalling and protostream. > Modularize existing content. > Show consistent examples for usage (i.e. should match CLI example). > Identify additional changes and work to develop customer content. > Review Server Guide marshalling section (8. Adding Custom Marshaller Bridges) and make sure this is relevant and up to date for DG 8 > From Ryan: > - protostream and marshalling: > The important things to document are: > Jboss marshalling no longer present by default, infinispan-jboss-marshalling jar must be added to the classpath of the client/server if required. > - Externalizers ignored unless this is present > Protostream is the default marshaller for user types. Need to document the process of generating marshallers using pojos, and configuring the serialization context. > - Best practices on how to evolve schemas to ensure backwards-compatibility > Possible to configure a custom user marshaller in embedded mode, for example if the user wants to use Java Serialization but not jboss marshalling. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10839) Doc Productization: Configuring Caches Declaratively and Programmatically

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10839?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10839. ------------------------------ > Doc Productization: Configuring Caches Declaratively and Programmatically > ------------------------------------------------------------------------- > > Key: ISPN-10839 > URL: https://issues.redhat.com/browse/ISPN-10839 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > These sections in the Configuration Guide need to be updated and improved. > Internal review draft is at: http://file.rdu.redhat.com/dnaro/10x-review/ISPN-10839/titles/configuring... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10725) Server Docs: Security

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10725?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10725. ------------------------------ > Server Docs: Security > --------------------- > > Key: ISPN-10725 > URL: https://issues.redhat.com/browse/ISPN-10725 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > Authentication and encryption docs for server. > Review draft at: http://file.rdu.redhat.com/dnaro/ISPN-10725/server/server.html#security -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11197) Server Docs: JMX Monitoring

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11197?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11197. ------------------------------ > Server Docs: JMX Monitoring > --------------------------- > > Key: ISPN-11197 > URL: https://issues.redhat.com/browse/ISPN-11197 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > Need to update server docs for JMX monitoring. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11219) Docs: Capacity Factor = 0 for site masters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11219?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11219. ------------------------------ > Docs: Capacity Factor = 0 for site masters > ------------------------------------------ > > Key: ISPN-11219 > URL: https://issues.redhat.com/browse/ISPN-11219 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > Add changes from https://github.com/infinispan/infinispan/pull/7766 into 10.1 and master. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11299) Stale values can be indexed during State Transfer

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11299?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11299: ------------------------------------- Description: If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. Sequence of events: * T1: State Transfer starts * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations * T3: An entry is added locally * T4: EWI stores the key * T5: The same key arrives from State Transfer * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) * T7: The entry operation is not committed in the data container since it was tracked before as DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false} was: If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. Sequence of events: * T1: State Transfer starts * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations * T3: An entry is added locally * T4: EWI stores the key * T5: The same key arrives from State Transfer * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) * T7: The entry operation is not committed in the data container since it was tracked before as {{DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false}}} > Stale values can be indexed during State Transfer > ------------------------------------------------- > > Key: ISPN-11299 > URL: https://issues.redhat.com/browse/ISPN-11299 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Gustavo Fernandes > Priority: Major > > If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. > Sequence of events: > * T1: State Transfer starts > * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations > * T3: An entry is added locally > * T4: EWI stores the key > * T5: The same key arrives from State Transfer > * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) > * T7: The entry operation is not committed in the data container since it was tracked before as DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11299) Stale values can be indexed during State Transfer

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11299?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11299: ------------------------------------- Description: If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. Sequence of events: * T1: State Transfer starts * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations * T3: An entry is added locally * T4: EWI stores the key * T5: The same key arrives from State Transfer * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) * T7: The entry operation is not committed in the data container since it was tracked before as {{DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false}}} was: If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. Sequence of events: * T1: State Transfer starts * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations * T3: An entry is added locally * T4: EWI stores the key * T5: The same key arrives from State Transfer * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) * T7: The entry operation is not committed in the data container since it was tracked before as ```DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false} > Stale values can be indexed during State Transfer > ------------------------------------------------- > > Key: ISPN-11299 > URL: https://issues.redhat.com/browse/ISPN-11299 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Gustavo Fernandes > Priority: Major > > If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. > Sequence of events: > * T1: State Transfer starts > * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations > * T3: An entry is added locally > * T4: EWI stores the key > * T5: The same key arrives from State Transfer > * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) > * T7: The entry operation is not committed in the data container since it was tracked before as {{DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false}}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11299) Stale values can be indexed during State Transfer

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11299?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11299: ------------------------------------- Description: If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. Sequence of events: * T1: State Transfer starts * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations * T3: An entry is added locally * T4: EWI stores the key * T5: The same key arrives from State Transfer * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) * T7: The entry operation is not committed in the data container since it was tracked before as ```DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false} was: If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. Sequence of events: * T1: State Transfer starts * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations * T3: An entry is added locally * T4: EWI stores the key * T5: The same key arrives from State Transfer * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) * T7: The entry operation is not committed in the data container since it was tracked before as ```DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false}``` > Stale values can be indexed during State Transfer > ------------------------------------------------- > > Key: ISPN-11299 > URL: https://issues.redhat.com/browse/ISPN-11299 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Gustavo Fernandes > Priority: Major > > If an operation is discarded during state transfer because it was already modified locally, the QueryInterceptor still propagates it to the index, leaving the index out of sync. > Sequence of events: > * T1: State Transfer starts > * T2: The EWI (EntryWrappingInterceptor) starts tracking all non-state-transfer operations > * T3: An entry is added locally > * T4: EWI stores the key > * T5: The same key arrives from State Transfer > * T6: QueryInterceptor indexes it (The QI is installed after EWI but indexing happens before storing the entry in the data container) > * T7: The entry operation is not committed in the data container since it was tracked before as ```DiscardPolicy{discardStateTransfer=true, discardXSiteStateTransfer=false} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2020