[JBoss JIRA] (ISPN-11049) Infinispan Server should resolve all the console URLs
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11049?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-11049:
--------------------------------
Sprint: DataGrid Sprint #37
> Infinispan Server should resolve all the console URLs
> -----------------------------------------------------
>
> Key: ISPN-11049
> URL: https://issues.redhat.com/browse/ISPN-11049
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.1.0.Beta1
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> Infinispan server serves the console from the static resources. This console is an front end app built in react that contains multiple URL paths.
> When we do F5 on a URL that is not 'console' or 'console/wlecome' the server responds with 404.
> The static resource (or console resource) should be able to serve the console app from any of the '/console/*' Urls so there is no 404 when there ir s refresh
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-11049) Infinispan Server should resolve all the console URLs
by Katia Aresti (Jira)
Katia Aresti created ISPN-11049:
-----------------------------------
Summary: Infinispan Server should resolve all the console URLs
Key: ISPN-11049
URL: https://issues.redhat.com/browse/ISPN-11049
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 10.1.0.Beta1
Reporter: Katia Aresti
Infinispan server serves the console from the static resources. This console is an front end app built in react that contains multiple URL paths.
When we do F5 on a URL that is not 'console' or 'console/wlecome' the server responds with 404.
The static resource (or console resource) should be able to serve the console app from any of the '/console/*' Urls so there is no 404 when there ir s refresh
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-11049) Infinispan Server should resolve all the console URLs
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11049?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-11049:
--------------------------------
Status: Open (was: New)
> Infinispan Server should resolve all the console URLs
> -----------------------------------------------------
>
> Key: ISPN-11049
> URL: https://issues.redhat.com/browse/ISPN-11049
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.1.0.Beta1
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> Infinispan server serves the console from the static resources. This console is an front end app built in react that contains multiple URL paths.
> When we do F5 on a URL that is not 'console' or 'console/wlecome' the server responds with 404.
> The static resource (or console resource) should be able to serve the console app from any of the '/console/*' Urls so there is no 404 when there ir s refresh
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-11049) Infinispan Server should resolve all the console URLs
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11049?page=com.atlassian.jira.plugi... ]
Katia Aresti reassigned ISPN-11049:
-----------------------------------
Assignee: Katia Aresti
> Infinispan Server should resolve all the console URLs
> -----------------------------------------------------
>
> Key: ISPN-11049
> URL: https://issues.redhat.com/browse/ISPN-11049
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.1.0.Beta1
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> Infinispan server serves the console from the static resources. This console is an front end app built in react that contains multiple URL paths.
> When we do F5 on a URL that is not 'console' or 'console/wlecome' the server responds with 404.
> The static resource (or console resource) should be able to serve the console app from any of the '/console/*' Urls so there is no 404 when there ir s refresh
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10963) Remove blocking queue from RocksDBStore
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-10963?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-10963:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 10.1.0.CR1
Resolution: Done
> Remove blocking queue from RocksDBStore
> ---------------------------------------
>
> Key: ISPN-10963
> URL: https://issues.redhat.com/browse/ISPN-10963
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Alpha1
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Major
> Fix For: 10.1.0.CR1, 10.1.0.Final
>
>
> Currently you can only insert 10000 elements into the rocks db store until you will block a thread until the expiration reaper is ran.
> By default it will be running each minute and the client will totally block.
> {code:java}
> cacheManager.defineConfiguration("weather", new ConfigurationBuilder()
> .persistence()
> .addStore(RocksDBStoreConfigurationBuilder.class)
> .location("target/data")
> .expiredLocation("target/expired")
> .expiration().lifespan(5, TimeUnit.SECONDS)
> .build());
> cache = cacheManager.getCache("weather");
> int max = 10001;
> for (int i=0; i<max; i++) {
> cache.put(UUID.randomUUID().toString(), UUID.randomUUID().toString());
> }
> {code}
> The test took 60478ms.
> 9999 = 1773 ms
> 10000 = 1797 ms
> Removing the queue and writing directly to RocksDB will be faster than the current code
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months