April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6151) Drop Map/Reduce framework in favour of Distributed Streams

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6151?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-6151. --------------------------------- Fix Version/s: 9.0.0.Alpha1 (was: 9.0.0.Alpha2) Resolution: Done Map Reduce was replaced by Distributed Streams > Drop Map/Reduce framework in favour of Distributed Streams > ---------------------------------------------------------- > > Key: ISPN-6151 > URL: https://issues.jboss.org/browse/ISPN-6151 > Project: Infinispan > Issue Type: Task > Components: Distributed Execution and Map/Reduce > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6482) Allow to HR client to specify only trustore

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6482?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6482: ---------------------------------- Status: Open (was: New) > Allow to HR client to specify only trustore > ------------------------------------------- > > Key: ISPN-6482 > URL: https://issues.jboss.org/browse/ISPN-6482 > Project: Infinispan > Issue Type: Enhancement > Components: Security > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > HR encryption over SSL can be set up on without client certificate validation on server side (i.e. no client certificate is needed at all), but HR client doesn't provide any straightforward way hot to configure only trust store. The only way (little bit awkward) is to construct directly SSLConfig and set it up in HR client config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6482) Allow to HR client to specify only trustore

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6482?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6482: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4230 > Allow to HR client to specify only trustore > ------------------------------------------- > > Key: ISPN-6482 > URL: https://issues.jboss.org/browse/ISPN-6482 > Project: Infinispan > Issue Type: Enhancement > Components: Security > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > HR encryption over SSL can be set up on without client certificate validation on server side (i.e. no client certificate is needed at all), but HR client doesn't provide any straightforward way hot to configure only trust store. The only way (little bit awkward) is to construct directly SSLConfig and set it up in HR client config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6381) Add more tests for js-client

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-6381?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-6381: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/js-client/pull/4 > Add more tests for js-client > ---------------------------- > > Key: ISPN-6381 > URL: https://issues.jboss.org/browse/ISPN-6381 > Project: Infinispan > Issue Type: Task > Reporter: Anna Manukyan > Assignee: Anna Manukyan > > Add more tests for js-client. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3905) Murmurhash3 implementation is slow on String keys

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3905?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-3905: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Murmurhash3 implementation is slow on String keys > ------------------------------------------------- > > Key: ISPN-3905 > URL: https://issues.jboss.org/browse/ISPN-3905 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha2 > > > String instances are a common choice for being used as key entries, still the getBytes() operation being performed allocates costly buffers, and the computation to get those bytes looks like expensive too. > I suspect there might be good reasons for not using the String's own hashcode directly as an input to Murmurhash? Still that's what other implementations seem to do. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-3906: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2 > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-3835: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 9.0.0.Alpha2 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3918) Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3918?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-3918: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer > --------------------------------------------------------------------------------------- > > Key: ISPN-3918 > URL: https://issues.jboss.org/browse/ISPN-3918 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Fix For: 9.0.0.Alpha2 > > Attachments: ntpiadjst.log.gz > > > In a non-tx cache, sometimes it's possible for a {{get(k)}} to return {{null}} even though a previous {{putIfAbsent(k, v)}} returned a non-null value and the only concurrent operations on the cache are concurrent putIfAbsent calls. > Say \[B, A, C] are the owners of k (C just joined) > 1. A starts a {{putIfAbsent(k, v1)}} command, sends it to B > 2. B forwards the command to A and C > 3. C writes {{k=v1}} > 4. C becomes the primary owner of k (owners are now \[C, A]) > 5. A/B see the new topology before committing and throw an outdatedTopologyException > 6. A retries the command, sends it to C > 7. C forwards the command to A, which writes {{k=v1}} > 8. C doesn't have to update the entry, returns null > If, between steps 3 and 7, another thread on A starts a {{putIfAbsent(k, v2)}} command, the command will fail and return {{v1}} (because the primary owner already has a value). However, a subsequent {{get(k)}} command will return {{null}}, because A is an owner and doesn't have the value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3729) Minimize the number of moved segments for SyncConsistentHashFactory

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3729?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-3729: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Minimize the number of moved segments for SyncConsistentHashFactory > ------------------------------------------------------------------- > > Key: ISPN-3729 > URL: https://issues.jboss.org/browse/ISPN-3729 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha2 > > > SyncConsistentHash uses an algorithm that's similar to consistent hashing, but when there is a collision (two nodes map to the same segment), the second node is moved to the next segment. Since the nodes are ordered by their UUID, that means it's possible for a joiner to change the mapping of existing nodes. > In order to make the load distribution more even, SyncConsistentHash also uses "virtual nodes": each node actually maps to multiple segments. This makes the number of collisions much higher (and implicitly, the number of extra moved segments). > Reading the original [consistent hashing paper|http://thor.cs.ucsb.edu/~ravenben/papers/coreos/kll%2B97.pdf], it looks like the collision handling should be done differently: a joiner should replace an existing node when it's "closer" to the segment boundary, but the existing node should never "lose" segments to another existing node (the property of monotonicity mentioned in the paper). We should investigate whether changing this would allow us to achieve better load balancing by using a much higher number of "virtual nodes" (without moving extra segments). If successful, we could even use SyncConsistentHashFactory as the default hash algorithm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3344) Create a release script for ProtoStream library

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-3344: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Create a release script for ProtoStream library > ----------------------------------------------- > > Key: ISPN-3344 > URL: https://issues.jboss.org/browse/ISPN-3344 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 6.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2 > > > Need to add license information and a short README to the project. Also update the 'Cutting Infinispan Releases' document with relevant details for Protostream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016