[JBoss JIRA] (ISPN-9346) Off-heap implementation crashes JVM
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9346?page=com.atlassian.jira.plugin.... ]
William Burns resolved ISPN-9346.
---------------------------------
Resolution: Duplicate Issue
> Off-heap implementation crashes JVM
> -----------------------------------
>
> Key: ISPN-9346
> URL: https://issues.jboss.org/browse/ISPN-9346
> Project: Infinispan
> Issue Type: Enhancement
> Components: Off Heap
> Affects Versions: 9.1.1.Final
> Reporter: Dmitry Katsubo
> Assignee: William Burns
> Attachments: logs.7z
>
>
> There is a suspect that off-heap implementation has caused attached JVM crashes (see [^logs.7z]).
> There are no steps to reproduce. Perhaps somebody encounters the same issue.
> Log extract:
> {code}
> SIGSEGV (0xb) at pc=0x00007fb9a2f358ad, pid=42551, tid=140426343024384
> Problematic frame:
> J 17187 C1 org.infinispan.container.offheap.BoundedOffHeapDataContainer.moveToEnd(J)V (137 bytes) @ 0x00007fb9a2f358ad [0x00007fb9a2f357a0+0x10d]
> J 17205 C1 org.infinispan.container.offheap.BoundedOffHeapDataContainer.entryRetrieved(J)V (74 bytes) @ 0x00007fb9a2e02c2c [0x00007fb9a2e02960+0x2cc]
> J 17295 C1 org.infinispan.container.offheap.OffHeapDataContainer.performGet(JLjava/lang/Object;)Lorg/infinispan/container/entries/InternalCacheEntry; (72 bytes) @ 0x00007fb9a310c5ac [0x00007fb9a310c000+0x5ac]
> J 18853 C1 org.infinispan.container.offheap.OffHeapDataContainer.compute(Lorg/infinispan/commons/marshall/WrappedBytes;Lorg/infinispan/container/DataContainer$ComputeAction;)Lorg/infinispan/container/entries/InternalCacheEntry; (157 bytes) @ 0x00007fb9a250e814 [0x00007fb9a250dd00+0xb14]
> J 18851 C1 org.infinispan.container.offheap.BoundedOffHeapDataContainer.compute(Ljava/lang/Object;Lorg/infinispan/container/DataContainer$ComputeAction;)Lorg/infinispan/container/entries/InternalCacheEntry; (10 bytes) @ 0x00007fb9a4658cbc [0x00007fb9a4658ae0+0x1dc]
> J 18840 C1 org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(Lorg/infinispan/container/entries/InternalCacheEntry;J)V (24 bytes) @ 0x00007fb9a1a2e55c [0x00007fb9a1a2e0e0+0x47c]
> j org.infinispan.expiration.impl.ExpirationManagerImpl.processExpiration()V+95
> j org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run()V+17
> J 15131 C2 java.util.concurrent.Executors$RunnableAdapter.call()Ljava/lang/Object; (14 bytes) @ 0x00007fb9a3cef368 [0x00007fb9a3cee200+0x1168]
> {code}
> Infinispan v9.1.1.Final
> Java v1.8.0_74-b02
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-9433:
-----------------------------------------
I don't think it is really important to have this hierarchy replicated in field scope at protobuf level. It is very polluting, and having the complexDef elsewhere under a certain name works great
> Add test for external analyzers
> -------------------------------
>
> Key: ISPN-9433
> URL: https://issues.jboss.org/browse/ISPN-9433
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying, Test Suite - Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Also it should test that Lucene analyzers can be defined.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-9433:
-------------------------------------
That capability of HSearch comes in the form of AnalyzerDef/CharFilterDef/TokenizerDef/TokenFilterDef annotations, which we do not implement in proto.
I thought about how hard it would be to implement them at proto level, which would provide tremendous flexibility, but dropped the idea because these annotations are polluted with Class references, which started to be a problem after HSearch added Elastic Search support. I know they want to redesign them in HSearch Next, so we might be able to implement them in future.
> Add test for external analyzers
> -------------------------------
>
> Key: ISPN-9433
> URL: https://issues.jboss.org/browse/ISPN-9433
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying, Test Suite - Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Also it should test that Lucene analyzers can be defined.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9433:
------------------------------------
Description:
The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
Also it should test that Lucene analyzers can be defined.
was:
The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
Also it should test that Lucene analyzers can be defined, and last but not least, analyzers can be defined at protobuf mapping level, by composing filters/tokenizers
> Add test for external analyzers
> -------------------------------
>
> Key: ISPN-9433
> URL: https://issues.jboss.org/browse/ISPN-9433
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying, Test Suite - Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Also it should test that Lucene analyzers can be defined.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-9433:
-----------------------------------------
Fair enough, I might have misunderstood its capabilities, I will remove this last "requirement"
> Add test for external analyzers
> -------------------------------
>
> Key: ISPN-9433
> URL: https://issues.jboss.org/browse/ISPN-9433
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying, Test Suite - Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Also it should test that Lucene analyzers can be defined, and last but not least, analyzers can be defined at protobuf mapping level, by composing filters/tokenizers
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-9433:
-------------------------------------
[~gustavonalle] Tthe @Analyzer (pseudo)annotation in protobuf can only take an analyzer definition name and cannot be used to define an analyzer on the spot by composing filters/tokenizers. Not sure if that's doable with hibernate-search's annotations, but certainly not possible with protobuf. So I'm not sure what you mean by "..and last but not least, analyzers can be defined at protobuf mapping level, by composing filters/tokenizers". The definition can only be done in the ProgrammaticSearchProvider while the *.proto file can only reference this definition by its name.
> Add test for external analyzers
> -------------------------------
>
> Key: ISPN-9433
> URL: https://issues.jboss.org/browse/ISPN-9433
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying, Test Suite - Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Also it should test that Lucene analyzers can be defined, and last but not least, analyzers can be defined at protobuf mapping level, by composing filters/tokenizers
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9433:
------------------------------------
Description:
The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
Also it should test that Lucene analyzers can be defined, and last but not least, analyzers can be defined at protobuf mapping level, by composing filters/tokenizers
was:The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Add test for external analyzers
> -------------------------------
>
> Key: ISPN-9433
> URL: https://issues.jboss.org/browse/ISPN-9433
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying, Test Suite - Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
> Also it should test that Lucene analyzers can be defined, and last but not least, analyzers can be defined at protobuf mapping level, by composing filters/tokenizers
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9433) Add test for external analyzers
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-9433:
---------------------------------------
Summary: Add test for external analyzers
Key: ISPN-9433
URL: https://issues.jboss.org/browse/ISPN-9433
Project: Infinispan
Issue Type: Task
Components: Remote Querying, Test Suite - Server
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The test need to verify that it's possible to deploy full fledged analyzers through the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache manager's module extensions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9209) Implement RemoteCache statistics
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9209?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9209:
----------------------------------
Fix Version/s: 9.4.0.Final
Sprint: Sprint 9.4.0.CR1
> Implement RemoteCache statistics
> --------------------------------
>
> Key: ISPN-9209
> URL: https://issues.jboss.org/browse/ISPN-9209
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.4.0.Final
>
>
> The Hot Rod client does not expose any local statistics (RemoteCacheManager.getStatistics() returns the server-side stats).
> We should have the following per-cache stats:
> - remote hits and hit avg time
> - remote misses and miss avg time
> - remote removes and remove avg time
> - near cache hits and avg time
> - near cache miss and avg time
> - near cache size
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months