[JBoss JIRA] (ISPN-3119) Cleanup the scripts we ship with the distribution
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3119?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3119:
--------------------------------
Summary: Cleanup the scripts we ship with the distribution (was: cleanup demo scritps)
> Cleanup the scripts we ship with the distribution
> --------------------------------------------------
>
> Key: ISPN-3119
> URL: https://issues.jboss.org/browse/ISPN-3119
> Project: Infinispan
> Issue Type: Task
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 5.3.0.CR1, 5.3.0.Final
>
>
> Make sure that all the scripts we ship as part of the distribution are correct. Also update the [release process| https://docspace.corp.redhat.com/docs/DOC-28594] with exact stept to test the scripts we ship, e.g.
> {quote}
> 1. memcached server
> $ ./startServer.sh -r memcached
> # from a different console test the client
> $ ./memcache.py
> - ./bin/startServer.sh -r memcached
> 2. Pi approximation demo. Open 3 consoles on the same machine
> $ ./runPiApproximationDemo.sh
> $ ./runPiApproximationDemo.sh
> $ ./runPiApproximationDemo.sh -t master
> {quote}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-3119) cleanup demo scritps
by Mircea Markus (JIRA)
Mircea Markus created ISPN-3119:
-----------------------------------
Summary: cleanup demo scritps
Key: ISPN-3119
URL: https://issues.jboss.org/browse/ISPN-3119
Project: Infinispan
Issue Type: Task
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.3.0.CR1, 5.3.0.Final
Make sure that all the scripts we ship as part of the distribution are correct. Also update the [release process| https://docspace.corp.redhat.com/docs/DOC-28594] with exact stept to test the scripts we ship, e.g.
{quote}
1. memcached server
$ ./startServer.sh -r memcached
# from a different console test the client
$ ./memcache.py
- ./bin/startServer.sh -r memcached
2. Pi approximation demo. Open 3 consoles on the same machine
$ ./runPiApproximationDemo.sh
$ ./runPiApproximationDemo.sh
$ ./runPiApproximationDemo.sh -t master
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-2903) Manual eviction should not delete entry from cache store
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2903:
-----------------------------------------------
Aleksandar Kostadinov <akostadi(a)redhat.com> made a comment on [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549]
> Manual eviction should not delete entry from cache store
> --------------------------------------------------------
>
> Key: ISPN-2903
> URL: https://issues.jboss.org/browse/ISPN-2903
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.2.3.Final
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: 5.2.x, jdg6
> Fix For: 5.2.5.Final, 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java, server.log, server.log
>
>
> Here's the scenario:
> Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7).
> 1. Create cache entry containing atomic map with 2 map entries on node1.
> 2. Passivate that cache entry on node2 via manual evict.
> 3. Modify 1 of the atomic map entries within the cache entry on node1.
> 4. Lookup atomic map on node2. It only contains 1 map entry - the map entry modified in step 3. The other map entry is lost.
> It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-2903) Manual eviction should not delete entry from cache store
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2903:
-----------------------------------------------
Aleksandar Kostadinov <akostadi(a)redhat.com> made a comment on [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549]
@Paul, I've run clustering failover tests in EC2 and I'm still hitting NPEs and looking at the clustedbench app it does NOT have passivation active. I'm attaching 6.1.0 ER8 full server log and the app itself so you can review.
> Manual eviction should not delete entry from cache store
> --------------------------------------------------------
>
> Key: ISPN-2903
> URL: https://issues.jboss.org/browse/ISPN-2903
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.2.3.Final
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: 5.2.x, jdg6
> Fix For: 5.2.5.Final, 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: AtomicMapServlet.java, AtomicMapTestCase.java, server.log, server.log
>
>
> Here's the scenario:
> Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7).
> 1. Create cache entry containing atomic map with 2 map entries on node1.
> 2. Passivate that cache entry on node2 via manual evict.
> 3. Modify 1 of the atomic map entries within the cache entry on node1.
> 4. Lookup atomic map on node2. It only contains 1 map entry - the map entry modified in step 3. The other map entry is lost.
> It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months