September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4710) DistributedSegmentReadLocker should be allowed to skip ReadLocks on small files

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-4710: ------------------------------------- Summary: DistributedSegmentReadLocker should be allowed to skip ReadLocks on small files Key: ISPN-4710 URL: https://issues.jboss.org/browse/ISPN-4710 Project: Infinispan Issue Type: Enhancement Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Gustavo Fernandes Fix For: 7.0.0.Beta2 Both of these methods: - {{org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(String)}} - {{org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.realFileDelete(FileReadLockKey, AdvancedCache<Object, Integer>, AdvancedCache<?, ?>, AdvancedCache<?, ?>, boolean)}} Are performing a lot of unnecessary operations - potentially on synchronous clustered caches - as we know in advance that files which are not being chunked don't need a read lock, and are not being chunked in smaller pieces (which affects how we delete things). The determining factor between the two styles is defined in: {{org.infinispan.lucene.impl.DirectoryLuceneV4.openInput(String, IOContext)}} {code}@Override public IndexInput openInput(final String name, final IOContext context) throws IOException { final IndexInputContext indexInputContext = impl.openInput(name); if ( indexInputContext.readLocks == null ) { return new SingleChunkIndexInput(indexInputContext); } else { return new InfinispanIndexInput(indexInputContext); } }{code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4709) Have Query enable asynchronous delete operations for the Directory automatically

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-4709: ------------------------------------- Summary: Have Query enable asynchronous delete operations for the Directory automatically Key: ISPN-4709 URL: https://issues.jboss.org/browse/ISPN-4709 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying Reporter: Sanne Grinovero Assignee: Gustavo Fernandes Fix For: 7.0.0.Beta2 Have the default Infinispan IndexManager apply ISPN-4708 to the Directory setup -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4708) Make DirectoryImplementor#deleteFile apply changes asynchronously

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-4708: ------------------------------------- Summary: Make DirectoryImplementor#deleteFile apply changes asynchronously Key: ISPN-4708 URL: https://issues.jboss.org/browse/ISPN-4708 Project: Infinispan Issue Type: Enhancement Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Gustavo Fernandes Fix For: 7.0.0.Beta2 Looks like the {{deleteFile}} operation is the main responsible component for the latency generated by writing to the Lucene Directory, but this operation could be processed asynchronously by a background thread. Configurtion API {{org.infinispan.lucene.directory.BuildContext}} could allow for an optional Executor to be passed for this purpose, and if there isn't we keep current behaviour for running it synchronously. The tricky part I guess is making sure that the tests, which verify written consistency -including delete operations - are refactored to be able to deal with the fact that delete operations will happen eventually. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4618) Map/Reduce jobs should not timeout by default

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4618?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4618: ----------------------------------------------- Rakesh <rghatvis(a)redhat.com> changed the Status of [bug 1128958|https://bugzilla.redhat.com/show_bug.cgi?id=1128958] from ASSIGNED to ON_QA > Map/Reduce jobs should not timeout by default > --------------------------------------------- > > Key: ISPN-4618 > URL: https://issues.jboss.org/browse/ISPN-4618 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Reporter: Sanne Grinovero > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Beta1 > > > It seems the fault of the jobs today is to timeout at the same timeout of replication commands. > The default should be to not timeout, and allow the user to optionially set a timeout. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4707) On leave, Hot Rod client ends up with old cluster formation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4707?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4707: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1140123 > On leave, Hot Rod client ends up with old cluster formation > ----------------------------------------------------------- > > Key: ISPN-4707 > URL: https://issues.jboss.org/browse/ISPN-4707 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Beta2 > > Attachments: hr-protocol-13.log, hr-protocol-20.log > > > In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure. On version 1.3 of the protocol, the cluster formation is updated correctly. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave

by Alan Field (JIRA)

[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ] Alan Field commented on ISPN-3223: ---------------------------------- Thanks, Galder > HotRod 2.0 Client recieves stale toplogy view on instance leave > --------------------------------------------------------------- > > Key: ISPN-3223 > URL: https://issues.jboss.org/browse/ISPN-3223 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 5.2.4.Final, 5.3.0.CR1, 7.0.0.Beta1 > Reporter: Takayoshi Kimura > Assignee: Galder Zamarreño > Fix For: 7.0.0.Beta2, 7.0.0.Final > > Attachments: hr-protocol-13.log, hr-protocol-20.log > > > When killed a HotRod server node, HotRod Clinet sometimes recieves a stale toplogy view which includes the dead node and uses it as a latest view. In this case the client keeps trying to connect that node and keeps failing. > Looks like the AbstractEncoder1x.generateTopologyResponse() takes care of node join but doesn't handle node leave: > {noformat} > if (!serverEndpointsMap.keySet.containsAll(cacheMembers)) { > {noformat} > For example, serverEndpointsMap.keySet is [A, B, C] and the actual cacheMembers is [A, B]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4700) Optimize non-indexed DSL 'like' queries

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4700?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-4700: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Optimize non-indexed DSL 'like' queries > --------------------------------------- > > Key: ISPN-4700 > URL: https://issues.jboss.org/browse/ISPN-4700 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta2 > > > Review usages of java.util.regex.Pattern -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4670) Profile and fine-tune the implementation of indexless query

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4670?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-4670: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Profile and fine-tune the implementation of indexless query > ----------------------------------------------------------- > > Key: ISPN-4670 > URL: https://issues.jboss.org/browse/ISPN-4670 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4707) On leave, Hot Rod client ends up with old cluster formation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4707?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4707: ----------------------------------- Attachment: hr-protocol-13.log hr-protocol-20.log > On leave, Hot Rod client ends up with old cluster formation > ----------------------------------------------------------- > > Key: ISPN-4707 > URL: https://issues.jboss.org/browse/ISPN-4707 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Beta2 > > Attachments: hr-protocol-13.log, hr-protocol-20.log > > > In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4707) On leave, Hot Rod client ends up with old cluster formation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4707?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4707: ----------------------------------- Description: In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure. On version 1.3 of the protocol, the cluster formation is updated correctly. (was: In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure.) > On leave, Hot Rod client ends up with old cluster formation > ----------------------------------------------------------- > > Key: ISPN-4707 > URL: https://issues.jboss.org/browse/ISPN-4707 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Beta2 > > Attachments: hr-protocol-13.log, hr-protocol-20.log > > > In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure. On version 1.3 of the protocol, the cluster formation is updated correctly. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2014