[JBoss JIRA] (ISPN-9805) Use remote-timeout instead of state-transfer timeout for leave requests
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-9805?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9805:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Use remote-timeout instead of state-transfer timeout for leave requests
> -----------------------------------------------------------------------
>
> Key: ISPN-9805
> URL: https://issues.jboss.org/browse/ISPN-9805
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.0.0.Alpha1, 9.4.3.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> Normally the leave request should not block, but in rare cases it does. E.g. because of ISPN-9588, sometimes the leave request never gets a response, and only gives up after the state-transfer timeout expires (4 minutes by default). If the test has more than one cache (e.g. `org.infinispan.CONFIG` is running), it will be killed by `TestNGLongTestsHook` after 5 minutes.
> We should use the smaller `remote-timeout` so that nodes block for a shorter time before leaving.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9809) Added version.component.console
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9809?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-9809.
--------------------------------
Resolution: Done
> Added version.component.console
> -------------------------------
>
> Key: ISPN-9809
> URL: https://issues.jboss.org/browse/ISPN-9809
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> There is a patch that injects `version.component.console` property to the pom.xml to update the console in Infinispan. However, when the console updates, the patch fails to apply. Added the property upstream to avoid future issues...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9815) Expose Cache based Publisher
by William Burns (Jira)
William Burns created ISPN-9815:
-----------------------------------
Summary: Expose Cache based Publisher
Key: ISPN-9815
URL: https://issues.jboss.org/browse/ISPN-9815
Project: Infinispan
Issue Type: Sub-task
Reporter: William Burns
Assignee: William Burns
After we have all the underlying methods we need to expose some sort of API for the users to use a non blocking Publisher in the future. See ISPN-9721 for more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9814) Convert DistributedStreams to use Distributed Publisher for streaming response
by William Burns (Jira)
William Burns created ISPN-9814:
-----------------------------------
Summary: Convert DistributedStreams to use Distributed Publisher for streaming response
Key: ISPN-9814
URL: https://issues.jboss.org/browse/ISPN-9814
Project: Infinispan
Issue Type: Sub-task
Components: Publisher, Streams
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Final
After ISPN-9812 is complete we should be able to convert DistributedCacheStream#iterator method over to using Publisher. We _should_ be able to implement forEach as well possibly, but unclear.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9813) Convert DistributedStreams to use Distributed Publisher for single response
by William Burns (Jira)
William Burns created ISPN-9813:
-----------------------------------
Summary: Convert DistributedStreams to use Distributed Publisher for single response
Key: ISPN-9813
URL: https://issues.jboss.org/browse/ISPN-9813
Project: Infinispan
Issue Type: Sub-task
Components: Publisher, Streams
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Final
After ISPN-9811 is complete, we should be able to easily convert the existing DistributedCacheStream and friends to Publisher instead. This JIRA is to handle the terminal operations that return a single result (ie. Stream#count, Stream#collect, Stream#toArray, Stream#min, Stream#findAny etc.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9812) Implement streaming response publisher method
by William Burns (Jira)
William Burns created ISPN-9812:
-----------------------------------
Summary: Implement streaming response publisher method
Key: ISPN-9812
URL: https://issues.jboss.org/browse/ISPN-9812
Project: Infinispan
Issue Type: Sub-task
Components: Publisher
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Final
We need to implement a streaming based publisher that would support rehash. This is required for exposing the Cache as a Publisher or iterator properly. The example method to allow is quite simple:
{code}
<R> Publisher<R> compose(Function<? super Publisher<T>, ? extends Publisher<R>> publisherFunction);
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9811) Implement single response publisher methods
by William Burns (Jira)
William Burns created ISPN-9811:
-----------------------------------
Summary: Implement single response publisher methods
Key: ISPN-9811
URL: https://issues.jboss.org/browse/ISPN-9811
Project: Infinispan
Issue Type: Sub-task
Components: Publisher
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Final
We need to implement the backend for a method like
{code}
<R> CompletionStage<R> compose(Function<? super Publisher<T>, ? extends CompletionStage<R>> transformer,
Function<? super Publisher<R>, ? extends CompletionStage<R>> finalizer);
{code}
This would allow for all methods that don't require streaming results to be done very easily.
For example a count method can then just be implemented by doing:
{code}
java.util.function.Function<Publisher<?>, CompletionStage<Long>> transformer = cp ->
Flowable.fromPublisher(cp)
.count()
.to(RxJavaInterop.singleToCompletionStage());
java.util.function.Function<Publisher<Long>, CompletionStage<Long>> finalizer = results ->
Flowable.fromPublisher(results)
.reduce((long) 0, Long::sum)
.to(RxJavaInterop.singleToCompletionStage());
return infinispanPublisher.compose(transformer, finalizer);
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by William Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9693:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
> ---------------------------------------------------------------------------
>
> Key: ISPN-9693
> URL: https://issues.jboss.org/browse/ISPN-9693
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months