[JBoss JIRA] (ISPN-12043) Shared stores should not have (add|remove)Segments methods invoked
by Will Burns (Jira)
Will Burns created ISPN-12043:
---------------------------------
Summary: Shared stores should not have (add|remove)Segments methods invoked
Key: ISPN-12043
URL: https://issues.redhat.com/browse/ISPN-12043
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 11.0.0.Final
Reporter: Will Burns
Assignee: Will Burns
Fix For: 12.0.0.Final, 11.0.1.…
[View More]Final
A shared store should never have its remove or add segments methods invoked as the store should always own all segments at all times. We should add this check in the PeristenceManagerImpl and technically we should only invoke these methods if the store is also configured as being segmented.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
4 years, 8 months
[JBoss JIRA] (ISPN-11641) JVM crashed. SIGSEGV in org.rocksdb.RocksIterator.next0
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11641?page=com.atlassian.jira.plugi... ]
Will Burns edited comment on ISPN-11641 at 6/22/20 1:20 PM:
------------------------------------------------------------
[~dan.berindei], It should not be possible to have an iterator open during the close invocation as of 9.3.0 when I converted stores to use Publisher as we protected that via the Semaphore.
However, I think it is possible to open an iterator when we do a clear that may have deleted the …
[View More]database.
was (Author: william.burns):
It should not be possible to have an iterator open during the close invocation as of 9.3.0 when I converted stores to use Publisher as we protected that via the Semaphore.
However, I think it is possible to open an iterator when we do a clear that may have deleted the database.
> JVM crashed. SIGSEGV in org.rocksdb.RocksIterator.next0
> -------------------------------------------------------
>
> Key: ISPN-11641
> URL: https://issues.redhat.com/browse/ISPN-11641
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.4.16.Final
> Reporter: Sergey Morgunov
> Priority: Major
> Attachments: crash.log
>
>
> *JRE*: OpenJDK 8u222.
> Crash log attached. (crash.log)
> Cache configuration:
> {code:xml}
> <distributed-cache name="sessions" configuration="sessionsConfiguration">
> <memory>
> <object size="100000" strategy="REMOVE"/>
> </memory>
> <persistence passivation="false">
> <rocksdb-store path="cache/warm/" preload="true" fetch-state="true">
> <expiration path="cache/expired/"/>
> </rocksdb-store>
> </persistence>
> </distributed-cache>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
4 years, 8 months
[JBoss JIRA] (ISPN-11641) JVM crashed. SIGSEGV in org.rocksdb.RocksIterator.next0
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11641?page=com.atlassian.jira.plugi... ]
Will Burns commented on ISPN-11641:
-----------------------------------
It should not be possible to have an iterator open during the close invocation as of 9.3.0 when I converted stores to use Publisher as we protected that via the Semaphore.
However, I think it is possible to open an iterator when we do a clear that may have deleted the database.
> JVM crashed. SIGSEGV in org.rocksdb.RocksIterator.next0
&…
[View More]gt; -------------------------------------------------------
>
> Key: ISPN-11641
> URL: https://issues.redhat.com/browse/ISPN-11641
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.4.16.Final
> Reporter: Sergey Morgunov
> Priority: Major
> Attachments: crash.log
>
>
> *JRE*: OpenJDK 8u222.
> Crash log attached. (crash.log)
> Cache configuration:
> {code:xml}
> <distributed-cache name="sessions" configuration="sessionsConfiguration">
> <memory>
> <object size="100000" strategy="REMOVE"/>
> </memory>
> <persistence passivation="false">
> <rocksdb-store path="cache/warm/" preload="true" fetch-state="true">
> <expiration path="cache/expired/"/>
> </rocksdb-store>
> </persistence>
> </distributed-cache>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
4 years, 8 months
[JBoss JIRA] (ISPN-11151) Migrating some remote tests from jdg-functional-tests to upstream
by Gustavo Lira e Silva (Jira)
[ https://issues.redhat.com/browse/ISPN-11151?page=com.atlassian.jira.plugi... ]
Gustavo Lira e Silva updated ISPN-11151:
----------------------------------------
Summary: Migrating some remote tests from jdg-functional-tests to upstream (was: Migrating some remote jdbc-cachestore tests from jdg-functional-tests to upstream)
> Migrating some remote tests from jdg-functional-tests to upstream
> -----------------------------------------------------------------
>
> …
[View More] Key: ISPN-11151
> URL: https://issues.redhat.com/browse/ISPN-11151
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Gustavo Lira e Silva
> Assignee: Gustavo Lira e Silva
> Priority: Major
>
> Some tests from jdg-functional-tests needs to be migrate to upstream.
> Tests that will be migrated:
> new tests into MemcachedOperations
> new tests into RestOperations
> AsyncJdbcStringBasedCacheStore
> JdbcStringBasedCacheStorePassivationDisabled
> JdbcStringBasedCacheStorePassivationEnabled
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
4 years, 8 months
[JBoss JIRA] (ISPN-12042) RemoteCacheConfigurationBuilder only implements Builder
by Donald Naro (Jira)
Donald Naro created ISPN-12042:
----------------------------------
Summary: RemoteCacheConfigurationBuilder only implements Builder
Key: ISPN-12042
URL: https://issues.redhat.com/browse/ISPN-12042
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 11.0.0.Final
Reporter: Donald Naro
{color:#333333}RemoteCacheConfigurationBuilder only implements Builder so you can't …
[View More]chain config methods from its result.
{color}
{color:#333333}For example, the following does not compile if you call remoteCache on the same builder:
{color}
{color:#333333}{{.{color:#7b8e29}remoteCache{color}({color:#6da02b}"another-cache"{color}).{color:#7b8e29}configuration{color}({color:#6da02b}"<infinispan><cache-container><distributed-cache name=\"another-cache\"/></cache-container></infinispan>"{color}).{color:#7b8e29}remoteCache{color}({color:#6da02b}"my-cache"{color}).{color:#7b8e29}templateName{color}({color:#6da02b}"org.infinispan.DIST_SYNC"{color});}}{color}
{color:#333333}This works:
builder.remoteCache("another-cache")
.configuration("<infinispan><cache-container><distributed-cache name=\"another-cache\"/></cache-container></infinispan>");
builder.remoteCache("my-cache")
.templateName("org.infinispan.DIST_SYNC");{color}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
4 years, 8 months