[JBoss JIRA] (ISPN-2445) Safe shutdown - transfer data to other nodes
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-2445?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-2445:
-----------------------------------------
Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Safe shutdown - transfer data to other nodes
> --------------------------------------------
>
> Key: ISPN-2445
> URL: https://issues.jboss.org/browse/ISPN-2445
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Matej Lazar
> Assignee: Dan Berindei
> Priority: Major
>
> Distributed cache should provide an configuration option to block shutdown until data from shutting down node is transferred to other nodes.
> This feature is useful if Infinispan is used as persistent storage.
> Without this option, in a cloud environment, where server node is deleted on scale down event, users are forced to use external storage, if they don't want to loose data.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-9827) The Hot Rod client should apply topology changes after the response has been processed
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9827?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9827:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> The Hot Rod client should apply topology changes after the response has been processed
> --------------------------------------------------------------------------------------
>
> Key: ISPN-9827
> URL: https://issues.jboss.org/browse/ISPN-9827
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> The Hot Rod client applies topology changes to the connection pool while it is processing the header. This could cause the channel on which it is reading to be closed before the response has been completely processed. Topology changes should be applied when the operation completes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-9572) Configuration parser support for multiple cache-containers
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9572?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9572:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Configuration parser support for multiple cache-containers
> ----------------------------------------------------------
>
> Key: ISPN-9572
> URL: https://issues.jboss.org/browse/ISPN-9572
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> The embedded configuration parser should allow parsing multiple <cache-container> elements, each one identified by a unique name.
> All cache-containers should share the same thread pools and transports.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10429) Hot Rod client doesn't retry on socket timeout
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10429?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10429:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Hot Rod client doesn't retry on socket timeout
> ----------------------------------------------
>
> Key: ISPN-10429
> URL: https://issues.jboss.org/browse/ISPN-10429
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> The Hot Rod client registers a timeout handler for operations using the socket timeout. However when this timeout is hit, the retry logic is not invoked causing requests to dead servers to fail immediately without retry.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-9946) ServerNG
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9946?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9946:
-----------------------------------------
Sprint: DataGrid Sprint #29, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #29, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> ServerNG
> --------
>
> Key: ISPN-9946
> URL: https://issues.jboss.org/browse/ISPN-9946
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-9965) HotRodRemoteCache*IT.testDataConversionsWithDefaultRemoteCache failures
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9965?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9965:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> HotRodRemoteCache*IT.testDataConversionsWithDefaultRemoteCache failures
> -----------------------------------------------------------------------
>
> Key: ISPN-9965
> URL: https://issues.jboss.org/browse/ISPN-9965
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> expected:<<[]string>Hello!</strin...> but was:<<[?xml version='1.0' encoding='UTF-8'?><]string>Hello!</strin...>
> Using the StAX driver with xstream has added the xml prolog to the xml responses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-8535) Rest API redesign
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-8535:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Rest API redesign
> -----------------
>
> Key: ISPN-8535
> URL: https://issues.jboss.org/browse/ISPN-8535
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.2.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references.
> Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples:
> * Create a cache: POST /rest/caches
> * Delete a cache: DELETE /rest/caches/myCache
> * Create a template: POST /rest/templates
> * Delete a template: DELETE /rest/templates/myTemplate
> * Create an entry: POST /rest/caches/myCache/1
> * Create a counter: POST /rest/counters
> * Get a counter value: GET /rest/counters/mycounter
> * Increment a counter: GET /rest/counters/mycounter?action=increment
> * Search a cache: GET /rest/caches/myCache?action=search
> * Create a script: POST /rest/scripts/
> * Get a script source: GET /rest/scritps/myScript
> * Execute a script: GET /rest/scripts/myScript?action=execute¶m1=foo
> * Stop individual servers and the full cluster
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-9382) Jenkins release pipeline should handle multiple branches and reversioning
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9382?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9382:
-----------------------------------------
Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Jenkins release pipeline should handle multiple branches and reversioning
> -------------------------------------------------------------------------
>
> Key: ISPN-9382
> URL: https://issues.jboss.org/browse/ISPN-9382
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10685) File stores locations do not respect the Global State persistent location
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10685?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10685:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #34)
> File stores locations do not respect the Global State persistent location
> --------------------------------------------------------------------------
>
> Key: ISPN-10685
> URL: https://issues.jboss.org/browse/ISPN-10685
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.0.CR2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> The file stores (Single, SoftIndex, RocksDB) should create files relative to the GlobalState persistent location unless specified.
> Additionally each of the file stores differs in the filesystem layout:
> * The SoftIndex store does not use the name of the cache in the file path, preventing sharing of directories between multiple caches.
> * The RocksDB store allows configuring data and expired locations to point to the same directory, which will result in data corruption
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months