[JBoss JIRA] (ISPN-6086) Hadoop MapReduce task fails after the prefered ispn server stopped
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6086?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-6086 at 2/2/16 11:57 AM:
------------------------------------------------------------------
The issue is that the Splitter only creates Splits with a single host/ip, and if the server goes down after the job starts, but before the task actually contacts the Infinispan server, there's no way of discovering the other nodes. This can be solved by propagating the list of servers to the tasks rather than only one. Created https://issues.jboss.org/browse/IHDP-2
was (Author: gustavonalle):
The issue is that the Splitter only accepts one host/ip, and if the server goes down after the job starts, but before the task actually contacts the Infinispan server, there's no way of discovering the other nodes. This can be solved by allowing propagating the list of servers to the tasks rather than only one. Created https://issues.jboss.org/browse/IHDP-2
> Hadoop MapReduce task fails after the prefered ispn server stopped
> -------------------------------------------------------------------
>
> Key: ISPN-6086
> URL: https://issues.jboss.org/browse/ISPN-6086
> Project: Infinispan
> Issue Type: Bug
> Components: Hadoop Integration
> Reporter: Anna Manukyan
> Assignee: Gustavo Fernandes
> Attachments: FailoverTest_when_prefered_stopped.log
>
>
> I have added tests to the infinispan-hadoop testsuite testing the load balancing of mapreduce task in case if the input server which is specified as a parameter to Hadoop configuration is stopped.
> The test is performed on 4 node cluster. The data read is performed from Infinispan cache, the write is performed to HDFS.
> There are 200000 entries in the cache. As soon as the Hadoop Job is submitted for performing map/reduce task, the preferred server is stopped.
> As a result, the Hadoop Map/Reduce result map is empty.
> You can find the test execution log attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6086) Hadoop MapReduce task fails after the prefered ispn server stopped
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6086?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-6086 at 2/2/16 11:56 AM:
------------------------------------------------------------------
The issue is that the Splitter only accepts one host/ip, and if the server goes down after the job starts, but before the task actually contacts the Infinispan server, there's no way of discovering the other nodes. This can be solved by allowing propagating the list of servers to the tasks rather than only one. Created https://issues.jboss.org/browse/IHDP-2
was (Author: gustavonalle):
The issue is that the connector configuration only accepts one host/ip, and if the server goes down after the job starts, but before the task actually contacts the Infinispan server, there's no way of discovering the other nodes. This can be solved by allowing the configuration to have more than 1 server. Created https://issues.jboss.org/browse/IHDP-2
> Hadoop MapReduce task fails after the prefered ispn server stopped
> -------------------------------------------------------------------
>
> Key: ISPN-6086
> URL: https://issues.jboss.org/browse/ISPN-6086
> Project: Infinispan
> Issue Type: Bug
> Components: Hadoop Integration
> Reporter: Anna Manukyan
> Assignee: Gustavo Fernandes
> Attachments: FailoverTest_when_prefered_stopped.log
>
>
> I have added tests to the infinispan-hadoop testsuite testing the load balancing of mapreduce task in case if the input server which is specified as a parameter to Hadoop configuration is stopped.
> The test is performed on 4 node cluster. The data read is performed from Infinispan cache, the write is performed to HDFS.
> There are 200000 entries in the cache. As soon as the Hadoop Job is submitted for performing map/reduce task, the preferred server is stopped.
> As a result, the Hadoop Map/Reduce result map is empty.
> You can find the test execution log attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6086) Hadoop MapReduce task fails after the prefered ispn server stopped
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6086?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-6086:
-----------------------------------------
The issue is that the connector configuration only accepts one host/ip, and if the server goes down after the job starts, but before the task actually contacts the Infinispan server, there's no way of discovering the other nodes. This can be solved by allowing the configuration to have more than 1 server. Created https://issues.jboss.org/browse/IHDP-2
> Hadoop MapReduce task fails after the prefered ispn server stopped
> -------------------------------------------------------------------
>
> Key: ISPN-6086
> URL: https://issues.jboss.org/browse/ISPN-6086
> Project: Infinispan
> Issue Type: Bug
> Components: Hadoop Integration
> Reporter: Anna Manukyan
> Assignee: Gustavo Fernandes
> Attachments: FailoverTest_when_prefered_stopped.log
>
>
> I have added tests to the infinispan-hadoop testsuite testing the load balancing of mapreduce task in case if the input server which is specified as a parameter to Hadoop configuration is stopped.
> The test is performed on 4 node cluster. The data read is performed from Infinispan cache, the write is performed to HDFS.
> There are 200000 entries in the cache. As soon as the Hadoop Job is submitted for performing map/reduce task, the preferred server is stopped.
> As a result, the Hadoop Map/Reduce result map is empty.
> You can find the test execution log attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6022) Unable to query cache when data is preloaded via AdvancedCacheLoader#process
by Dan Siviter (JIRA)
[ https://issues.jboss.org/browse/ISPN-6022?page=com.atlassian.jira.plugin.... ]
Dan Siviter updated ISPN-6022:
------------------------------
Affects Version/s: 8.1.1.Final
> Unable to query cache when data is preloaded via AdvancedCacheLoader#process
> ----------------------------------------------------------------------------
>
> Key: ISPN-6022
> URL: https://issues.jboss.org/browse/ISPN-6022
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Loaders and Stores
> Affects Versions: 8.1.0.Final, 8.1.1.Final
> Reporter: Dan Siviter
>
> When preloading from a {{AdvancedCacheLoader}} the index doesn't get updated. Therefore it is only possible to query items that have been {{#put(...)}} into the cache. I am able to get preloaded items from the cache using their key which leads me to think the index is never built on pre-load.
> I've seen no implicit rebuilding of caches in any of the existing {{AdvancedCacheLoader#process(...)}} which leads me to think this will not work with any of them.
> I've verified this reindexing using {{searchManager.getMassIndexer().start()}} and the query will then return results.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6145) Reorganize cache store configuration
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-6145:
----------------------------------
Summary: Reorganize cache store configuration
Key: ISPN-6145
URL: https://issues.jboss.org/browse/ISPN-6145
Project: Infinispan
Issue Type: Enhancement
Components: Console
Reporter: Pedro Zapata
Cache stores should be placed under a 'Store' section, with a selector of the available store, plus a panel with the properties for each one.
All available cache stores should be selectable
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6144) Display error messsages to user
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-6144:
----------------------------------
Summary: Display error messsages to user
Key: ISPN-6144
URL: https://issues.jboss.org/browse/ISPN-6144
Project: Infinispan
Issue Type: Bug
Components: Console
Reporter: Pedro Zapata
Assignee: Tristan Tarrant
If you create an invalid configuration (i.e, set some random value in the site property), an exception is thrown in the log but it’s, not reported to the console.
No feedback about successful, or wrong creation is reported to the user, without looking into the server log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months