November 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6908) Display available JDBC datasources as a dropdown menu

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6908?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6908: -------------------------------------- Priority: Minor (was: Major) > Display available JDBC datasources as a dropdown menu > ----------------------------------------------------- > > Key: ISPN-6908 > URL: https://issues.jboss.org/browse/ISPN-6908 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Minor > > Currently the name of JDBC datasources are entered manually by the user, this should be replaced with a select option that consists of the configured datasources. > “/profile=clustered/subsystem=datasources/data-source=..." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6719) Add class attributes to element on JDBC store configuration for testing

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6719?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6719: -------------------------------------- Priority: Minor (was: Major) > Add class attributes to element on JDBC store configuration for testing > ----------------------------------------------------------------------- > > Key: ISPN-6719 > URL: https://issues.jboss.org/browse/ISPN-6719 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Minor > > In the cache configuration page, on the JDBC store tab, there are several inputs/selects. To be able to test is automatically, it's very helpful to have the inputs/selects marked with classes just like with File store or LevelDB tabs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7066) The default cache configuration should not be applied to other caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-7066: ------------------------------------- Forum Reference: http://lists.jboss.org/pipermail/infinispan-dev/2016-November/017011.html, https://developer.jboss.org/message/965340 Assignee: Tristan Tarrant > The default cache configuration should not be applied to other caches > --------------------------------------------------------------------- > > Key: ISPN-7066 > URL: https://issues.jboss.org/browse/ISPN-7066 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.3.Final, 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Tristan Tarrant > > Hi guys, > We noticed a weird behaviour of the Infinispan config where caches that are configured with no persistence assume the persistence configuration of the default cache for the cache container. This can potentially lead to some serious errors as data put into the other caches is getting written into the store of the default cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7066) The default cache configuration should not be applied to other caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7066: ---------------------------------- Summary: The default cache configuration should not be applied to other caches (was: Caches assume persistence configuration from default cache) > The default cache configuration should not be applied to other caches > --------------------------------------------------------------------- > > Key: ISPN-7066 > URL: https://issues.jboss.org/browse/ISPN-7066 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.3.Final, 8.2.4.Final > Reporter: Vladimir Dzhuvinov > > Hi guys, > We noticed a weird behaviour of the Infinispan config where caches that are configured with no persistence assume the persistence configuration of the default cache for the cache container. This can potentially lead to some serious errors as data put into the other caches is getting written into the store of the default cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6794) Administration console - editing javascript task name doesn't work correctly

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6794?page=com.atlassian.jira.plugin.... ] Roman Macor closed ISPN-6794. ----------------------------- Resolution: Done > Administration console - editing javascript task name doesn't work correctly > ---------------------------------------------------------------------------- > > Key: ISPN-6794 > URL: https://issues.jboss.org/browse/ISPN-6794 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > > Editing javascript task name, doesn't change the name of the script. If we try to edit name the script can no longer be executed. > Console error message when trying to run edited script: > Error Some unexpected problem happened when launching the task: DGISPN0118: Failed to invoke operation: java.lang.NullPointerException > Steps to reproduce: > upload javascript > - click on cache container -> Configuration -> Tasks -> Create new script > - fill in the mandatory parameter (e.g. Task name: newTask, Language: javascript, Execution mode: local, script body: cache.put('key','value')) > - click create script task button > edit script > - click on cache container -> Configuration -> Tasks -> Edit > - change the name of the script > - click update script > Result: > name remains the same and script can no longer be executed > Note that other properties such as mode or script body can be edited in this way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7197) Administration console - completed tasks are not shown in task history right away

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7197?page=com.atlassian.jira.plugin.... ] Roman Macor reassigned ISPN-7197: --------------------------------- Assignee: Vladimir Blagojevic > Administration console - completed tasks are not shown in task history right away > --------------------------------------------------------------------------------- > > Key: ISPN-7197 > URL: https://issues.jboss.org/browse/ISPN-7197 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: local-task.jar > > > Steps to reproduce: > start domain.sh > start cli.sh -> deploy /path/to/attached/jar/local-task.jar --all-server-groups > in administration console -> click on cache container -> task execution -> Launch new task -> fill in the form: task = LocalTask, Cache= default, Originator node: master:server-one, Parameter1: param; value -> Click Launch task (Success! The task has been successfully launched is displayed) -> click close -> click on Task history > result: the task is not there > Please note that the task will be displayed in task history after a few moments (about 20 seconds) or after log out -> log in action. > Javascript tasks are displayed in history right away. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7197) Administration console - completed tasks are not shown in task history right away

by Roman Macor (JIRA)

Roman Macor created ISPN-7197: --------------------------------- Summary: Administration console - completed tasks are not shown in task history right away Key: ISPN-7197 URL: https://issues.jboss.org/browse/ISPN-7197 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.Alpha4 Reporter: Roman Macor Attachments: local-task.jar Steps to reproduce: start domain.sh start cli.sh -> deploy /path/to/attached/jar/local-task.jar --all-server-groups in administration console -> click on cache container -> task execution -> Launch new task -> fill in the form: task = LocalTask, Cache= default, Originator node: master:server-one, Parameter1: param; value -> Click Launch task (Success! The task has been successfully launched is displayed) -> click close -> click on Task history result: the task is not there Please note that the task will be displayed in task history after a few moments (about 20 seconds) or after log out -> log in action. Javascript tasks are displayed in history right away. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7194) Administration console - task history tab is not working

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7194?page=com.atlassian.jira.plugin.... ] Roman Macor closed ISPN-7194. ----------------------------- Resolution: Done > Administration console - task history tab is not working > -------------------------------------------------------- > > Key: ISPN-7194 > URL: https://issues.jboss.org/browse/ISPN-7194 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > > Click on cache container -> task execution -> TASK_HISTORY > Result: nothing happens, the tab is not active > Expected results: task history should be showed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7190) Administration console - when adding new cache, base configuration shouldn't show existing caches

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7190?page=com.atlassian.jira.plugin.... ] Roman Macor closed ISPN-7190. ----------------------------- Resolution: Done [~vblagojevic] I was testing it with latest snapshot of Infinispan which is using 9.0.0.Alpha4 version of management console, (I'm always clearing cache before management console tests). I will be using 9.0.0 of management console from now on, which is the current latest version in https://github.com/infinispan/infinispan-management-console. It is indeed resolved there, so I'm closing this issue. > Administration console - when adding new cache, base configuration shouldn't show existing caches > ------------------------------------------------------------------------------------------------- > > Key: ISPN-7190 > URL: https://issues.jboss.org/browse/ISPN-7190 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screen Shot 2016-11-13 at 8.05.40 AM.png, Screenshot from 2016-11-11.png > > > Click on cache container -> Add cache -> expand "base configuration" drop down > Result: The drop down offers cache configurations and existing caches > Expected result: The drop down should only offer cache configurations. ("default" and "memcachedCache" shouldn't be there ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5021) Nodes that finish the rebalance later can see outdated values

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5021?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-5021: ------------------------------ Labels: consistency testsuite_stability (was: testsuite_stability) > Nodes that finish the rebalance later can see outdated values > ------------------------------------------------------------- > > Key: ISPN-5021 > URL: https://issues.jboss.org/browse/ISPN-5021 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: consistency, testsuite_stability > > Copied from [ISPN-4444|https://issues.jboss.org/browse/ISPN-4444?focusedCommentId=1302...] > If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help. > I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance: > 1. T0: read_ch=old, write_ch=old > 2. start a rebalance > 3. T1: read_ch=old, write_ch=old+new > 4. new owners have all the data > 5. T2: read_ch=new, write_ch=old+new > 6. remove old cache entries and ignore further writes > 7. T3: read_ch=new, write_ch=new -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2016