[jira] [Resolved] (IGNITE-2342) HadoopFileSystemFactory must set correct context ClassLoader before calling FileSystem.get()
[ https://issues.apache.org/jira/browse/IGNITE-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-2342. - Resolution: Fixed > HadoopFileSystemFactory must set correct context ClassLoader before calling > FileSystem.get() > > > Key: IGNITE-2342 > URL: https://issues.apache.org/jira/browse/IGNITE-2342 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Labels: important > Fix For: 1.6 > > > FileSystem.get() might delegate to ServiceLoader to get the list of file > system implementation. And ServiceLoader is known to be sensitive to context > classloader. > We must ensure that Thread.contextClassLoader is equal to > Factory.getClassLoader(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2342) HadoopFileSystemFactory must set correct context ClassLoader before calling FileSystem.get()
[ https://issues.apache.org/jira/browse/IGNITE-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-2342. --- > HadoopFileSystemFactory must set correct context ClassLoader before calling > FileSystem.get() > > > Key: IGNITE-2342 > URL: https://issues.apache.org/jira/browse/IGNITE-2342 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Labels: important > Fix For: 1.6 > > > FileSystem.get() might delegate to ServiceLoader to get the list of file > system implementation. And ServiceLoader is known to be sensitive to context > classloader. > We must ensure that Thread.contextClassLoader is equal to > Factory.getClassLoader(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2340) Throw sensible error from IgniteHadoopFileSystem if real file system is not IgniteHadoopIgfsSecondaryFileSystem
[ https://issues.apache.org/jira/browse/IGNITE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-2340. - Resolution: Fixed > Throw sensible error from IgniteHadoopFileSystem if real file system is not > IgniteHadoopIgfsSecondaryFileSystem > --- > > Key: IGNITE-2340 > URL: https://issues.apache.org/jira/browse/IGNITE-2340 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Labels: important > Fix For: 1.6 > > > Consider the following scenario: > 1) User configures some custom secondary file system; > 2) Some paths are set to PROXY mode (e.g. default modes); > 3) User instantiates IgniteHadoopFileSystem somewhere else. > Result: > IgniteHadoopFileSystem notices PROXY paths and tries to get FileSystem > factory from handshake request, but it is null. As a result, NPE is thrown a > moment later. > Proposed fix: > If factory is null. we must throw an exception and advise user to set > IgniteHadoopIgfsSecondaryFileSystem as secondary file system.in IGFS > configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2341) Improve warnings about BinaryMarshaller switched to "optimized" mode
[
https://issues.apache.org/jira/browse/IGNITE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-2341.
---
> Improve warnings about BinaryMarshaller switched to "optimized" mode
>
>
> Key: IGNITE-2341
> URL: https://issues.apache.org/jira/browse/IGNITE-2341
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Some classes implement Externalizable interface and hence cannot be written
> with binary marshaller. In this case a warning is printed:
> {code}
> Class "o.a.i.i.processors.hadoop.jobtracker.HadoopJobMetadata" cannot be
> written in binary format because it either implements Externalizable
> interface or have writeObject/readObject methods. Please ensure that all
> nodes have this class in classpath. To enable binary serialization either
> implement Binarylizable interface or set explicit serializer using
> BinaryTypeConfiguration.setSerializer() method.
> {code}
> 1) We need to make it more sensible: we must clearly note that these classes
> will be deserialized on the server.
> 2) These warnings should not be printed for "o.a.i" classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2340) Throw sensible error from IgniteHadoopFileSystem if real file system is not IgniteHadoopIgfsSecondaryFileSystem
[ https://issues.apache.org/jira/browse/IGNITE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-2340. --- > Throw sensible error from IgniteHadoopFileSystem if real file system is not > IgniteHadoopIgfsSecondaryFileSystem > --- > > Key: IGNITE-2340 > URL: https://issues.apache.org/jira/browse/IGNITE-2340 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Labels: important > Fix For: 1.6 > > > Consider the following scenario: > 1) User configures some custom secondary file system; > 2) Some paths are set to PROXY mode (e.g. default modes); > 3) User instantiates IgniteHadoopFileSystem somewhere else. > Result: > IgniteHadoopFileSystem notices PROXY paths and tries to get FileSystem > factory from handshake request, but it is null. As a result, NPE is thrown a > moment later. > Proposed fix: > If factory is null. we must throw an exception and advise user to set > IgniteHadoopIgfsSecondaryFileSystem as secondary file system.in IGFS > configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2341) Improve warnings about BinaryMarshaller switched to "optimized" mode
[
https://issues.apache.org/jira/browse/IGNITE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-2341.
-
Resolution: Fixed
> Improve warnings about BinaryMarshaller switched to "optimized" mode
>
>
> Key: IGNITE-2341
> URL: https://issues.apache.org/jira/browse/IGNITE-2341
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Some classes implement Externalizable interface and hence cannot be written
> with binary marshaller. In this case a warning is printed:
> {code}
> Class "o.a.i.i.processors.hadoop.jobtracker.HadoopJobMetadata" cannot be
> written in binary format because it either implements Externalizable
> interface or have writeObject/readObject methods. Please ensure that all
> nodes have this class in classpath. To enable binary serialization either
> implement Binarylizable interface or set explicit serializer using
> BinaryTypeConfiguration.setSerializer() method.
> {code}
> 1) We need to make it more sensible: we must clearly note that these classes
> will be deserialized on the server.
> 2) These warnings should not be printed for "o.a.i" classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088934#comment-15088934 ] Igor Rudyak commented on IGNITE-1371: - Alexey, I finished with items 4-5 and pushed everything into ignite-1371 branch. The only thing which wasn't refactored is the logic related to Serializers. I am not sure that fully understood your approach with Binary Marshaller. Are you suggesting just to use OptimizedMarshaller to serialize objects to BLOB? How about restrictions of Binary Marshaller (https://apacheignite.readme.io/docs/binary-marshaller)? How about forward and backward compatibility of Binary Marshaller serialization (which is for example supported by Kryo)? By the way, one of the useful features of Serializers approach - it could be used to secure sensitive data. Thus all the sensitive data from in-memory Ignite cache will be persisted into Cassandra in encrypted form. For this purpose you just need to implement your custom Serializer which implements data encryption/decryption. > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexandre Boudnik >Assignee: Igor Rudyak > Attachments: master_02b59e4_ignite-1371.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > It will provide ability to map particular cache holding POJOs to Cassandra > table. Later it would be generalized to support eventually any any Key-Value > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2202) Local server query result doesn't include versions in entries
[
https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088966#comment-15088966
]
Denis Magda commented on IGNITE-2202:
-
Implemented the logic discussed above for {{ScanQueries}}. Need to support the
rest of queries.
> Local server query result doesn't include versions in entries
> -
>
> Key: IGNITE-2202
> URL: https://issues.apache.org/jira/browse/IGNITE-2202
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Denis Magda
>Priority: Critical
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest2.java
>
>
> Cache entries returned as query results don't contain versions even if the
> query is local.
> Test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2343) IGFS: MapReduce task sent by Hunk/Splunk fails with NPE
Denis Magda created IGNITE-2343:
---
Summary: IGFS: MapReduce task sent by Hunk/Splunk fails with NPE
Key: IGNITE-2343
URL: https://issues.apache.org/jira/browse/IGNITE-2343
Project: Ignite
Issue Type: Bug
Components: IGFS
Affects Versions: ignite-1.4
Reporter: Denis Magda
Assignee: Vladimir Ozerov
Fix For: 1.6
A MR task being sent by Hunk [1] fails with NPE
{noformat}
[10:31:58,250][ERROR][Hadoop-task-fd3ff783-d952-4147-8e5b-8e3080b91ddb_1-MAP-50-
0-#271%null%][HadoopRunnableTask] Task execution failed.
class org.apache.ignite.IgniteCheckedException: class
org.apache.ignite.IgniteCh eckedException: null
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0(
HadoopV2MapTask.java:105)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2Task.run(Hado
opV2Task.java:54)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
un(HadoopV2TaskContext.java:249)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.runTask(HadoopRunnableTask.java:201)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.call0(HadoopRunnableTask.java:144)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask$1.call(HadoopRunnableTask.java:116)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask$1.call(HadoopRunnableTask.java:114)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1
.run(HadoopV2TaskContext.java:550)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma
tion.java:1657)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
unAsJobOwner(HadoopV2TaskContext.java:548)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.call(HadoopRunnableTask.java:114)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.call(HadoopRunnableTask.java:46)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu
torService$2.body(HadoopExecutorService.java:186)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at com.splunk.mr.SplunkSearchMapper.runImpl(SplunkSearchMapper.java:308)
at com.splunk.mr.SplunkBaseMapper.run(SplunkBaseMapper.java:169)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0(
HadoopV2MapTask.java:87)
... 16 more
at org.apache.ignite.internal.processors.hadoop.HadoopUtils.transformExc
eption(HadoopUtils.java:290)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
un(HadoopV2TaskContext.java:255)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.runTask(HadoopRunnableTask.java:201)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.call0(HadoopRunnableTask.java:144)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask$1.call(HadoopRunnableTask.java:116)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask$1.call(HadoopRunnableTask.java:114)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1
.run(HadoopV2TaskContext.java:550)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma
tion.java:1657)
at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
unAsJobOwner(HadoopV2TaskContext.java:548)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.call(HadoopRunnableTask.java:114)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
bleTask.call(HadoopRunnableTask.java:46)
at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu
torService$2.body(HadoopExecutorService.java:186)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
at java.lang.Thread.run(Thread.java:745)
{noformat}
[1] http://www.splunk.com/en_us/products/hunk.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2344) WebSessionFilter doesn't support session ID renewal
Denis Magda created IGNITE-2344:
---
Summary: WebSessionFilter doesn't support session ID renewal
Key: IGNITE-2344
URL: https://issues.apache.org/jira/browse/IGNITE-2344
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Denis Magda
It's quite a common scenario to update a session ID after a user successfully
logged in preserving the session content for further usage.
Ignite's {{WebSessionFilter}} doesn't support such a use case creating a
session from scratch.
To support this behavior we can store a special Cookie that will hold latest
session ID. When a session is passed to {{WebSessionFilter}} and the filter
detects that this is a fresh session it will check the Cookie in advance. If
the Cookie exists and holds an old session ID then the filter will be able to
get a session content from the cache using the old ID and put it back using the
new ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2344) WebSessionFilter doesn't support session ID renewal
[
https://issues.apache.org/jira/browse/IGNITE-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089193#comment-15089193
]
Denis Magda commented on IGNITE-2344:
-
The ticket was created as a result of this discussion
http://apache-ignite-users.70518.x6.nabble.com/Web-app-with-CMS-td2414.html
> WebSessionFilter doesn't support session ID renewal
> ---
>
> Key: IGNITE-2344
> URL: https://issues.apache.org/jira/browse/IGNITE-2344
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>
> It's quite a common scenario to update a session ID after a user successfully
> logged in preserving the session content for further usage.
> Ignite's {{WebSessionFilter}} doesn't support such a use case creating a
> session from scratch.
> To support this behavior we can store a special Cookie that will hold latest
> session ID. When a session is passed to {{WebSessionFilter}} and the filter
> detects that this is a fresh session it will check the Cookie in advance. If
> the Cookie exists and holds an old session ID then the filter will be able to
> get a session content from the cache using the old ID and put it back using
> the new ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2343) IGFS: MapReduce task sent by Hunk/Splunk fails with NPE
[
https://issues.apache.org/jira/browse/IGNITE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089205#comment-15089205
]
Denis Magda commented on IGNITE-2343:
-
One more important thing to pay attention to while this issue will be being
fixed.
If the node fails with the stack trace from the description it doesn't respond
any longer and the only way to stop it is to kill forcibly using 'kill -9'.
> IGFS: MapReduce task sent by Hunk/Splunk fails with NPE
> ---
>
> Key: IGNITE-2343
> URL: https://issues.apache.org/jira/browse/IGNITE-2343
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> A MR task being sent by Hunk [1] fails with NPE
> {noformat}
> [10:31:58,250][ERROR][Hadoop-task-fd3ff783-d952-4147-8e5b-8e3080b91ddb_1-MAP-50-
> 0-#271%null%][HadoopRunnableTask] Task execution failed.
> class org.apache.ignite.IgniteCheckedException: class
> org.apache.ignite.IgniteCh eckedException: null
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0(
> HadoopV2MapTask.java:105)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2Task.run(Hado
> opV2Task.java:54)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
> un(HadoopV2TaskContext.java:249)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.runTask(HadoopRunnableTask.java:201)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.call0(HadoopRunnableTask.java:144)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask$1.call(HadoopRunnableTask.java:116)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask$1.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1
> .run(HadoopV2TaskContext.java:550)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma
> tion.java:1657)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
> unAsJobOwner(HadoopV2TaskContext.java:548)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.call(HadoopRunnableTask.java:46)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu
> torService$2.body(HadoopExecutorService.java:186)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at com.splunk.mr.SplunkSearchMapper.runImpl(SplunkSearchMapper.java:308)
> at com.splunk.mr.SplunkBaseMapper.run(SplunkBaseMapper.java:169)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2MapTask.run0(
> HadoopV2MapTask.java:87)
> ... 16 more
> at org.apache.ignite.internal.processors.hadoop.HadoopUtils.transformExc
> eption(HadoopUtils.java:290)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
> un(HadoopV2TaskContext.java:255)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.runTask(HadoopRunnableTask.java:201)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.call0(HadoopRunnableTask.java:144)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask$1.call(HadoopRunnableTask.java:116)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask$1.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext$1
> .run(HadoopV2TaskContext.java:550)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInforma
> tion.java:1657)
> at org.apache.ignite.internal.processors.hadoop.v2.HadoopV2TaskContext.r
> unAsJobOwner(HadoopV2TaskContext.java:548)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.call(HadoopRunnableTask.java:114)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunna
> bleTask.call(HadoopRunnableTask.java:46)
> at org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecu
> torService$2.body(HadoopExecutorService.java:186)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java :110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> [1] http://www.splunk.com/en_us/products
[jira] [Commented] (IGNITE-944) HTTP REST log command doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089223#comment-15089223
]
Denis Magda commented on IGNITE-944:
Hi Saikat, sorry for the delay. We will review your contribution in the nearest
days.
> HTTP REST log command doesn't work
> --
>
> Key: IGNITE-944
> URL: https://issues.apache.org/jira/browse/IGNITE-944
> Project: Ignite
> Issue Type: Bug
> Components: general, newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>
> Request http://localhost:8080/ignite?cmd=log&to=1&from=0 returns following
> {noformat}
> {"error":"Failed to find registered handler for command:
> LOG","response":null,"sessionToken":"","successStatus":1}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089229#comment-15089229
]
Denis Magda commented on IGNITE-429:
Roman, thanks! Someone will review the changes the next week.
> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm
> and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9
[ https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089227#comment-15089227 ] Denis Magda commented on IGNITE-2016: - Roman, thanks! Sorry for the delay. I'll review the changes in the nearest days. > Update KafkaStreamer to fit new features introduced in Kafka 0.9 > > > Key: IGNITE-2016 > URL: https://issues.apache.org/jira/browse/IGNITE-2016 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh > > Particularly, > - new consumer > - Kafka Connect (Copycat) > http://www.confluent.io/blog/apache-kafka-0.9-is-released > This can be a a different integration task or a complete re-write of the > current implementation, considering the fact that Kafka Connect is a new > standard way for "large-scale, real-time data import and export for Kafka." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-255) Jvm8 warns that MaxPermSize is ignored
[
https://issues.apache.org/jira/browse/IGNITE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089232#comment-15089232
]
Denis Magda commented on IGNITE-255:
Saikat, thanks for taking care of this. Someone will review the changes the
next week.
> Jvm8 warns that MaxPermSize is ignored
> --
>
> Key: IGNITE-255
> URL: https://issues.apache.org/jira/browse/IGNITE-255
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-1
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>
> Jaba8 doesn't support MaxPermSize anymore. Either we should replace it in
> ignite.sh by a similar option of Java8 or set it only if ignite.sh started
> for Java7
> {noformat}
> D:\GridGain\Ignite-SP1\ignite-fabric-1.0.0-RC1-SNAPSHOT>bin\ignite.bat
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> [15:50:16]__
> [15:50:16] / _/ ___/ |/ / _/_ __/ __/
> [15:50:16] _/ // (_ /// / / / / _/
> [15:50:16] /___/\___/_/|_/___/ /_/ /___/
> [15:50:16]
> [15:50:16] ver. 1.0.0-RC1-SNAPSHOT#20150214-sha1:4d01989c
> [15:50:16] 2015 Copyright(C) Apache Software Foundation
> [15:50:16]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
