[JBoss JIRA] (ISPN-4001) Add a test with the JPACacheStore in client server mode
by Mircea Markus (JIRA)
Mircea Markus created ISPN-4001:
-----------------------------------
Summary: Add a test with the JPACacheStore in client server mode
Key: ISPN-4001
URL: https://issues.jboss.org/browse/ISPN-4001
Project: Infinispan
Issue Type: Feature Request
Components: Server
Reporter: Mircea Markus
Assignee: Mircea Markus
It should be possible to use the JPA cache store in client/server mode. On top of that, it would be useful that the data the HR clients writes to be available for read directly from the database, through SQL.
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4000) Delta view logging
by Takayoshi Kimura (JIRA)
[ https://issues.jboss.org/browse/ISPN-4000?page=com.atlassian.jira.plugin.... ]
Work on ISPN-4000 started by Takayoshi Kimura.
> Delta view logging
> ------------------
>
> Key: ISPN-4000
> URL: https://issues.jboss.org/browse/ISPN-4000
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Takayoshi Kimura
> Assignee: Takayoshi Kimura
>
> Currently on view change the only log we have is "INFO ISPN000094: Received new cluster view".
> {noformat}
> 11:36:27,355 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) ISPN000094: Received new cluster view: [localhost-7255|23] (24) [localhost-7255, localhost-51221, localhost-12479, localhost-1550, localhost-10300, localhost-11620, localhost-35337, localhost-40886, localhost-3020, localhost-51201, localhost-32626, localhost-17205, localhost-2984, localhost-45021, localhost-23189, localhost-9189, localhost-12902, localhost-38468, localhost-36454, localhost-63088 ...]
> {noformat}
> In a large cluster environment the view list is truncated at max.list.print_size sys prop value, 20 by default. We can increase it but it's still hard to see who is joined/left.
> It would be nice to see the delta on view change, like the following:
> {noformat}
> 11:36:27,355 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) Joined: [localhost-8582], Left: []
> {noformat}
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4000) Delta view logging
by Takayoshi Kimura (JIRA)
[ https://issues.jboss.org/browse/ISPN-4000?page=com.atlassian.jira.plugin.... ]
Takayoshi Kimura updated ISPN-4000:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2384
> Delta view logging
> ------------------
>
> Key: ISPN-4000
> URL: https://issues.jboss.org/browse/ISPN-4000
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Takayoshi Kimura
> Assignee: Takayoshi Kimura
>
> Currently on view change the only log we have is "INFO ISPN000094: Received new cluster view".
> {noformat}
> 11:36:27,355 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) ISPN000094: Received new cluster view: [localhost-7255|23] (24) [localhost-7255, localhost-51221, localhost-12479, localhost-1550, localhost-10300, localhost-11620, localhost-35337, localhost-40886, localhost-3020, localhost-51201, localhost-32626, localhost-17205, localhost-2984, localhost-45021, localhost-23189, localhost-9189, localhost-12902, localhost-38468, localhost-36454, localhost-63088 ...]
> {noformat}
> In a large cluster environment the view list is truncated at max.list.print_size sys prop value, 20 by default. We can increase it but it's still hard to see who is joined/left.
> It would be nice to see the delta on view change, like the following:
> {noformat}
> 11:36:27,355 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) Joined: [localhost-8582], Left: []
> {noformat}
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4000) Delta view logging
by Takayoshi Kimura (JIRA)
[ https://issues.jboss.org/browse/ISPN-4000?page=com.atlassian.jira.plugin.... ]
Work on ISPN-4000 stopped by Takayoshi Kimura.
> Delta view logging
> ------------------
>
> Key: ISPN-4000
> URL: https://issues.jboss.org/browse/ISPN-4000
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Takayoshi Kimura
> Assignee: Takayoshi Kimura
>
> Currently on view change the only log we have is "INFO ISPN000094: Received new cluster view".
> {noformat}
> 11:36:27,355 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) ISPN000094: Received new cluster view: [localhost-7255|23] (24) [localhost-7255, localhost-51221, localhost-12479, localhost-1550, localhost-10300, localhost-11620, localhost-35337, localhost-40886, localhost-3020, localhost-51201, localhost-32626, localhost-17205, localhost-2984, localhost-45021, localhost-23189, localhost-9189, localhost-12902, localhost-38468, localhost-36454, localhost-63088 ...]
> {noformat}
> In a large cluster environment the view list is truncated at max.list.print_size sys prop value, 20 by default. We can increase it but it's still hard to see who is joined/left.
> It would be nice to see the delta on view change, like the following:
> {noformat}
> 11:36:27,355 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) Joined: [localhost-8582], Left: []
> {noformat}
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4000) Delta view logging
by Takayoshi Kimura (JIRA)
Takayoshi Kimura created ISPN-4000:
--------------------------------------
Summary: Delta view logging
Key: ISPN-4000
URL: https://issues.jboss.org/browse/ISPN-4000
Project: Infinispan
Issue Type: Feature Request
Components: Core
Affects Versions: 6.0.1.Final
Reporter: Takayoshi Kimura
Assignee: Takayoshi Kimura
Currently on view change the only log we have is "INFO ISPN000094: Received new cluster view".
{noformat}
11:36:27,355 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) ISPN000094: Received new cluster view: [localhost-7255|23] (24) [localhost-7255, localhost-51221, localhost-12479, localhost-1550, localhost-10300, localhost-11620, localhost-35337, localhost-40886, localhost-3020, localhost-51201, localhost-32626, localhost-17205, localhost-2984, localhost-45021, localhost-23189, localhost-9189, localhost-12902, localhost-38468, localhost-36454, localhost-63088 ...]
{noformat}
In a large cluster environment the view list is truncated at max.list.print_size sys prop value, 20 by default. We can increase it but it's still hard to see who is joined/left.
It would be nice to see the delta on view change, like the following:
{noformat}
11:36:27,355 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) Joined: [localhost-8582], Left: []
{noformat}
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-3999) Invoke reducer immediatelly as intermediate VOut values are being collected
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-3999?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic reassigned ISPN-3999:
-----------------------------------------
Assignee: Vladimir Blagojevic (was: Mircea Markus)
> Invoke reducer immediatelly as intermediate VOut values are being collected
> ---------------------------------------------------------------------------
>
> Key: ISPN-3999
> URL: https://issues.jboss.org/browse/ISPN-3999
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
>
> Currently in intermediate phase [1] as values for every KOut are being collected/grouped in the cluster we simply add every VOut to the list of values key by KOut. In reducer phase we then send a reducer function that gets invoked on List<VOut> and reduces those values into single VOut. However, this could be suboptimal as we can invoke reducer function as every VOut gets grouped rather than wait for all VOut values to be collected and then invoke reducer. However, reduce function could potentially take a lot of time to execute even for one value thus causing prolonged locking and congestions. We should implement this enhancement and do thorough performance measurements. This feature should be have an API setting in MapReduceTask.
> Sanne Grinovero gets the credit for this idea.
> [1] http://blog.infinispan.org/2012/07/mapreduce-improvements-in-infinispan.html
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-3999) Invoke reducer immediatelly as intermediate VOut values are being collected
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-3999?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-3999:
--------------------------------------
Priority: Minor (was: Major)
> Invoke reducer immediatelly as intermediate VOut values are being collected
> ---------------------------------------------------------------------------
>
> Key: ISPN-3999
> URL: https://issues.jboss.org/browse/ISPN-3999
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Minor
>
> Currently in intermediate phase [1] as values for every KOut are being collected/grouped in the cluster we simply add every VOut to the list of values key by KOut. In reducer phase we then send a reducer function that gets invoked on List<VOut> and reduces those values into single VOut. However, this could be suboptimal as we can invoke reducer function as every VOut gets grouped rather than wait for all VOut values to be collected and then invoke reducer. However, reduce function could potentially take a lot of time to execute even for one value thus causing prolonged locking and congestions. We should implement this enhancement and do thorough performance measurements. This feature should be have an API setting in MapReduceTask.
> Sanne Grinovero gets the credit for this idea.
> [1] http://blog.infinispan.org/2012/07/mapreduce-improvements-in-infinispan.html
--
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
12 years, 1 month