May 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7831) Adjust node memory graph to match PatternFly widget

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-7831: ----------------------------------------- Summary: Adjust node memory graph to match PatternFly widget Key: ISPN-7831 URL: https://issues.jboss.org/browse/ISPN-7831 Project: Infinispan Issue Type: Sub-task Components: Console Affects Versions: 9.0.0.Final Reporter: Vladimir Blagojevic Fix For: 9.1.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7830) Highlight the selected main navigation tab

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-7830: ----------------------------------------- Summary: Highlight the selected main navigation tab Key: ISPN-7830 URL: https://issues.jboss.org/browse/ISPN-7830 Project: Infinispan Issue Type: Sub-task Components: Console Affects Versions: 9.0.0.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 9.1.0.Final On the main navigational tab at the top of the screen, we have "Caches", "Clusters", "Status Events". We should highlight the selected tab following the Patternfly UI guidelines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7829) Upgrade Administration Console UI/X using Patternfly best practices

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7829?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7829: -------------------------------------- Attachment: InfinispanReview.pdf > Upgrade Administration Console UI/X using Patternfly best practices > ------------------------------------------------------------------- > > Key: ISPN-7829 > URL: https://issues.jboss.org/browse/ISPN-7829 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > Attachments: InfinispanReview.pdf > > > Up to 9.0.0.Final Infinispan release we have mostly relied on common sense when it comes to UI/X of Administration Console. We have now feedback from Patternfly UI/X team and we should upgrade overall UI/X to the highest standard and the best UIX practices. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7829) Upgrade Administration Console UI/X using Patternfly best practices

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-7829: ----------------------------------------- Summary: Upgrade Administration Console UI/X using Patternfly best practices Key: ISPN-7829 URL: https://issues.jboss.org/browse/ISPN-7829 Project: Infinispan Issue Type: Enhancement Components: Console Affects Versions: 9.0.0.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 9.1.0.Final Up to 9.0.0.Final Infinispan release we have mostly relied on common sense when it comes to UI/X of Administration Console. We have now feedback from Patternfly UI/X team and we should upgrade overall UI/X to the highest standard and the best UIX practices. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7806) QueryInterceptor should not load entries from DC but context

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7806?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-7806: ----------------------------------------- Same apply here from https://issues.jboss.org/browse/ISPN-3795?focusedCommentId=13405764&page=... regarding entries in context when the originator is a non-owner > QueryInterceptor should not load entries from DC but context > ------------------------------------------------------------ > > Key: ISPN-7806 > URL: https://issues.jboss.org/browse/ISPN-7806 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.Final > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > > Currently in {{visitPrepareCommand}} the query interceptor is loading data directly from data container. That's wrong - if the entry is passivated/evicted, the previous value is incorrect. > As the data is not loaded (from DC/persistence) at current QI position, we should move QueryInterceptor after EntryWrappingInterceptor, CacheLoaderInterceptor and xDistributionInterceptor (which may load the data from remote node), and load the previous entry from context instead. The same approach should be taken for non-tx command, rather than relying on their return value. > There will still be issues if the command has SKIP_CACHE_LOAD flag: I suggest warning message if it doesn't have SKIP_INDEXING flag as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7802) Use non-growing buffered input stream in TcpTransport

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/ISPN-7802?page=com.atlassian.jira.plugin.... ] Dennis Reed commented on ISPN-7802: ----------------------------------- Proposed fix to avoid creating large pooled native buffers inside NIO: https://github.com/infinispan/infinispan/pull/5133 > Use non-growing buffered input stream in TcpTransport > ----------------------------------------------------- > > Key: ISPN-7802 > URL: https://issues.jboss.org/browse/ISPN-7802 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.0.0.Final > Reporter: Radim Vansa > Assignee: Tristan Tarrant > > The buffering implementation of {{TcpTransport.socketInputStream}} needs to use fixed size input buffer, rather than growing as {{BufferedInputStream}} does. Growing buffer can lead to excessive memory consumption on heap, and more importantly, by direct memory allocated in JDK classes and pooled in thread-local caches. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7828) Add tests for indexing with the IGNORE_RETURN_VALUES flag

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7828?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7828: ------------------------------------ Summary: Add tests for indexing with the IGNORE_RETURN_VALUES flag (was: Add tests for indexing combined wih the IGNORE_RETURN_VALUES flag) > Add tests for indexing with the IGNORE_RETURN_VALUES flag > --------------------------------------------------------- > > Key: ISPN-7828 > URL: https://issues.jboss.org/browse/ISPN-7828 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7828) Add tests for indexing combined wih the IGNORE_RETURN_VALUES flag

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7828: --------------------------------------- Summary: Add tests for indexing combined wih the IGNORE_RETURN_VALUES flag Key: ISPN-7828 URL: https://issues.jboss.org/browse/ISPN-7828 Project: Infinispan Issue Type: Task Components: Test Suite - Query Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3795) QueryInterceptor incorrectly relies on the return value of a RemoveCommand

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3795?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-3795: ----------------------------------------- Sent a PR for the specific case of the Remove and Replace command, where the value needed is available in the command itself, so it's trivial to detect if the command is conditional and avoid looking at the return value, and look in the command instead. The trouble with the context lookup is that if the command originates in a non-owner, there will not be any entry in the context. As [~pruivo] was saying, even if the entry is fetched remotely, it may change between the time it is fetched and the time the primary owner executes the command. > QueryInterceptor incorrectly relies on the return value of a RemoveCommand > -------------------------------------------------------------------------- > > Key: ISPN-3795 > URL: https://issues.jboss.org/browse/ISPN-3795 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > > QueryInterceptor uses the return value from RemoveCommand/ReplaceCommand to remove the value from the index. > But both RemoveCommand and ReplaceCommand have a variant with an expected value parameter, and this variant return a boolean value instead of the removed/replaced value. In that case, the previous value won't be removed from the index. > QueryInterceptor should probably use the previous value from the context entries to update the index instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7823) RemoteCacheManager can block waiting to connect/ping

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7823?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-7823: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5132 > RemoteCacheManager can block waiting to connect/ping > ---------------------------------------------------- > > Key: ISPN-7823 > URL: https://issues.jboss.org/browse/ISPN-7823 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 8.2.6.Final, 9.0.0.Final > Reporter: Galder Zamarreño > Assignee: Katia Aresti > > When running Java Hot Rod client on top sensitive environments to blocking, e.g. Vert.x, you realise that the RemoteCacheManager constructor blocks. > This is due to the fact that RCM constructor waits to establish connections with the initial servers and sends pings on startup. > You can avoid RCM doing this by passing start=false as parameter and then calling start() manually, but start() is a blocking method. > So, we should have an alternative start() method that returns a CompletableFuture, hence avoiding any blocking. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017