February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-5830) Manage state transfer actions

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5830?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-5830: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/52 > Manage state transfer actions > ----------------------------- > > Key: ISPN-5830 > URL: https://issues.jboss.org/browse/ISPN-5830 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Pedro Zapata > Labels: jdg7 > > As an administrator, I want to control Cross site state transfer (when replica sites go offline and come back online) conveniently from the Management Console. > At its core, this is a cache level operation. However, we need a Cache container level operation that will transfer state for all cache that are replicated to the affected data-center(s). > The following actions will be added to the Cache container action menu > - Take site offline > - Bring site online > Another 2 additional options will also be added: > - Force state transfer > - Stop state transfer > Those options will be only enabled if cross site replication is enabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6231) The workflow for submitting new task and seeing the result is not natural

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6231?page=com.atlassian.jira.plugin.... ] Pedro Zapata commented on ISPN-6231: ------------------------------------ I agree, there's some small changes we can do improve this workflow: - Replace 'Cancel' with 'Close'. - Move 'Launch task' to left to 'Close' for consistency with other dialogs. - Make alerts dismissable Keeping the same dialog open makes sense when you want to launch multiple tasks, or keep the parameters in sight. Opening a new dialog would be too cumbersome for implementation and for user as well. > The workflow for submitting new task and seeing the result is not natural > ------------------------------------------------------------------------- > > Key: ISPN-6231 > URL: https://issues.jboss.org/browse/ISPN-6231 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 8.2.0.Beta2 > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > Priority: Minor > > When I open "Launch new task" modal dialog, fill in all the details, and click "Launch task", the task is successfully executed. The problem I see is that, the screen remains open and for leaving this screen, the user has to click "Cancel" even though the task has been submitted and executed. > A more natural approach could be this: > After clicking "Launch task" the original modal dialog disappears and a new dialog appears. This new modal dialog would contain just two elements: > 1) A message about success and the link to show the result > 2) "OK" button (instead of cancel) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6231) The workflow for submitting new task and seeing the result is not natural

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6231?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6231: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > The workflow for submitting new task and seeing the result is not natural > ------------------------------------------------------------------------- > > Key: ISPN-6231 > URL: https://issues.jboss.org/browse/ISPN-6231 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 8.2.0.Beta2 > Reporter: Martin Gencur > Assignee: Pedro Zapata > Priority: Minor > > When I open "Launch new task" modal dialog, fill in all the details, and click "Launch task", the task is successfully executed. The problem I see is that, the screen remains open and for leaving this screen, the user has to click "Cancel" even though the task has been submitted and executed. > A more natural approach could be this: > After clicking "Launch task" the original modal dialog disappears and a new dialog appears. This new modal dialog would contain just two elements: > 1) A message about success and the link to show the result > 2) "OK" button (instead of cancel) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6231) The workflow for submitting new task and seeing the result is not natural

by Martin Gencur (JIRA)

Martin Gencur created ISPN-6231: ----------------------------------- Summary: The workflow for submitting new task and seeing the result is not natural Key: ISPN-6231 URL: https://issues.jboss.org/browse/ISPN-6231 Project: Infinispan Issue Type: Enhancement Components: Console Affects Versions: 8.2.0.Beta2 Reporter: Martin Gencur Assignee: Vladimir Blagojevic Priority: Minor When I open "Launch new task" modal dialog, fill in all the details, and click "Launch task", the task is successfully executed. The problem I see is that, the screen remains open and for leaving this screen, the user has to click "Cancel" even though the task has been submitted and executed. A more natural approach could be this: After clicking "Launch task" the original modal dialog disappears and a new dialog appears. This new modal dialog would contain just two elements: 1) A message about success and the link to show the result 2) "OK" button (instead of cancel) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6230) Task history tab does not show tasks unless Refresh button is pressed as well

by Martin Gencur (JIRA)

Martin Gencur created ISPN-6230: ----------------------------------- Summary: Task history tab does not show tasks unless Refresh button is pressed as well Key: ISPN-6230 URL: https://issues.jboss.org/browse/ISPN-6230 Project: Infinispan Issue Type: Enhancement Components: Console Reporter: Martin Gencur Assignee: Vladimir Blagojevic Priority: Minor This is rather a small usability issue: When I run a task and then click "Task history", the tab doesn't show any tasks. I have to click "Refresh" and only then the tasks are displayed. It might be better to call refresh when "Task history" tab is clicked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6229) Rename select box for choosing the Task to be run

by Martin Gencur (JIRA)

Martin Gencur created ISPN-6229: ----------------------------------- Summary: Rename select box for choosing the Task to be run Key: ISPN-6229 URL: https://issues.jboss.org/browse/ISPN-6229 Project: Infinispan Issue Type: Enhancement Components: Console Affects Versions: 8.2.0.Beta2 Reporter: Martin Gencur Assignee: Pedro Zapata Priority: Minor The select box for choosing the task on "Launch new task" screen is misleading. From a usability standpoint, it would be better to rename it to either "Task" or "Task name" (and also the tooltip). Right now it is named "Type". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5601) Merge ExtendedModuleCommandFactory into ModuleCommandFactory

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-5601?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-5601: ---------------------------------- Assignee: (was: Ryan Emerson) > Merge ExtendedModuleCommandFactory into ModuleCommandFactory > ------------------------------------------------------------ > > Key: ISPN-5601 > URL: https://issues.jboss.org/browse/ISPN-5601 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.0.Alpha2 > Reporter: Radim Vansa > Fix For: 8.2.0.CR1 > > > These are the docs for ExtendedModuleCommandFactory: > {quote} > Temporary workaround to avoid modifying ModuleCommandFactory interface. This interface should be merged with ModuleCommandFactory in 6.0. > {quote} > Seems that was forgotten in 6.0, 8.0 can fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5517) JDBCBinaryStore size method should query count directly instead of iterating

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-5517?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-5517: ---------------------------------- Assignee: (was: Ryan Emerson) > JDBCBinaryStore size method should query count directly instead of iterating > ---------------------------------------------------------------------------- > > Key: ISPN-5517 > URL: https://issues.jboss.org/browse/ISPN-5517 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > Fix For: 8.0.0.CR1, 8.2.0.CR1 > > > JDBCBinaryStore size method iterates upon all of the rows in the database. We should instead use the getCountRowsSql from the table manipulation just like JDBCStringBasedStore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3729) Minimize the number of moved segments for SyncConsistentHashFactory

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3729?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3729: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Minimize the number of moved segments for SyncConsistentHashFactory > ------------------------------------------------------------------- > > Key: ISPN-3729 > URL: https://issues.jboss.org/browse/ISPN-3729 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > SyncConsistentHash uses an algorithm that's similar to consistent hashing, but when there is a collision (two nodes map to the same segment), the second node is moved to the next segment. Since the nodes are ordered by their UUID, that means it's possible for a joiner to change the mapping of existing nodes. > In order to make the load distribution more even, SyncConsistentHash also uses "virtual nodes": each node actually maps to multiple segments. This makes the number of collisions much higher (and implicitly, the number of extra moved segments). > Reading the original [consistent hashing paper|http://thor.cs.ucsb.edu/~ravenben/papers/coreos/kll%2B97.pdf], it looks like the collision handling should be done differently: a joiner should replace an existing node when it's "closer" to the segment boundary, but the existing node should never "lose" segments to another existing node (the property of monotonicity mentioned in the paper). We should investigate whether changing this would allow us to achieve better load balancing by using a much higher number of "virtual nodes" (without moving extra segments). If successful, we could even use SyncConsistentHashFactory as the default hash algorithm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3344) Create a release script for ProtoStream library

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3344: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Create a release script for ProtoStream library > ----------------------------------------------- > > Key: ISPN-3344 > URL: https://issues.jboss.org/browse/ISPN-3344 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 6.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1 > > > Need to add license information and a short README to the project. Also update the 'Cutting Infinispan Releases' document with relevant details for Protostream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 2016