[JBoss JIRA] (ISPN-11629) Initialize DataConversion storage media type only once
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11629?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11629:
--------------------------------
Status: Open (was: New)
> Initialize DataConversion storage media type only once
> ------------------------------------------------------
>
> Key: ISPN-11629
> URL: https://issues.redhat.com/browse/ISPN-11629
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 11.0.0.Dev03
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> {{DataConversion}} constructors have a {{storageMediaType}} parameter, but then the storage media type is overridden in {{injectDependencies()}}, except for the static instances defined as constants in {{DataConversion}}.
> {{InternalCacheFactory}} can also be simplified to only use the {{DataConversion}} s to create the {{EncoderCache}}, without passing them to the wrapped cache(s).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (ISPN-11629) Initialize DataConversion storage media type only once
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11629?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11629:
--------------------------------
Description:
{{DataConversion}} constructors have a {{storageMediaType}} parameter, but then the storage media type is overridden in {{injectDependencies()}}, except for the static instances defined as constants in {{DataConversion}}.
{{InternalCacheFactory}} can also be simplified to only use the {{DataConversion}} s to create the {{EncoderCache}}, without passing them to the wrapped cache(s).
was:
{{DataConversion}} constructors have a {{storageMediaType}} parameter, but then the storage media type is overridden in {{injectDependencies()}}, except for the static instances defined as constants in {{DataConversion}}.
{{InternalCacheFactory}} can also be simplified to only use the {{DataConversion}}s to create the {{EncoderCache}}, without passing them to the wrapped cache(s).
> Initialize DataConversion storage media type only once
> ------------------------------------------------------
>
> Key: ISPN-11629
> URL: https://issues.redhat.com/browse/ISPN-11629
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 11.0.0.Dev03
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> {{DataConversion}} constructors have a {{storageMediaType}} parameter, but then the storage media type is overridden in {{injectDependencies()}}, except for the static instances defined as constants in {{DataConversion}}.
> {{InternalCacheFactory}} can also be simplified to only use the {{DataConversion}} s to create the {{EncoderCache}}, without passing them to the wrapped cache(s).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11423?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11423:
-----------------------------------
Fix Version/s: 11.0.0.Dev05
(was: 11.0.0.Dev04)
> Dump information in panic scenarios
> -----------------------------------
>
> Key: ISPN-11423
> URL: https://issues.redhat.com/browse/ISPN-11423
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Server
> Affects Versions: 10.1.3.Final, 11.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level.
> The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default.
> These files can be sent to support via an SOS report.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11248) Add test for ServerTask that utilizes protostream stored entries
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11248?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11248:
-----------------------------------
Fix Version/s: 11.0.0.Dev05
(was: 11.0.0.Dev04)
> Add test for ServerTask that utilizes protostream stored entries
> ----------------------------------------------------------------
>
> Key: ISPN-11248
> URL: https://issues.redhat.com/browse/ISPN-11248
> Project: Infinispan
> Issue Type: Task
> Reporter: Will Burns
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> We currently have a single ServerTask that just prints out "Hello <name>". We should add a new test that actually tests a very likely use case of storing entries in protostream and using a task that deserializes them properly (this could be done automatically by the encoding layer of the cache, if it is working).
> We may also want to look into sharing this with a custom loader, as we have users doing this today. And it is quite clunky, so we can see how the usability is in 11.0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-5938) ClusterListenerReplInitialStateTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent fails randomly
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-5938?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-5938:
----------------------------------
Fix Version/s: 11.0.0.Dev05
(was: 11.0.0.Dev04)
> ClusterListenerReplInitialStateTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent fails randomly
> -------------------------------------------------------------------------------------------------
>
> Key: ISPN-5938
> URL: https://issues.redhat.com/browse/ISPN-5938
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 11.0.0.Alpha1
> Reporter: Roman Macor
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> ClusterListenerReplInitialStateTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent fails randomly with:
> Stacktrace
> java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:205)
> at org.infinispan.notifications.cachelistener.cluster.ClusterListenerReplTest.testPrimaryOwnerGoesDownAfterBackupRaisesEvent(ClusterListenerReplTest.java:123)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11304) Allow scaling up without state transfer
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11304?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11304:
-----------------------------------
Fix Version/s: 11.0.0.Dev05
(was: 11.0.0.Dev04)
> Allow scaling up without state transfer
> ---------------------------------------
>
> Key: ISPN-11304
> URL: https://issues.redhat.com/browse/ISPN-11304
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 10.1.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> We should allow a cache to scale up without performing any state transfer, but without losing the data.
> To simplify things, the initial version will support a single owner, and will assume that only one node is being added at a time.
> The cache must be accessible remotely, but since information about the location of the keys is not accessible from the client, the client is expected to ignore ownership and use a round-robin access strategy.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11381) AdvancedCache.getGroup(key) may return incomplete results during state transfer
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11381?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11381:
-----------------------------------
Fix Version/s: 11.0.0.Dev05
(was: 11.0.0.Dev04)
> AdvancedCache.getGroup(key) may return incomplete results during state transfer
> -------------------------------------------------------------------------------
>
> Key: ISPN-11381
> URL: https://issues.redhat.com/browse/ISPN-11381
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> {{AdvancedCache.getGroup(groupKey)}} returns all the keys that belong to a group.
> If the originator is not an owner, the command is forwarded to the primary owner. If the originator is a primary or a backup owner for the group key, the command is executed locally.
> During state transfer, a node may be a write owner for the group key but not a read owner. Currently {{GroupingInterceptor}} uses {{LocalizedCacheTopogy.isWriteOwner(groupKey)}} instead of {{isReadOwner(groupKey)}}, so it executes the command on the originator instead of forwarding it to the primary owner.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years