[JBoss JIRA] (ISPN-11010) Server should support config server
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-11010?page=com.atlassian.jira.plugin... ]
Diego Lovison updated ISPN-11010:
---------------------------------
Summary: Server should support config server (was: Server should support URL configuration)
> Server should support config server
> -----------------------------------
>
> Key: ISPN-11010
> URL: https://issues.jboss.org/browse/ISPN-11010
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.1.0.Beta1
> Reporter: Diego Lovison
> Priority: Major
>
> As a developer, I would like to store the configurations outside the project.
> A few changes are required before that:
> 1) Server should support all in one config file (xml|yalm)
> The config file should support all configuration available at `server.sh -h`
> Example: *config.yaml*
> {code:yaml}
> bind-address: localhost
> server-config: infinispan.xml
> {code}
> In this case, I am going to start the server with: server.sh --file-config=config.yaml
> 2) In order to have all configuration in one place, as a developer I would like to have the following:
> {code:yaml}
> infinispan:
> config:
> server:
> git:
> uri: https://github.com/infinispan/config-repo
> username: foo
> password: foo123
> bind-address: localhost
> server-config: infinispan.xml
> {code}
> Different authentications should be supported like:
> {code:yaml}
> uri: git@gitserver.com:infinispan/repo1.git
> ignoreLocalSshSettings: true
> hostKey: myKey
> hostKeyAlgorithm: ssh-rsa
> privateKey: |
> -----BEGIN RSA PRIVATE KEY-----
> bLaH
> -----END RSA PRIVATE KEY-----
> {code}
> It allows the team have a centralised configuration files with formal approval (aka PR).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-11007?page=com.atlassian.jira.plugin... ]
Dan Berindei commented on ISPN-11007:
-------------------------------------
There is one issue common to integration tests in general: the {{maven-failsafe-plugin}} system properties do not include most of the properties defined for {{maven-surefire-plugin}}, like {{log4j.configurationFile}} and {{java.net.preferIPv4Stack}}.
> State Transfer hangs on org.infinispan.CONFIG cache
> ---------------------------------------------------
>
> Key: ISPN-11007
> URL: https://issues.jboss.org/browse/ISPN-11007
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.1.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
> Priority: Major
> Attachments: log.trace, log.txt, stack
>
>
> Observed when running the tests from integrationtests/elasticsearch-indexmanager-it
> Attached the stack stack trace and debug log.
> When running with -Dinfinispan.cluster.stack=tcp it works
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-11007?page=com.atlassian.jira.plugin... ]
Dan Berindei commented on ISPN-11007:
-------------------------------------
The trace log shows that the node B node doesn't receive any UDP multicast messages from node A (the coordinator).
No idea why it doesn't work only in this particular test.
> State Transfer hangs on org.infinispan.CONFIG cache
> ---------------------------------------------------
>
> Key: ISPN-11007
> URL: https://issues.jboss.org/browse/ISPN-11007
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.1.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
> Priority: Major
> Attachments: log.trace, log.txt, stack
>
>
> Observed when running the tests from integrationtests/elasticsearch-indexmanager-it
> Attached the stack stack trace and debug log.
> When running with -Dinfinispan.cluster.stack=tcp it works
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11009) Server should support a custom path for the log file
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-11009?page=com.atlassian.jira.plugin... ]
Dan Berindei edited comment on ISPN-11009 at 11/29/19 10:06 AM:
----------------------------------------------------------------
Implemented as {{\-l}} and {{--logging-config}}
was (Author: dan.berindei):
Implemented as {{-l}} and {{--logging-config}}
> Server should support a custom path for the log file
> ----------------------------------------------------
>
> Key: ISPN-11009
> URL: https://issues.jboss.org/browse/ISPN-11009
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.1.0.Beta1
> Reporter: Diego Lovison
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> As a developer I would like to have my static log property file and setup it when starting the server
> {noformat}
> ./server.sh -log /path/to/my-logging.properties
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years