[JBoss JIRA] (ISPN-5743) SIFS.start() throws IllegalArgumentException: Negative position
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5743?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5743:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.Alpha2
8.2.2.Final
9.0.0.Final
Resolution: Done
> SIFS.start() throws IllegalArgumentException: Negative position
> ----------------------------------------------------------------
>
> Key: ISPN-5743
> URL: https://issues.jboss.org/browse/ISPN-5743
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> This can happen when a record about deletion of entry with the same key was read recently and was not applied into index.
> Fix is quite trivial, but this revealed a situation when an entry can be reincarnated during cache store startup - since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5753) SIFS can reincarnate deleted entries during startup
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5753?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5753:
----------------------------------
Status: Pull Request Sent (was: Open)
> SIFS can reincarnate deleted entries during startup
> ---------------------------------------------------
>
> Key: ISPN-5753
> URL: https://issues.jboss.org/browse/ISPN-5753
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> Since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order. Then we could add the entry into the index even though it was deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5753) SIFS can reincarnate deleted entries during startup
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5753?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5753:
----------------------------------
Fix Version/s: 9.0.0.Alpha2
8.2.2.Final
9.0.0.Final
> SIFS can reincarnate deleted entries during startup
> ---------------------------------------------------
>
> Key: ISPN-5753
> URL: https://issues.jboss.org/browse/ISPN-5753
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> Since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order. Then we could add the entry into the index even though it was deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5753) SIFS can reincarnate deleted entries during startup
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5753?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5753:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> SIFS can reincarnate deleted entries during startup
> ---------------------------------------------------
>
> Key: ISPN-5753
> URL: https://issues.jboss.org/browse/ISPN-5753
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> Since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order. Then we could add the entry into the index even though it was deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5743) SIFS.start() throws IllegalArgumentException: Negative position
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5743?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5743:
----------------------------------
Status: Pull Request Sent (was: Open)
> SIFS.start() throws IllegalArgumentException: Negative position
> ----------------------------------------------------------------
>
> Key: ISPN-5743
> URL: https://issues.jboss.org/browse/ISPN-5743
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
>
> This can happen when a record about deletion of entry with the same key was read recently and was not applied into index.
> Fix is quite trivial, but this revealed a situation when an entry can be reincarnated during cache store startup - since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5943) Access log and statistics of cache operations
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5943?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-5943:
--------------------------------
Description:
The HotRod and REST endpoint will have a dedicated log category, which will be disabled by default, to which we will log using a format which follows the typical HTTPD server access.log format, i.e. client_ip user_id timestamp op key response_size processing_time.
Enabling the log will be possible either by configuring the XML or by using the CLI.
was:
The HotRod and REST endpoint will have a dedicated log category, which will be disabled by default, to which we will log using a format which follows the typical HTTPD server access.log format, i.e. client_ip user_id timestamp op key response_size processing_time.
Enabling the log will be possible either by configuring the XML or by using the CLI.
Additional JMX and DMR metrics will be implemented which report the number of invocations for each operation, their cumulative execution time, and the average execution time.
> Access log and statistics of cache operations
> ---------------------------------------------
>
> Key: ISPN-5943
> URL: https://issues.jboss.org/browse/ISPN-5943
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Pedro Zapata
> Assignee: William Burns
> Labels: jdg7
>
> The HotRod and REST endpoint will have a dedicated log category, which will be disabled by default, to which we will log using a format which follows the typical HTTPD server access.log format, i.e. client_ip user_id timestamp op key response_size processing_time.
> Enabling the log will be possible either by configuring the XML or by using the CLI.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6521) Statistics for Server
by William Burns (JIRA)
William Burns created ISPN-6521:
-----------------------------------
Summary: Statistics for Server
Key: ISPN-6521
URL: https://issues.jboss.org/browse/ISPN-6521
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management, Server
Reporter: William Burns
JMX and DMR metrics will be implemented which report the number of invocations for each operation, their cumulative execution time, and the average execution time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months