June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12052) Allow CLI batch files to be processed on server startup

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-12052: ----------------------------------- Summary: Allow CLI batch files to be processed on server startup Key: ISPN-12052 URL: https://issues.redhat.com/browse/ISPN-12052 Project: Infinispan Issue Type: Enhancement Components: CLI, Server Affects Versions: 11.0.0.Final Reporter: Ryan Emerson Fix For: 12.0.0.Final The recommended way to configure Infinispan is now via the CLI. However, currently the server is unaware of the CLI syntax and simply processes it's command via the REST endpoint. We should enhance the server so that it's aware of the CLI syntax and is able to process one or more CLI batch files upon server startup. Crucially, the server's health checks should not pass untill all batches have been processed so that all configured resources are available before the server signals that it's ready. Providing batch files on startup is very useful for the Infinispan image, as it allows users to provide static configuration of caches at boot time without having to configure .xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12044) CLI performance test tool

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12044?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12044: ----------------------------------- Status: Open (was: New) > CLI performance test tool > ------------------------- > > Key: ISPN-12044 > URL: https://issues.redhat.com/browse/ISPN-12044 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > A performance test tool built into the CLI that can test the throughput and response time of an Infinispan server cluster. > * Hot Rod and REST > * put/get ratio > * key/value size > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12044) CLI performance test tool

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12044?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12044: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8500 > CLI performance test tool > ------------------------- > > Key: ISPN-12044 > URL: https://issues.redhat.com/browse/ISPN-12044 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > A performance test tool built into the CLI that can test the throughput and response time of an Infinispan server cluster. > * Hot Rod and REST > * put/get ratio > * key/value size > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12051) REST Client URI support

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-12051: -------------------------------------- Summary: REST Client URI support Key: ISPN-12051 URL: https://issues.redhat.com/browse/ISPN-12051 Project: Infinispan Issue Type: Enhancement Components: REST Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 12.0.0.Final This should be as close as possible to ISPN-11960 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12044) CLI performance test tool

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12044?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-12044: -------------------------------------- Assignee: Tristan Tarrant > CLI performance test tool > ------------------------- > > Key: ISPN-12044 > URL: https://issues.redhat.com/browse/ISPN-12044 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > A performance test tool built into the CLI that can test the throughput and response time of an Infinispan server cluster. > * Hot Rod and REST > * put/get ratio > * key/value size > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12035) RocksDB Options do not work with RocksDB examples

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12035?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12035: ----------------------------------- Priority: Minor (was: Major) > RocksDB Options do not work with RocksDB examples > ------------------------------------------------- > > Key: ISPN-12035 > URL: https://issues.redhat.com/browse/ISPN-12035 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Michael Burman > Priority: Minor > > RocksDB examples and configurations use a method to indicate the size in multiples, such as: > > db_options.db_write_buffer_size = 64 << 30; > > Or for example 512 * 1024 * 1024. This does not work with Infinispan, setting: > > > <property name="database.db_write_buffer_size">268435456</property> > vs > <property name="database.db_write_buffer_size">256 * 1024 * 1024</property> > > Ends with different result in the RocksDB, with only the first one working and the latter one causing the size to be 256 bytes instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12035) RocksDB Options do not work with RocksDB examples

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12035?page=com.atlassian.jira.plugi... ] Tristan Tarrant commented on ISPN-12035: ---------------------------------------- This would mean adding expression support to our parser which is something I'd like to avoid... > RocksDB Options do not work with RocksDB examples > ------------------------------------------------- > > Key: ISPN-12035 > URL: https://issues.redhat.com/browse/ISPN-12035 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Michael Burman > Priority: Minor > > RocksDB examples and configurations use a method to indicate the size in multiples, such as: > > db_options.db_write_buffer_size = 64 << 30; > > Or for example 512 * 1024 * 1024. This does not work with Infinispan, setting: > > > <property name="database.db_write_buffer_size">268435456</property> > vs > <property name="database.db_write_buffer_size">256 * 1024 * 1024</property> > > Ends with different result in the RocksDB, with only the first one working and the latter one causing the size to be 256 bytes instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12020) Simple Tutorial: Update Remote Cache Admin

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12020?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12020: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Simple Tutorial: Update Remote Cache Admin > ------------------------------------------ > > Key: ISPN-12020 > URL: https://issues.redhat.com/browse/ISPN-12020 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > The simple tutorial for creating remote caches shows how to add a static cache configuration to infinispan.xml in the server/conf directory. This should be removed because those caches are not synchronized across the cluster. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12050) Clean up Search Javadocs

by Donald Naro (Jira)

Donald Naro created ISPN-12050: ---------------------------------- Summary: Clean up Search Javadocs Key: ISPN-12050 URL: https://issues.redhat.com/browse/ISPN-12050 Project: Infinispan Issue Type: Enhancement Affects Versions: 11.0.0.Final Reporter: Donald Naro Assignee: Donald Naro Fix For: 12.0.0.Final Need to update Javadocs for org.infinispan.query.Search to reflect changes from deprecations and removals in 11. [https://docs.jboss.org/infinispan/11.0/apidocs/org/infinispan/query/Searc...] Also clarify terminology a little to distinguish between Search and Query. "Infinispan Search" provides the capabilities. Ickle is the query language. Add clarity by separating concepts a little throughout the Javadocs instead of using query to mean search. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11770) Add default Infinispan JGroups stacks for the test suite

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11770?page=com.atlassian.jira.plugi... ] Diego Lovison commented on ISPN-11770: -------------------------------------- The commit was https://github.com/infinispan/infinispan/commit/03deac03f3abab866cf63b0ee... > Add default Infinispan JGroups stacks for the test suite > -------------------------------------------------------- > > Key: ISPN-11770 > URL: https://issues.redhat.com/browse/ISPN-11770 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Server > Affects Versions: 11.0.0.Dev05, 10.1.7.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > > As a QE, I would like to set one argument and let the whole test suite behavior in the same way: > Today we need the following arguments: > * org.infinispan.test.server.cluster.stack > * infinispan.cluster.stack > It is not possible to use default-jgroups-tcp.xml or default-jgroups-udp.xml in the core module. In the server module, I can use it. > The name of the stacks for the core and server module is not matching. > * For the core, when using tcp, it is using stacks/test-tcp.xml > * For the server, when using tcp, it is using default-jgroups-tcp.xml > The main goals of this JIRA: > * Keep only one argument: infinispan.cluster.stack > * Allow the core module uses default-jgroups-tcp.xml or default-jgroups-udp.xml > * Standardize the stack name: > * * tcp -> default-jgroups-tcp.xml > * * udp -> default-jgroups-udp.xml > * * test-tcp -> tcp.xml > * * test-udp -> udp.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2020