[JBoss JIRA] (ISPN-6247) Speed up DistWriteSkewTest and its subclasses
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6247?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6247:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.2.0.Final
Resolution: Done
> Speed up DistWriteSkewTest and its subclasses
> ---------------------------------------------
>
> Key: ISPN-6247
> URL: https://issues.jboss.org/browse/ISPN-6247
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 8.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.2.0.CR1, 8.2.0.Final
>
>
> {{DistWriteSkewTest}} is annotated with {{@CleanupAfterMethod}}, so the cluster is recreated for each one of the test methods. Since there are a lot of test methods inherited from {{AbstractClusteredWriteSkewTest}}, the repeated cluster startup and shutdown add a lot of overhead.
> Since the test doesn't start or stop nodes, it should be possible to start the cluster only once for the whole class, eventually using different key names if leftover keys turn out to be a problem.
> The annotation is also used for {{ReplWriteSkewTest}}, {{DistL1WriteSkewTest}}, and {{DistTotalOrderWriteSkewTest}}. It should be possible to reuse the cluster for all of them.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
6 years, 11 months
[JBoss JIRA] (ISPN-6289) SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation with the new log4j2 configuration
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6289?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6289:
-------------------------------
Description: When moving the log4j2 configuration files for ISPN-6255, I also made the file appender asynchronous. Because the async appender catches {{InterruptionException}} s and resets the thread interruption status, this affected {{SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation}}, and it's failing almost every time. (was: When moving the log4j2 configuration files for ISPN-6255, I also made the file appender asynchronous. Because the async appender catches {{InterruptionException}}s and resets the thread interruption status, this affected {{SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation}}, and it's failing almost every time.)
> SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation with the new log4j2 configuration
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-6289
> URL: https://issues.jboss.org/browse/ISPN-6289
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.2.0.CR1
>
>
> When moving the log4j2 configuration files for ISPN-6255, I also made the file appender asynchronous. Because the async appender catches {{InterruptionException}} s and resets the thread interruption status, this affected {{SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation}}, and it's failing almost every time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
6 years, 11 months
[JBoss JIRA] (ISPN-6289) SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation with the new log4j2 configuration
by Dan Berindei (JIRA)
Dan Berindei created ISPN-6289:
----------------------------------
Summary: SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation with the new log4j2 configuration
Key: ISPN-6289
URL: https://issues.jboss.org/browse/ISPN-6289
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.2.0.CR1
When moving the log4j2 configuration files for ISPN-6255, I also made the file appender asynchronous. Because the async appender catches {{InterruptionException}}s and resets the thread interruption status, this affected {{SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation}}, and it's failing almost every time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
6 years, 11 months
[JBoss JIRA] (ISPN-6256) Configuration in server guide is not working
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-6256?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek closed ISPN-6256.
---------------------------------
Resolution: Duplicate Issue
ISPN-6278 duplicates this issue, but it already contains link to PR (and Jira reference in the commit), so favoring ISPN-6278 :-)
> Configuration in server guide is not working
> --------------------------------------------
>
> Key: ISPN-6256
> URL: https://issues.jboss.org/browse/ISPN-6256
> Project: Infinispan
> Issue Type: Bug
> Components: Documentation-Servers
> Reporter: Roman Macor
>
> http://infinispan.org/docs/8.2.x/infinispan_server_guide/infinispan_serve...
> Configuration:
> {code:xml}
> <cache-container default-cache="secured">
> <security>
> <authorization mapper="org.infinispan.security.IdentityRoleMapper">
> <role name="admin" permissions="ALL" />
> <role name="reader" permissions="READ" />
> <role name="writer" permissions="WRITE" />
> <role name="supervisor" permissions="READ WRITE EXEC BULK"/>
> </roles>
> </security>
> <local-cache name="secured">
> <security>
> <authorization roles="admin reader writer supervisor" />
> </security>
> </local-cache>
> </cache-container>
> {code}
> Should be replaced with:
> {code:xml}
> <cache-container default-cache="secured">
> <security>
> <authorization>
> <identity-role-mapper />
> <role name="admin" permissions="ALL" />
> <role name="reader" permissions="READ" />
> <role name="writer" permissions="WRITE" />
> <role name="supervisor" permissions="READ WRITE EXEC BULK"/>
> </authorization>
> </security>
> <local-cache name="secured">
> <security>
> <authorization roles="admin reader writer supervisor" />
> </security>
> </local-cache>
> </cache-container>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
6 years, 11 months
[JBoss JIRA] (ISPN-6247) Speed up DistWriteSkewTest and its subclasses
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6247?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6247:
-------------------------------
Status: Open (was: New)
> Speed up DistWriteSkewTest and its subclasses
> ---------------------------------------------
>
> Key: ISPN-6247
> URL: https://issues.jboss.org/browse/ISPN-6247
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 8.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.2.0.CR1
>
>
> {{DistWriteSkewTest}} is annotated with {{@CleanupAfterMethod}}, so the cluster is recreated for each one of the test methods. Since there are a lot of test methods inherited from {{AbstractClusteredWriteSkewTest}}, the repeated cluster startup and shutdown add a lot of overhead.
> Since the test doesn't start or stop nodes, it should be possible to start the cluster only once for the whole class, eventually using different key names if leftover keys turn out to be a problem.
> The annotation is also used for {{ReplWriteSkewTest}}, {{DistL1WriteSkewTest}}, and {{DistTotalOrderWriteSkewTest}}. It should be possible to reuse the cluster for all of them.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
6 years, 11 months