June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-330) Separate scheduled/unscheduled async cache store configuration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-330?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño resolved ISPN-330. ----------------------------------- Resolution: Won't Fix > Separate scheduled/unscheduled async cache store configuration > -------------------------------------------------------------- > > Key: ISPN-330 > URL: https://issues.jboss.org/browse/ISPN-330 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration, Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Implement configuration that allows differentiation between scheduled/unscheduled strategies: > <async enabled="true"> > <scheduled frequency="1000" /> > </async> > > <async enabled="true"> > <unscheduled poolsize="50" /> > </async> > > This format allows for easier extension of properties in scheduled/unscheduled modes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-159) Extended coalesced logic to other parts

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-159?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño resolved ISPN-159. ----------------------------------- Resolution: Won't Fix > Extended coalesced logic to other parts > --------------------------------------- > > Key: ISPN-159 > URL: https://issues.jboss.org/browse/ISPN-159 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Transactions > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Reuse same coalesced async cache store logic to: > - Reduce size of replicable commands where N modifications are sent so that only latest state is sent. > - Manage the async replication queue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1195) Rehashing and state transfer to use digesting

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1195?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-1195: -------------------------------------- Assignee: (was: Galder Zamarreño) > Rehashing and state transfer to use digesting > --------------------------------------------- > > Key: ISPN-1195 > URL: https://issues.jboss.org/browse/ISPN-1195 > Project: Infinispan > Issue Type: Feature Request > Components: Core, State Transfer > Reporter: Manik Surtani > Priority: Critical > Labels: rehash, state_transfer, versioning > > Rather than pushing entire state to new joiners, a mechanism of digests should be used to minimise network transfers. For example, Merkle trees can be used to determine which entries are out of date and need pushing, in the case of nodes that persist to a local cache store, and is restarted but still has access to some state on disk. > This would require versioned entries though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-387) Enable accessing Hot Rod servers via WebSockets

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-387?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño resolved ISPN-387. ----------------------------------- Resolution: Out of Date > Enable accessing Hot Rod servers via WebSockets > ----------------------------------------------- > > Key: ISPN-387 > URL: https://issues.jboss.org/browse/ISPN-387 > Project: Infinispan > Issue Type: Feature Request > Components: Memcached, Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Add a flag to Hot Rod server configuration so that appropiate Base64 encoder/decoder can be used when interfacing with WebSocket clients. This might also require for Netty WebSocket channel handlers to be set up so that WebSocket upgrade handshaking can be dealt with independent of Hot Rod. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1402) Limit rate of incoming requests on Hot Rod server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1402?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-1402: -------------------------------------- Assignee: (was: Galder Zamarreño) > Limit rate of incoming requests on Hot Rod server > ------------------------------------------------- > > Key: ISPN-1402 > URL: https://issues.jboss.org/browse/ISPN-1402 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Sanne Grinovero > Priority: Minor > > Like application servers have a way to configure a limit of parallel incoming requests, if a too high number of requests is incoming some of these should be put in a queue, to protect the server performance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1368) RpcManagerFactory should not create an RpcManager for local caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1368?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-1368. ------------------------------------ Resolution: Out of Date > RpcManagerFactory should not create an RpcManager for local caches > ------------------------------------------------------------------ > > Key: ISPN-1368 > URL: https://issues.jboss.org/browse/ISPN-1368 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.0.0.FINAL > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > > As indicated in ISPN-1348, RpcManagerFactory should not create an RpcManager for those caches whose mode is LOCAL,, even if the transport is not null. > Btw, I don't want this fixed till ISPN-1366 is in place, otherwise ISPN-1348 does become a problem and finding a solution for it without ISPN-1366 complicates things greatly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1437) Servers need typed configuration and injection of components

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1437?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-1437. ------------------------------------ Resolution: Out of Date > Servers need typed configuration and injection of components > ------------------------------------------------------------ > > Key: ISPN-1437 > URL: https://issues.jboss.org/browse/ISPN-1437 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Currently Infinispan servers cannot be plugged with executor services for the Netty master and worker threads, which makes them hard to manage in an app server environment where the app server might want to provide its own executors. > This might also require re-thinking how Infinispan servers are configured which currently rely on a bunch of properties. A typed approach would be welcome here. > In Lisbon, we had an interesting discussion around this but in the context of Infinispan core itself, how this is configured, how it has components injected that might be managed by an app server. He has some ideas based on the work he did for Weld, so maybe these can be applied to Infinispan servers too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1439) Async store needs redesigning to support injected executors

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1439?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-1439. ------------------------------------ Resolution: Out of Date > Async store needs redesigning to support injected executors > ----------------------------------------------------------- > > Key: ISPN-1439 > URL: https://issues.jboss.org/browse/ISPN-1439 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > The CoalescedAsyncStore design is pretty complex and is designed around AsyncStore being able to control the lifecycle of the async store coordinator and processor executors. > A re-design of the async store is needed to enable central management of these executors, in such way that the NamedExecutorFactory can start with the right parameters (take in account that multiple caches could be configured with an async store), and the shutdown procedure can be correctly executed by the cache manager. > The async store's coalesced logic makes this a fairly complex task, particularly since the introduction of Sanne's changes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1600) Use ServiceLoader to load other pluggable services

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1600?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-1600. ------------------------------------ Resolution: Won't Fix > Use ServiceLoader to load other pluggable services > -------------------------------------------------- > > Key: ISPN-1600 > URL: https://issues.jboss.org/browse/ISPN-1600 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > The most interesting services that could benefit from this are most likely: Externalizers and Cache Stores. > Other interesting candidates are maybe transaction manager lookup classes. > This could be extended to other parts such as hash functions...etc, but such extensions are not that common. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1441) Better and more sensible executor configuration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1441?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-1441. ------------------------------------ Resolution: Won't Fix > Better and more sensible executor configuration > ----------------------------------------------- > > Key: ISPN-1441 > URL: https://issues.jboss.org/browse/ISPN-1441 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: executors > > Dan and I had a chat about ISPN-1396 and we both agreed that a better configuration and management approach is needed for Infinispan's executors: > - Firstly, out of the box for SE environments, Infinispan should have executors configured with newCachedThreadPool because they provide better queuing performance than a fixed thread pool. > - Sure, in an managed env (i.e. AS), this won't fly, which is why all executors need to be injectable. This should be in place once ISPN-1396 is in place. > - So, if we go for cached thread pools for SE environments, we don't need any of the properties of executors any more. Besides, these can be more confusing for the user (there is knowledged of at least one case where things went wrong due to bad config here). So, the configuration would be limited to injecting executors. If you need any specific executor settings, pass us the right executors. To aid these cases, we could have some executor builders available with some common executor configuration for managed envs (i.e. we could borrow settings from AS?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018