April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9040) Legacy JDBC update failures on Oracle and DB2

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-9040: ---------------------------------- Summary: Legacy JDBC update failures on Oracle and DB2 Key: ISPN-9040 URL: https://issues.jboss.org/browse/ISPN-9040 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 9.2.1.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.2.2.Final When upsert is disabled, both updates on the JDBC store will fail for the Oracle and DB2 database due to the PreparedStatement setting the wrong values for the corresponding SQL. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8980) High concurrency : Infinispan Directory Provider: Lucene : Error loading metadata for index file

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8980?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-8980: --------------------------------------- Hello, the {{AutoNodeSelector}} has several limitations, it's still marked "experimental" because the main contributors on that area moved to use Inifnispan Query's IndexManager. The longer term plan is to port some of the improvements back into Hibernate Search; coincidentally I'm working this week to update the Hibernate Search codebase to JGroups 4. I believe your problem might be related to: https://hibernate.atlassian.net/browse/HSEARCH-1554 : in short, a lack of timely lock migration. A workaround could be to set {{hibernate.search.default.exclusive_index_use=false}}; I believe that should avoid the locking problem but it comes at a performance penalty. See also https://hibernate.atlassian.net/browse/HSEARCH-2598 > High concurrency : Infinispan Directory Provider: Lucene : Error loading metadata for index file > ------------------------------------------------------------------------------------------------ > > Key: ISPN-8980 > URL: https://issues.jboss.org/browse/ISPN-8980 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 8.2.5.Final > Reporter: Debashish Bharali > Assignee: Gustavo Fernandes > Priority: Critical > Attachments: SysOutLogs.txt, neutrino-hibernate-search-worker-jgroups.xml, neutrino-hibernatesearch-infinispan.xml > > > During high concurrency of action, we are getting *{color:red}'Error loading metadata for index file'{color}* even in *{color:red}Non-Clustered{color}* env. > *Hibernate Search Indexes (Lucene Indexes) - 5.7.0.Final* > *Infinispan - 8.2.5.Final* > *infinispan-directory-provider-8.2.5.Final* > *jgroups-3.6.7.Final* > *Worker Backend : JGroups* > *Worker Execution: Sync* > *write_metadata_async: false (implicitly)* > *Note:* Currently we are on Non-Clustered env. We are moving to Clustered Env within few days. > On analyzing the code, and putting some additional SYSOUT loggers into FileListOperations and DirectoryImplementor classes, we have established the following points: > # This is happening during high concurrency on non-clustered env. > # One thread *'T1'* is deleting a segment and segment name *'SEG1'* from the *'FileListCacheKey'* list* stored in MetaDatacache*. > # Concurrently, at the same time, another thread *'T2'* is looping through the FileList ['copy list' from MetadataCache - for -FileListCacheKey - provided by toArray method of *FileListOperations* (changes also being done in the corresponding original list by T1 thread) ]. > # *'T2'* is calling open input method on each segment name - getting corresponding Metadata segment from *MetadataCache*. > # However, for *'T2'*, the *'copy list'* still contains the name of segment *'SEG1'*. > # So while looping through the list, *'T2'* tries to get Segment from MetadataCache for segment name *'SEG1'*. > # But at this instant, *segment* corresponding to segment name *'SEG1'*, has been already removed from *MetadataCache* by *'T1'*. > # This results in *'java.io.FileNotFoundException: Error loading metadata for index file'* for segment name *'SEG1'* > # As mentioned earlier, this happens more often during high concurrency. > *{color:red}On a standalone server (non-clustered), we are getting below error intermittently:{color}* > Full Stack trace: > 2018-03-19 17:29:11,938 ERROR [Hibernate Search sync consumer thread for index com.nucleus.integration.ws.server.globalcustomer.entity.GlobalCustomer] o.h.s.e.i.LogErrorHandler [LogErrorHandler.java:69] > *{color:red}HSEARCH000058: Exception occurred java.io.FileNotFoundException: Error loading metadata for index file{color}*: M|segments_w6|com.nucleus.integration.ws.server.globalcustomer.entity.GlobalCustomer|-1 > Primary Failure: > Entity com.nucleus.integration.ws.server.globalcustomer.entity.GlobalCustomer Id 1649990024999813056 Work Type org.hibernate.search.backend.AddLuceneWork > java.io.FileNotFoundException: Error loading metadata for index file: M|segments_w6|com.nucleus.integration.ws.server.globalcustomer.entity.GlobalCustomer|-1 > at org.infinispan.lucene.impl.DirectoryImplementor.openInput(DirectoryImplementor.java:138) ~[infinispan-lucene-directory-8.2.5.Final.jar:8.2.5.Final] > at org.infinispan.lucene.impl.DirectoryLucene.openInput(DirectoryLucene.java:102) ~[infinispan-lucene-directory-8.2.5.Final.jar:8.2.5.Final] > at org.apache.lucene.store.Directory.openChecksumInput(Directory.java:109) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:294) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:171) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:949) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.createNewIndexWriter(IndexWriterHolder.java:126) ~[hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.getIndexWriter(IndexWriterHolder.java:92) ~[hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.AbstractCommitPolicy.getIndexWriter(AbstractCommitPolicy.java:33) ~[hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.SharedIndexCommitPolicy.getIndexWriter(SharedIndexCommitPolicy.java:77) ~[hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.SharedIndexWorkspaceImpl.getIndexWriter(SharedIndexWorkspaceImpl.java:36) ~[hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriterDelegate(AbstractWorkspaceImpl.java:203) [hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.applyUpdates(LuceneBackendQueueTask.java:81) [hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.run(LuceneBackendQueueTask.java:46) [hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.applyChangesets(SyncWorkProcessor.java:165) [hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.run(SyncWorkProcessor.java:151) [hibernate-search-engine-5.7.0.Final.jar:5.7.0.Final] > at java.lang.Thread.run(Thread.java:785) [na:1.8.0-internal] > *As per our understanding, this issue should not come in {color:red}'non-clustered'{color} env. Also it should not arise when worker execution is {color:red}'sync'{color}.* > *We have debugged the code, and confirmed that the value for {color:red}'write_metadata_async'{color} is coming as 'false' only (as expected).* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9039) Parametrized admin console branding

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9039?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-9039: ----------------------------------------- Assignee: Vladimir Blagojevic > Parametrized admin console branding > ----------------------------------- > > Key: ISPN-9039 > URL: https://issues.jboss.org/browse/ISPN-9039 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9039) Parametrized admin console branding

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-9039: ----------------------------------------- Summary: Parametrized admin console branding Key: ISPN-9039 URL: https://issues.jboss.org/browse/ISPN-9039 Project: Infinispan Issue Type: Sub-task Components: Console Reporter: Vladimir Blagojevic -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9038) UNICAST3 conn_expiry_timeout should use JGroups default value

by Rich DiCroce (JIRA)

Rich DiCroce created ISPN-9038: ---------------------------------- Summary: UNICAST3 conn_expiry_timeout should use JGroups default value Key: ISPN-9038 URL: https://issues.jboss.org/browse/ISPN-9038 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.1.6.Final Reporter: Rich DiCroce Per [~belaban]'s comments on JGRP-2260, WildFly should not change the default conn_expiry_timeout for UNICAST3. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9037) Release Docker images from CI

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9037: ------------------------------------- Summary: Release Docker images from CI Key: ISPN-9037 URL: https://issues.jboss.org/browse/ISPN-9037 Project: Infinispan Issue Type: Enhancement Components: OpenShift, Build Reporter: Tristan Tarrant Assignee: Osni Oliveira -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7979) Include all component licenses in distributions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7979?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-7979: ------------------------------------- Assignee: Jakub Senko (was: Tristan Tarrant) > Include all component licenses in distributions > ----------------------------------------------- > > Key: ISPN-7979 > URL: https://issues.jboss.org/browse/ISPN-7979 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Tristan Tarrant > Assignee: Jakub Senko > Priority: Blocker > Fix For: 9.3.0.Final > > > The distributions should include licenses for all components -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9036: ---------------------------------- Summary: Parameterized branding for C++ (was: Parameterized branding fot C++) > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding fot C++

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9036: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Parameterized branding fot C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding fot C++

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9036: ------------------------------------- Summary: Parameterized branding fot C++ Key: ISPN-9036 URL: https://issues.jboss.org/browse/ISPN-9036 Project: Infinispan Issue Type: Enhancement Reporter: Tristan Tarrant Assignee: Vittorio Rigamonti -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2018