[JBoss JIRA] (ISPN-4851) Make SyncConsistentHashFactory the default CH factory
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4851?page=com.atlassian.jira.plugin.... ]
Work on ISPN-4851 started by Dan Berindei.
------------------------------------------
> Make SyncConsistentHashFactory the default CH factory
> -----------------------------------------------------
>
> Key: ISPN-4851
> URL: https://issues.jboss.org/browse/ISPN-4851
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration, Core
> Affects Versions: 7.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 7.1.0.Beta1
>
>
> With ISPN-4682 fixed, SyncConsistentHashFactory should be good enough to be the default. It still allows for more variation in the number of owned segments per node (+/-10% owned segments and +/-20% for primary-owned segments), but that should be acceptable for most purposes.
> The major advantage of SCHF is that it depends only on the cache members and not on the order they joined. Users expect a key to map to the same node in all caches (as long as the caches have the same members).
> One downside of SCHF, especially for testing, is that the segment ownership differs between test runs (being based on the random address assigned to each node). However, most tests that depend on key ownership should use {{ControlledConsistentHashFactory}} anyway.
> We also need to verify that the number of segments moved by SCHF is comparable to the number of segments moved by DefaultConsistentHashFactory (ISPN-3729).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-4322) AS Remote Client Module Integration Tests module fails with IBM JDK
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-4322?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek commented on ISPN-4322:
---------------------------------------
fails as there's not {{jps}} utility in IBM JDK, needs to be re-worked to use some other approach how to kill running java applications
> AS Remote Client Module Integration Tests module fails with IBM JDK
> -------------------------------------------------------------------
>
> Key: ISPN-4322
> URL: https://issues.jboss.org/browse/ISPN-4322
> Project: Infinispan
> Issue Type: Bug
> Components: Integration
> Affects Versions: 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4
> Environment: IBM JDK, RHEL
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Labels: testsuite_stability
>
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Infinispan BOM .................................... SUCCESS [10.419s]
> [INFO] Infinispan Common Parent .......................... SUCCESS [16.691s]
> [INFO] Infinispan Commons ................................ SUCCESS [30.414s]
> [INFO] Infinispan Core ................................... SUCCESS [1:20:24.345s]
> [INFO] Parent pom for server modules ..................... SUCCESS [2.764s]
> [INFO] Infinispan Server - Core Components ............... SUCCESS [1:39.998s]
> [INFO] Infinispan Query DSL API .......................... SUCCESS [3.182s]
> [INFO] Parent pom for cachestore modules ................. SUCCESS [1.421s]
> [INFO] Infinispan JDBC CacheStore ........................ SUCCESS [7:13.024s]
> [INFO] Parent pom for the Lucene integration modules ..... SUCCESS [1.302s]
> [INFO] Infinispan integration with Lucene v.3.x .......... SUCCESS [1:22.270s]
> [INFO] Infinispan Lucene Directory Implementation ........ SUCCESS [5.801s]
> [INFO] Infinispan Query API .............................. SUCCESS [16:27.946s]
> [INFO] Infinispan Tools .................................. SUCCESS [12.958s]
> [INFO] Infinispan Remote Query Client .................... SUCCESS [3.958s]
> [INFO] Infinispan Remote Query Server .................... SUCCESS [16.646s]
> [INFO] Infinispan JPA CacheStore ......................... SUCCESS [54.680s]
> [INFO] Infinispan Hot Rod Server ......................... SUCCESS [6:13.951s]
> [INFO] Infinispan Hot Rod Client ......................... SUCCESS [9:17.450s]
> [INFO] Parent pom for compatibility modules .............. SUCCESS [0.876s]
> [INFO] infinispan-custom52x-store ........................ SUCCESS [33.084s]
> [INFO] infinispan-adaptor52x ............................. SUCCESS [4:05.587s]
> [INFO] Infinispan remote CacheStore ...................... SUCCESS [53.506s]
> [INFO] Infinispan LevelDB CacheStore ..................... SUCCESS [1:19.592s]
> [INFO] Infinispan REST Server ............................ SUCCESS [2:08.409s]
> [INFO] Infinispan REST CacheStore ........................ SUCCESS [16.715s]
> [INFO] Infinispan Memcached Server ....................... SUCCESS [2:22.394s]
> [INFO] Infinispan RHQ Plugin ............................. SUCCESS [42.140s]
> [INFO] Infinispan CLI Server ............................. SUCCESS [48.143s]
> [INFO] Infinispan CLI Client ............................. SUCCESS [16.878s]
> [INFO] Infinispan CDI support ............................ SUCCESS [1:24.550s]
> [INFO] Infinispan AS/EAP modules for library ............. SUCCESS [18.319s]
> [INFO] Infinispan AS/EAP modules for remote client ....... SUCCESS [2.329s]
> [INFO] Integration tests: Security Tests ................. SUCCESS [2:11.936s]
> [INFO] Integration tests: SecurityManager tests .......... SUCCESS [13.313s]
> [INFO] Integration tests: AS Module Integration Tests .... SUCCESS [1:10.370s]
> [INFO] Integration tests: AS Remote Client Module Integration Tests FAILURE [57.162s]
> [INFO] Integration tests: Lucene Directory with Infinispan Query SUCCESS [23.074s]
> [INFO] Integration tests: Infinispan compatibility mode .. SUCCESS [35.351s]
> [INFO] Infinispan Distribution ........................... SUCCESS [1.090s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2:26:30.994s
> [INFO] Finished at: Fri May 23 21:38:55 EDT 2014
> [INFO] Final Memory: 227M/542M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (infinispan-server-shutdown) on project infinispan-as-module-remote-client-integrationtests: An Ant BuildException has occured: Execute failed: java.io.IOException: Cannot run program "/qa/tools/opt/amd64/ibm-java-70/bin/jps" (in directory "/mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client"): error=2, No such file or directory
> [ERROR] around Ant part ...<exec executable="/qa/tools/opt/amd64/ibm-java-70/bin/jps" output="jps.pid" osfamily="unix"/>... @ 4:96 in /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :infinispan-as-module-remote-client-integrationtests
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5097) Server jgroups configuration does not specify defaults for S3
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-5097?page=com.atlassian.jira.plugin.... ]
Alan Field edited comment on ISPN-5097 at 1/5/15 4:55 PM:
----------------------------------------------------------
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without editing the XML file. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
{noformat}
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
{noformat}
This error also occurs if you try to set the value on the command line to a blank. (-Djgroups.s3.access_key=) I think fixing this is also going to require a code change.
was (Author: afield):
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without specifying all 6 properties on the command line. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
{noformat}
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
{noformat}
This error also occurs if you try to set the value on the command line to a blank. (-Djgroups.s3.access_key=) I think fixing this is also going to require a code change.
> Server jgroups configuration does not specify defaults for S3
> -------------------------------------------------------------
>
> Key: ISPN-5097
> URL: https://issues.jboss.org/browse/ISPN-5097
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Blocker
> Fix For: 7.1.0.Beta1
>
>
> Since we now properly expand expressions in the JGroups subsystem the server fails to start because the S3 properties don't have defaults
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5097) Server jgroups configuration does not specify defaults for S3
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-5097?page=com.atlassian.jira.plugin.... ]
Alan Field edited comment on ISPN-5097 at 1/5/15 2:37 PM:
----------------------------------------------------------
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without specifying all 6 properties on the command line. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
{noformat}
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
{noformat}
This error also occurs if you try to set the value on the command line to a blank. (-Djgroups.s3.access_key=) I think fixing this is also going to require a code change.
was (Author: afield):
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without specifying all 6 properties on the command line. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
{noformat}
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
{noformat}
I think fixing this is also going to require a code change.
> Server jgroups configuration does not specify defaults for S3
> -------------------------------------------------------------
>
> Key: ISPN-5097
> URL: https://issues.jboss.org/browse/ISPN-5097
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Blocker
> Fix For: 7.1.0.Beta1
>
>
> Since we now properly expand expressions in the JGroups subsystem the server fails to start because the S3 properties don't have defaults
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5119) Fail fast when using two phase commit with ASYNC backup strategy
by Matej Čimbora (JIRA)
Matej Čimbora created ISPN-5119:
-----------------------------------
Summary: Fail fast when using two phase commit with ASYNC backup strategy
Key: ISPN-5119
URL: https://issues.jboss.org/browse/ISPN-5119
Project: Infinispan
Issue Type: Bug
Components: Configuration, Cross-Site Replication
Affects Versions: 7.0.3.Final
Reporter: Matej Čimbora
Assignee: Matej Čimbora
Example:
<backup site="LON" useTwoPhaseCommit="true" strategy="ASYNC"/>
>From xsd (two-phase-commit):
Whether a backup will use a 2PC cycle for SYNC backups. Defaults to "false". NOTE: Not used for ASYNC backup strategies.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5097) Server jgroups configuration does not specify defaults for S3
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-5097?page=com.atlassian.jira.plugin.... ]
Alan Field edited comment on ISPN-5097 at 1/5/15 2:00 PM:
----------------------------------------------------------
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without specifying all 6 properties on the command line. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
{noformat}
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
{noformat}
I think fixing this is also going to require a code change.
was (Author: afield):
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without specifying all 6 properties on the command line. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
I think fixing this is also going to require a code change.
> Server jgroups configuration does not specify defaults for S3
> -------------------------------------------------------------
>
> Key: ISPN-5097
> URL: https://issues.jboss.org/browse/ISPN-5097
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Blocker
> Fix For: 7.1.0.Beta1
>
>
> Since we now properly expand expressions in the JGroups subsystem the server fails to start because the S3 properties don't have defaults
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5097) Server jgroups configuration does not specify defaults for S3
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-5097?page=com.atlassian.jira.plugin.... ]
Alan Field reopened ISPN-5097:
------------------------------
Specifying defaults for each of these S3 properties means that you can't configure the server to run in AWS without specifying all 6 properties on the command line. It should be possible to have a blank default value for a property, but specifying a colon at the end of the property name produces this error:
13:50:42,479 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 23) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "s3")
]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters"
I think fixing this is also going to require a code change.
> Server jgroups configuration does not specify defaults for S3
> -------------------------------------------------------------
>
> Key: ISPN-5097
> URL: https://issues.jboss.org/browse/ISPN-5097
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Blocker
> Fix For: 7.1.0.Beta1
>
>
> Since we now properly expand expressions in the JGroups subsystem the server fails to start because the S3 properties don't have defaults
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years