[jira] [Assigned] (IGNITE-15344) Reduce amount of output for printing node2part map

[Chandresh Pancholi (Jira)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-15344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-15344:
---

Assignee: Chandresh Pancholi

> Reduce amount of output for printing node2part map
> --
>
> Key: IGNITE-15344
> URL: https://issues.apache.org/jira/browse/IGNITE-15344
> Project: Ignite
>  Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Chandresh Pancholi
>Priority: Major
>  Labels: newbie
>
> _Current output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0, 
> nodeOrder=1, updateSeq=3, size=2, 
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0, 
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100, 
> map={0=OWNING, 1=OWNING, 2=OWNING, 3=OWNING, 4=OWNING, 5=OWNING, 6=OWNING, 
> 7=OWNING, 8=OWNING, 9=OWNING, 10=OWNING, 11=OWNING, 12=OWNING, 13=OWNING, 
> 14=OWNING, 15=OWNING, 16=OWNING, 17=OWNING, 18=OWNING, 19=OWNING, 20=OWNING, 
> 21=OWNING, 22=OWNING, 23=OWNING, 24=OWNING, 25=OWNING, 26=OWNING, 27=OWNING, 
> 28=OWNING, 29=OWNING, 30=OWNING, 31=OWNING, 32=OWNING, 33=OWNING, 34=OWNING, 
> 35=OWNING, 36=OWNING, 37=OWNING, 38=OWNING, 39=OWNING, 40=OWNING, 41=OWNING, 
> 42=OWNING, 43=OWNING, 44=OWNING, 45=OWNING, 46=OWNING, 47=OWNING, 48=OWNING, 
> 49=OWNING, 50=OWNING, 51=OWNING, 52=OWNING, 53=OWNING, 54=OWNING, 55=OWNING, 
> 56=OWNING, 57=OWNING, 58=OWNING, 59=OWNING, 60=OWNING, 61=OWNING, 62=OWNING, 
> 63=OWNING, 64=OWNING, 65=OWNING, 66=OWNING, 67=OWNING, 68=OWNING, 69=OWNING, 
> 70=OWNING, 71=OWNING, 72=OWNING, 73=OWNING, 74=OWNING, 75=OWNING, 76=OWNING, 
> 77=OWNING, 78=OWNING, 79=OWNING, 80=OWNING, 81=OWNING, 82=OWNING, 83=OWNING, 
> 84=OWNING, 85=OWNING, 86=OWNING, 87=OWNING, 88=OWNING, 89=OWNING, 90=OWNING, 
> 91=OWNING, 92=OWNING, 93=OWNING, 94=OWNING, 95=OWNING, 96=OWNING, 97=OWNING, 
> 98=OWNING, 99=OWNING}],
> {code}
> _Proposed output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0, 
> nodeOrder=1, updateSeq=3, size=2, 
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0, 
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100, 
> map={OWNING=0-100}],
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-15344) Reduce amount of output for printing node2part map

[Chandresh Pancholi (Jira)]

[ 
https://issues.apache.org/jira/browse/IGNITE-15344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411915#comment-17411915
 ] 

Chandresh Pancholi commented on IGNITE-15344:
-

[~mmuzaf] I was going through the code for first contribution. nodeId is a UUID 
and shown here is an integer. is this the right format?

> Reduce amount of output for printing node2part map
> --
>
> Key: IGNITE-15344
> URL: https://issues.apache.org/jira/browse/IGNITE-15344
> Project: Ignite
>  Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: newbie
>
> _Current output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0, 
> nodeOrder=1, updateSeq=3, size=2, 
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0, 
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100, 
> map={0=OWNING, 1=OWNING, 2=OWNING, 3=OWNING, 4=OWNING, 5=OWNING, 6=OWNING, 
> 7=OWNING, 8=OWNING, 9=OWNING, 10=OWNING, 11=OWNING, 12=OWNING, 13=OWNING, 
> 14=OWNING, 15=OWNING, 16=OWNING, 17=OWNING, 18=OWNING, 19=OWNING, 20=OWNING, 
> 21=OWNING, 22=OWNING, 23=OWNING, 24=OWNING, 25=OWNING, 26=OWNING, 27=OWNING, 
> 28=OWNING, 29=OWNING, 30=OWNING, 31=OWNING, 32=OWNING, 33=OWNING, 34=OWNING, 
> 35=OWNING, 36=OWNING, 37=OWNING, 38=OWNING, 39=OWNING, 40=OWNING, 41=OWNING, 
> 42=OWNING, 43=OWNING, 44=OWNING, 45=OWNING, 46=OWNING, 47=OWNING, 48=OWNING, 
> 49=OWNING, 50=OWNING, 51=OWNING, 52=OWNING, 53=OWNING, 54=OWNING, 55=OWNING, 
> 56=OWNING, 57=OWNING, 58=OWNING, 59=OWNING, 60=OWNING, 61=OWNING, 62=OWNING, 
> 63=OWNING, 64=OWNING, 65=OWNING, 66=OWNING, 67=OWNING, 68=OWNING, 69=OWNING, 
> 70=OWNING, 71=OWNING, 72=OWNING, 73=OWNING, 74=OWNING, 75=OWNING, 76=OWNING, 
> 77=OWNING, 78=OWNING, 79=OWNING, 80=OWNING, 81=OWNING, 82=OWNING, 83=OWNING, 
> 84=OWNING, 85=OWNING, 86=OWNING, 87=OWNING, 88=OWNING, 89=OWNING, 90=OWNING, 
> 91=OWNING, 92=OWNING, 93=OWNING, 94=OWNING, 95=OWNING, 96=OWNING, 97=OWNING, 
> 98=OWNING, 99=OWNING}],
> {code}
> _Proposed output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0, 
> nodeOrder=1, updateSeq=3, size=2, 
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0, 
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100, 
> map={OWNING=0-100}],
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-8777) REST: metadata command failed on cluster of size 1.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511294#comment-16511294
 ] 

Chandresh Pancholi commented on IGNITE-8777:


[~kuaw26] Could you please help me out with the unit test? 

> REST: metadata command failed on cluster of size 1.
> ---
>
> Key: IGNITE-8777
> URL: https://issues.apache.org/jira/browse/IGNITE-8777
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.5
>Reporter: Alexey Kuznetsov
>Assignee: Chandresh Pancholi
>Priority: Major
>  Labels: newbie
>
> Start *only one *node.
> Execute REST command: 
> http://localhost:8080/ignite?cmd=getorcreate=myNewPartionedCache=2
> Cache will be created.
> Execute 
> http://localhost:8080/ignite?cmd=metadata=myNewPartionedCache
> Error will be returned:  {“successStatus”:1,“error”:“Failed to handle 
> request: [req=CACHE_METADATA, err=Failed to request meta data. 
> myNewPartionedCache is not found]“,”response”:null,“sessionToken”:null}
> After some debug, I see in code GridCacheCommandHandler.MetadataTask#map:
> {code}
> ...
> for (int i = 1; i < subgrid.size(); i++) {
>  
> }
> if (map.isEmpty())
> throw new IgniteException("Failed to request meta data. " 
> + cacheName + " is not found");
> ...
> {code}
> So, in case of cluster with only one node this code will throw exception.
> I guess the fix should be - just replace "int i = 1" with "int i = 0".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7752) Update Ignite KafkaStreamer to use new KafkaConsmer configuration.

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-7752:
--

Assignee: Chandresh Pancholi

> Update Ignite KafkaStreamer to use new KafkaConsmer configuration.
> --
>
> Key: IGNITE-7752
> URL: https://issues.apache.org/jira/browse/IGNITE-7752
> Project: Ignite
>  Issue Type: Task
>  Components: streaming
>Reporter: Andrew Mashenkov
>Assignee: Chandresh Pancholi
>Priority: Major
>  Labels: newbie
> Fix For: 2.6
>
>
> Seems, for now it is impossible to use new style KafkaConsumer configuration 
> in KafkaStreamer.
> The issue here is Ignite use 
> kafka.consumer.Consumer.createJavaConsumerConnector() method which creates 
> old consumer (ZookeeperConsumerConnector).
> We should create a new KafkaConsumer instead which looks like support both, 
> old and new style configs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8641) SpringDataExample should use example-ignite.xml config

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-8641:
--

Assignee: Chandresh Pancholi

> SpringDataExample should use example-ignite.xml config
> --
>
> Key: IGNITE-8641
> URL: https://issues.apache.org/jira/browse/IGNITE-8641
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Chandresh Pancholi
>Priority: Major
>  Labels: newbie
> Fix For: 2.6
>
>
> {{SpringDataExample}} uses 
> {{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring 
> configuration while all other examples use {{example-ignite.xml}} 
> configuration file.
> It leads to inconsistent examples behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8777) REST: metadata command failed on cluster of size 1.

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-8777:
--

Assignee: Chandresh Pancholi

> REST: metadata command failed on cluster of size 1.
> ---
>
> Key: IGNITE-8777
> URL: https://issues.apache.org/jira/browse/IGNITE-8777
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.5
>Reporter: Alexey Kuznetsov
>Assignee: Chandresh Pancholi
>Priority: Major
>  Labels: newbie
>
> Start *only one *node.
> Execute REST command: 
> http://localhost:8080/ignite?cmd=getorcreate=myNewPartionedCache=2
> Cache will be created.
> Execute 
> http://localhost:8080/ignite?cmd=metadata=myNewPartionedCache
> Error will be returned:  {“successStatus”:1,“error”:“Failed to handle 
> request: [req=CACHE_METADATA, err=Failed to request meta data. 
> myNewPartionedCache is not found]“,”response”:null,“sessionToken”:null}
> After some debug, I see in code GridCacheCommandHandler.MetadataTask#map:
> {code}
> ...
> for (int i = 1; i < subgrid.size(); i++) {
>  
> }
> if (map.isEmpty())
> throw new IgniteException("Failed to request meta data. " 
> + cacheName + " is not found");
> ...
> {code}
> So, in case of cluster with only one node this code will throw exception.
> I guess the fix should be - just replace "int i = 1" with "int i = 0".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-533) Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi updated IGNITE-533:
--
Assignee: Maksim Kozlov  (was: Chandresh Pancholi)

> Implement IgniteZeromqStreamer to stream data from ZeroMQ
> -
>
> Key: IGNITE-533
> URL: https://issues.apache.org/jira/browse/IGNITE-533
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Maksim Kozlov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [ZeroMQ|http://zeromq.org/] for more info.
> We should create {{IgniteZeroMqStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert ZeroMQ messages to Ignite data using an optional pluggable 
> converter. If not provided, we should have some default mechanism.
> * 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-533) Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831725#comment-15831725
 ] 

Chandresh Pancholi commented on IGNITE-533:
---

[~dreamx] Go ahead. 

> Implement IgniteZeromqStreamer to stream data from ZeroMQ
> -
>
> Key: IGNITE-533
> URL: https://issues.apache.org/jira/browse/IGNITE-533
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [ZeroMQ|http://zeromq.org/] for more info.
> We should create {{IgniteZeroMqStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert ZeroMQ messages to Ignite data using an optional pluggable 
> converter. If not provided, we should have some default mechanism.
> * 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] [Issue Comment Deleted] (IGNITE-2837) Docker daemon doesn't start on the AWS instances

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi updated IGNITE-2837:
---
Comment: was deleted

(was: [~vsidorova] Could you please share the link of "Amazon EC2 Deployment" 
instruction?)

> Docker daemon doesn't start on the AWS instances
> 
>
> Key: IGNITE-2837
> URL: https://issues.apache.org/jira/browse/IGNITE-2837
> Project: Ignite
>  Issue Type: Bug
>  Components: aws
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa  Sidorova
> Attachments: gcloud_ignitedocker_step6.png, ignite_aws_docker.png
>
>
> -
> DESCRIPTION
> -
> Deployment docker onto Amazon EC2 by this 
> https://apacheignite.readme.io/docs/docker-deployment instruction is failed
> -
> STEPS FOR REPRODUCE
> -
> Do items 1-7 from "Amazon EC2 Deployement" instruction
> Do item 8
> -
> ACTUAL RESULT
> -
> The list of containers is empty. And command "sudo ./startup.sh" get result:
> {noformat}
> --2016-03-15 16:51:56--  http://169.254.169.254/latest/user-data
> Connecting to 169.254.169.254:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 41 [application/octet-stream]
> Saving to: ‘user-data’
> user-data   
> 100%[===>]
>   41  --.-KB/s   in 0s 
> 2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
> 1.5.0.final: Pulling from apacheignite/ignite
> 77e39ee82117: Already exists 
> 5eb1402f0414: Already exists 
> 9287fae7a16e: Already exists 
> 0288ae931294: Already exists 
> e5faec61f132: Already exists 
> 9e9bea63cb40: Already exists 
> dcb718404a8b: Already exists 
> a8ce4138c3d9: Already exists 
> 7c01b1c179c8: Already exists 
> a41c2ba526d9: Already exists 
> 5108e60af9fc: Already exists 
> 171a6bf29457: Already exists 
> 1e2a752083e5: Already exists 
> 6dc3a9ded560: Already exists 
> 5d9df50a72b0: Already exists 
> e3dee37923c1: Already exists 
> c7d92bcdbf90: Already exists 
> 8de8b8b056fa: Already exists 
> b298c64b2b41: Already exists 
> 8185ba03f727: Already exists 
> Digest: 
> sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
> Status: Image is up to date for apacheignite/ignite:1.5.0.final
> 84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
> {noformat}
> -
> EXPECTED RESULT
> -
> Docker daemon and Ignite nodes should be started on all running amazon 
> instances
> -
> ADDITIONAL INFO
> -
> Reproducible for all Amazon regions (west, east, central)
> For reproducing you can use instances with name ignite-docker-image in any 
> region



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2837) Docker daemon doesn't start on the AWS instances

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15800543#comment-15800543
 ] 

Chandresh Pancholi commented on IGNITE-2837:


[~vsidorova] Could you please share the link of "Amazon EC2 Deployment" 
instruction?

> Docker daemon doesn't start on the AWS instances
> 
>
> Key: IGNITE-2837
> URL: https://issues.apache.org/jira/browse/IGNITE-2837
> Project: Ignite
>  Issue Type: Bug
>  Components: aws
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa  Sidorova
> Attachments: gcloud_ignitedocker_step6.png, ignite_aws_docker.png
>
>
> -
> DESCRIPTION
> -
> Deployment docker onto Amazon EC2 by this 
> https://apacheignite.readme.io/docs/docker-deployment instruction is failed
> -
> STEPS FOR REPRODUCE
> -
> Do items 1-7 from "Amazon EC2 Deployement" instruction
> Do item 8
> -
> ACTUAL RESULT
> -
> The list of containers is empty. And command "sudo ./startup.sh" get result:
> {noformat}
> --2016-03-15 16:51:56--  http://169.254.169.254/latest/user-data
> Connecting to 169.254.169.254:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 41 [application/octet-stream]
> Saving to: ‘user-data’
> user-data   
> 100%[===>]
>   41  --.-KB/s   in 0s 
> 2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
> 1.5.0.final: Pulling from apacheignite/ignite
> 77e39ee82117: Already exists 
> 5eb1402f0414: Already exists 
> 9287fae7a16e: Already exists 
> 0288ae931294: Already exists 
> e5faec61f132: Already exists 
> 9e9bea63cb40: Already exists 
> dcb718404a8b: Already exists 
> a8ce4138c3d9: Already exists 
> 7c01b1c179c8: Already exists 
> a41c2ba526d9: Already exists 
> 5108e60af9fc: Already exists 
> 171a6bf29457: Already exists 
> 1e2a752083e5: Already exists 
> 6dc3a9ded560: Already exists 
> 5d9df50a72b0: Already exists 
> e3dee37923c1: Already exists 
> c7d92bcdbf90: Already exists 
> 8de8b8b056fa: Already exists 
> b298c64b2b41: Already exists 
> 8185ba03f727: Already exists 
> Digest: 
> sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
> Status: Image is up to date for apacheignite/ignite:1.5.0.final
> 84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
> {noformat}
> -
> EXPECTED RESULT
> -
> Docker daemon and Ignite nodes should be started on all running amazon 
> instances
> -
> ADDITIONAL INFO
> -
> Reproducible for all Amazon regions (west, east, central)
> For reproducing you can use instances with name ignite-docker-image in any 
> region



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4519) Update AWS, GCE and JCloud IP finders libs

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799570#comment-15799570
 ] 

Chandresh Pancholi commented on IGNITE-4519:


AWS and Jcloud tests are passing on Teamcity but GCE are failing due to 
authentication.
http://ci.ignite.apache.org/viewLog.html?buildId=409918;

> Update AWS, GCE and JCloud IP finders libs
> --
>
> Key: IGNITE-4519
> URL: https://issues.apache.org/jira/browse/IGNITE-4519
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Chandresh Pancholi
>
> There are special IP finders that are created for cloud environments. They 
> all located in dedicated modules and depend on 3rd party libs.
> - ignite-aws
> - ignite-gce
> - ignite-cloud 
> These 3rd party libs has to be updated to the latest one. As a part of this 
> activity the one has to make sure that all the tests pass as usual after the 
> update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4519) Update AWS, GCE and JCloud IP finders libs

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15798203#comment-15798203
 ] 

Chandresh Pancholi commented on IGNITE-4519:


It would be great if you suggest the way to test GCE and Cloud because they are 
asking for account Ids and i don't have accounts for GCE.

> Update AWS, GCE and JCloud IP finders libs
> --
>
> Key: IGNITE-4519
> URL: https://issues.apache.org/jira/browse/IGNITE-4519
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Chandresh Pancholi
>
> There are special IP finders that are created for cloud environments. They 
> all located in dedicated modules and depend on 3rd party libs.
> - ignite-aws
> - ignite-gce
> - ignite-cloud 
> These 3rd party libs has to be updated to the latest one. As a part of this 
> activity the one has to make sure that all the tests pass as usual after the 
> update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4519) Update AWS, GCE and JCloud IP finders libs

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-4519:
--

Assignee: Chandresh Pancholi

> Update AWS, GCE and JCloud IP finders libs
> --
>
> Key: IGNITE-4519
> URL: https://issues.apache.org/jira/browse/IGNITE-4519
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Chandresh Pancholi
>
> There are special IP finders that are created for cloud environments. They 
> all located in dedicated modules and depend on 3rd party libs.
> - ignite-aws
> - ignite-gce
> - ignite-cloud 
> These 3rd party libs has to be updated to the latest one. As a part of this 
> activity the one has to make sure that all the tests pass as usual after the 
> update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484146#comment-15484146
 ] 

Chandresh Pancholi commented on IGNITE-532:
---

[~sboikov] I will make necessary change and update the PR.


> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala 
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka 
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If 
> not provided, then we should have some default mechanism.
> * 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] [Assigned] (IGNITE-3579) Message type should be short.

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-3579:
--

Assignee: Chandresh Pancholi

> Message type should be short.
> -
>
> Key: IGNITE-3579
> URL: https://issues.apache.org/jira/browse/IGNITE-3579
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Chandresh Pancholi
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Currently we encode internal messages with {{byte}}. It turns out that we 
> almost exhausted possible IDs. 
> We should change {{byte}} to {{short}} for message ID.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-3579) Message type should be short.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474017#comment-15474017
 ] 

Chandresh Pancholi edited comment on IGNITE-3579 at 9/8/16 2:34 PM:


[~vozerov] Please provide starting point for this task so that i can pick it up 
ASAP.


was (Author: chandresh pancholi):
Please provide starting point for this task so that i can pick it up ASAP.

> Message type should be short.
> -
>
> Key: IGNITE-3579
> URL: https://issues.apache.org/jira/browse/IGNITE-3579
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Chandresh Pancholi
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Currently we encode internal messages with {{byte}}. It turns out that we 
> almost exhausted possible IDs. 
> We should change {{byte}} to {{short}} for message ID.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3579) Message type should be short.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474017#comment-15474017
 ] 

Chandresh Pancholi commented on IGNITE-3579:


Please provide starting point for this task so that i can pick it up ASAP.

> Message type should be short.
> -
>
> Key: IGNITE-3579
> URL: https://issues.apache.org/jira/browse/IGNITE-3579
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Currently we encode internal messages with {{byte}}. It turns out that we 
> almost exhausted possible IDs. 
> We should change {{byte}} to {{short}} for message ID.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-949) Add Python API for Ignite RDD

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi updated IGNITE-949:
--
Assignee: (was: Chandresh Pancholi)

> Add Python API for Ignite RDD
> -
>
> Key: IGNITE-949
> URL: https://issues.apache.org/jira/browse/IGNITE-949
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>
> Should be close to the Java version:
> https://apacheignite.readme.io/docs/ignitecontext--igniterdd



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-2377) Docker image hangs on Mac OS

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473987#comment-15473987
 ] 

Chandresh Pancholi edited comment on IGNITE-2377 at 9/8/16 2:23 PM:


I have tested with Ignite latest master (1.7.1) and docker Version 1.12.0-a 
(build: 11213) and it works fine and its not hanging anywhere. I followed steps 
given on ignite docker page and in description of stackoverflow question.
1. sudo docker pull apacheignite/ignite-docker
2.docker run --expose=4700-4800 -it -p 47500-47600:47500-47600 -p 
47100-47200:47100-47200 --net=host -e 
"CONFIG_URI=https://raw.githubusercontent.com/apache/ignite/master/examples/config/example-default.xml;
 apacheignite/ignite-docker

Log output
inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.Examples/Properties/AssemblyInfo.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.Examples/Services/IMapService.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.Examples/Services/ServicesExample.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Apache.Ignite.ExamplesDll.csproj
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Apache.Ignite.ExamplesDll.snk
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Account.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Address.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Employee.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/EmployeeKey.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Organization.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/OrganizationType.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/AverageSalaryJob.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/AverageSalaryTask.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/CharacterCountClosure.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/CharacterCountReducer.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/ContinuousQueryFilter.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/EmployeeStore.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/EmployeeStoreFactory.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/EmployeeStorePredicate.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Events/LocalListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/LocalListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/RemoteOrderedListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/RemoteUnorderedListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/Topic.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Properties/AssemblyInfo.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Services/MapService.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/README.txt  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/licenses/apache-2.0.txt
  
ignite/gridgain-professional-fabric-1.7.1/bin/ignite.sh, WARN: Failed to 
resolve JMX host (JMX will be disabled): moby
[14:10:38]__   
[14:10:38]   /  _/ ___/ |/ /  _/_  __/ __/ 
[14:10:38]  _/ // (7 7// /  / / / _/   
[14:10:38] /___/\___/_/|_/___/ /_/ /___/  

[jira] [Assigned] (IGNITE-2377) Docker image hangs on Mac OS

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-2377:
--

Assignee: Chandresh Pancholi

> Docker image hangs on Mac OS
> 
>
> Key: IGNITE-2377
> URL: https://issues.apache.org/jira/browse/IGNITE-2377
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Chandresh Pancholi
>  Labels: newbie
> Fix For: 1.8
>
>
> Docker hangs at the point when {{CommandLineRandomNumberGenerator}} is being 
> executed. The reason is that the current and previous Docker version has some 
> bug that can be overcame if to put {{System.exit(0)}} at the end of 
> {{main(...)}} function.
> More investigation details and steps to reproduce can be found here:
> http://stackoverflow.com/questions/34661934/ignite-running-in-docker-is-general-java-docker-issue
> It makes sense to add {{System.exit(0)}} to all our classes that are executed 
> by {{ignite.bat}} or {{ignite.sh}} because it's not harmful in any case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2377) Docker image hangs on Mac OS

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473987#comment-15473987
 ] 

Chandresh Pancholi commented on IGNITE-2377:


I have tested with Ignite latest master (1.8) and docker Version 1.12.0-a 
(build: 11213) and it works fine and its not hanging anywhere. I followed steps 
given on ignite docker page and in description of stackoverflow question.
1. sudo docker pull apacheignite/ignite-docker
2.docker run --expose=4700-4800 -it -p 47500-47600:47500-47600 -p 
47100-47200:47100-47200 --net=host -e 
"CONFIG_URI=https://raw.githubusercontent.com/apache/ignite/master/examples/config/example-default.xml;
 apacheignite/ignite-docker

Log output
inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.Examples/Properties/AssemblyInfo.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.Examples/Services/IMapService.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.Examples/Services/ServicesExample.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Apache.Ignite.ExamplesDll.csproj
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Apache.Ignite.ExamplesDll.snk
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Account.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Address.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Employee.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/EmployeeKey.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/Organization.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Binary/OrganizationType.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/AverageSalaryJob.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/AverageSalaryTask.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/CharacterCountClosure.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Compute/CharacterCountReducer.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/ContinuousQueryFilter.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/EmployeeStore.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/EmployeeStoreFactory.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Datagrid/EmployeeStorePredicate.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Events/LocalListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/LocalListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/RemoteOrderedListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/RemoteUnorderedListener.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Messaging/Topic.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Properties/AssemblyInfo.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Services/MapService.cs
  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/examples/README.txt  
  inflating: 
ignite/gridgain-professional-fabric-1.7.1/platforms/dotnet/licenses/apache-2.0.txt
  
ignite/gridgain-professional-fabric-1.7.1/bin/ignite.sh, WARN: Failed to 
resolve JMX host (JMX will be disabled): moby
[14:10:38]__   
[14:10:38]   /  _/ ___/ |/ /  _/_  __/ __/ 
[14:10:38]  _/ // (7 7// /  / / / _/   
[14:10:38] /___/\___/_/|_/___/ /_/ /___/  
[14:10:38] 
[14:10:38] ver. 

[jira] [Assigned] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-3176:
--

Assignee: Chandresh Pancholi

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.8
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472976#comment-15472976
 ] 

Chandresh Pancholi commented on IGNITE-3176:


I tried reproducing the issue. Below are the steps
1. Run bin/benchmark-run-all.sh config/benchmark.properties in one terminal 
with 2 server hosts
2.Run bin/benchmark-run-all.sh config/benchmark.properties in another terminal 
with 2 server hosts

I have got 4 diff GC log file.

Let me know incase i missed any steps to reproduce it.


> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3812) Add executors configuration validation.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470465#comment-15470465
 ] 

Chandresh Pancholi commented on IGNITE-3812:


Please provide Test class name to reproduce it.

> Add executors configuration validation.
> ---
>
> Key: IGNITE-3812
> URL: https://issues.apache.org/jira/browse/IGNITE-3812
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.6
>Reporter: Andrew Mashenkov
>
> An IllegalArgumentException will be thrown from one of java standard 
> implementation of ThreadPool without any information about wrong parameter  
> if incorrect value provided (e.g. if set  threadPoolSize <= 0). So, it is not 
> obvious which executor service initialization has failed.
> See IgnitionEx.IgniteNamedInstance class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466849#comment-15466849
 ] 

Chandresh Pancholi commented on IGNITE-532:
---

Thank you Semen.

> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala 
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka 
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If 
> not provided, then we should have some default mechanism.
> * 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] [Assigned] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-532:
-

Assignee: Chandresh Pancholi  (was: Joshua Goldie)

> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala 
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka 
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If 
> not provided, then we should have some default mechanism.
> * 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-532) Implement IgniteAkkaStreamer to stream data from Akka actors.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298716#comment-15298716
 ] 

Chandresh Pancholi commented on IGNITE-532:
---

I have started working on it. I will update once it done.

> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Joshua Goldie
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala 
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka 
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If 
> not provided, then we should have some default mechanism.
> * 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] [Assigned] (IGNITE-2323) Improvments for http client

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-2323:
--

Assignee: Chandresh Pancholi

> Improvments for http client
> ---
>
> Key: IGNITE-2323
> URL: https://issues.apache.org/jira/browse/IGNITE-2323
> Project: Ignite
>  Issue Type: Sub-task
>  Components: clients
>Reporter: Semen Boikov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.7
>
>
> Need to fix following issues in http code used in nodejs client:
> - request timeout is hardcoded, need to make it configurable
> - need to handle session token which can be returned by ignite
> - X-Signature is calculated for each, probably can do it only once



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1650) Add ability to specify thread pool for IgniteFuture listen/chain methods.

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-1650:
--

Assignee: Chandresh Pancholi

> Add ability to specify thread pool for IgniteFuture listen/chain methods.
> -
>
> Key: IGNITE-1650
> URL: https://issues.apache.org/jira/browse/IGNITE-1650
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.6
>
>
> Closures passed to IgniteFuture listen() and chain() methods are executed 
> either in the same thread if future is completed, or in a completion thread 
> (usually this is a thread from one of Ignite pools).
> This enforces restrictions on what user can do in closures. He cannot use 
> call operations, he cannot call any Ignite operations. Otherwise deadlocks or 
> starvation could occur.
> To fix that we should allow user to pass optional thread pool where passed 
> closure should be executed. This already done in Java 8 CompletableFuture. We 
> should do almost the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1650) Add ability to specify thread pool for IgniteFuture listen/chain methods.

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249821#comment-15249821
 ] 

Chandresh Pancholi commented on IGNITE-1650:


[~vozerov] How can i reproduce it? or from where i can better understand it?



> Add ability to specify thread pool for IgniteFuture listen/chain methods.
> -
>
> Key: IGNITE-1650
> URL: https://issues.apache.org/jira/browse/IGNITE-1650
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> Closures passed to IgniteFuture listen() and chain() methods are executed 
> either in the same thread if future is completed, or in a completion thread 
> (usually this is a thread from one of Ignite pools).
> This enforces restrictions on what user can do in closures. He cannot use 
> call operations, he cannot call any Ignite operations. Otherwise deadlocks or 
> starvation could occur.
> To fix that we should allow user to pass optional thread pool where passed 
> closure should be executed. This already done in Java 8 CompletableFuture. We 
> should do almost the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-533) Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249635#comment-15249635
 ] 

Chandresh Pancholi commented on IGNITE-533:
---

Won't be any licensing problem?
If not then i will implement Pub-Sub with zeromq and put data into ignite cache.

[~dsetrakyan] What do you think?


> Implement IgniteZeromqStreamer to stream data from ZeroMQ
> -
>
> Key: IGNITE-533
> URL: https://issues.apache.org/jira/browse/IGNITE-533
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [ZeroMQ|http://zeromq.org/] for more info.
> We should create {{IgniteZeroMqStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert ZeroMQ messages to Ignite data using an optional pluggable 
> converter. If not provided, we should have some default mechanism.
> * 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-949) Add Python API for Ignite RDD

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074896#comment-15074896
 ] 

Chandresh Pancholi commented on IGNITE-949:
---

Yes!!

> Add Python API for Ignite RDD
> -
>
> Key: IGNITE-949
> URL: https://issues.apache.org/jira/browse/IGNITE-949
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>
> Should be close to the Java version:
> https://apacheignite.readme.io/docs/ignitecontext--igniterdd



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-949) Add Python API for Ignite RDD

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-949:
-

Assignee: Chandresh Pancholi

> Add Python API for Ignite RDD
> -
>
> Key: IGNITE-949
> URL: https://issues.apache.org/jira/browse/IGNITE-949
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Chandresh Pancholi
>
> Should be close to the Java version:
> https://apacheignite.readme.io/docs/ignitecontext--igniterdd



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-944) HTTP REST log command doesn't work

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071655#comment-15071655
 ] 

Chandresh Pancholi commented on IGNITE-944:
---

Sure Saikat.
Go ahead.

> 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: Chandresh Pancholi
>
> Request http://localhost:8080/ignite?cmd=log=1=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

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14997289#comment-14997289
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Before that can you check whats the mistake am i making with ignite node that i 
am starting?
One node i am starting in beforetest and another one is in StormStreamer class.

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995609#comment-14995609
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Anton,
Here is the request https://github.com/apache/ignite/pull/138



> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991467#comment-14991467
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Thanks Anton.
I have been facing issue with another node creation.
Will send pull request .

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14962908#comment-14962908
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Everytime i run tests i get Test timed out (5000ms) (not (every? (memfn 
waiting?) daemons)).

I tried with possible timeouts form 5 sec to 50 sec. :( 

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14962957#comment-14962957
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Gian,
Where to put this change  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: Chandresh Pancholi
>
> 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] [Comment Edited] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14962957#comment-14962957
 ] 

Chandresh Pancholi edited comment on IGNITE-429 at 10/19/15 7:25 AM:
-

Gian,
Where to put this change  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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14963189#comment-14963189
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Gian,
I made changes in config/default-config.xml . i am still getting same 
exception. can you please check where am i making mistake?
I have pushed the code in my 
branch(https://github.com/chandresh-pancholi/ignite)

> 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: Chandresh Pancholi
>
> 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] [Comment Edited] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14962957#comment-14962957
 ] 

Chandresh Pancholi edited comment on IGNITE-429 at 10/19/15 9:44 AM:
-

Gian,
Where to put this change  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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14963955#comment-14963955
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Hey Gian, i am using same config to start another node.
Here is the stack trace
org.apache.ignite.IgniteException: Default grid instance has already been 
started.
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:880)
 ~[classes/:na]
at org.apache.ignite.Ignition.start(Ignition.java:349) ~[classes/:na]
at 
org.apache.ignite.stream.storm.StormStreamer.prepare(StormStreamer.java:155) 
~[classes/:na]
at 
backtype.storm.daemon.executor$fn__3439$fn__3451.invoke(executor.clj:692) 
~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.util$async_loop$fn__460.invoke(util.clj:461) 
~[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]
Caused by: org.apache.ignite.IgniteCheckedException: Default grid instance has 
already been started.
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:952) 
~[classes/:na]
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546) 
~[classes/:na]
at org.apache.ignite.Ignition.start(Ignition.java:346) ~[classes/:na]
... 5 common frames omitted
29332 [Thread-11-bolt] ERROR backtype.storm.daemon.executor - 
org.apache.ignite.IgniteException: Default grid instance has already been 
started.
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:880)
 ~[classes/:na]
at org.apache.ignite.Ignition.start(Ignition.java:349) ~[classes/:na]
at 
org.apache.ignite.stream.storm.StormStreamer.prepare(StormStreamer.java:155) 
~[classes/:na]
at 
backtype.storm.daemon.executor$fn__3439$fn__3451.invoke(executor.clj:692) 
~[storm-core-0.9.5.jar:0.9.5]
at backtype.storm.util$async_loop$fn__460.invoke(util.clj:461) 
~[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]
Caused by: org.apache.ignite.IgniteCheckedException: Default grid instance has 
already been started.
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:952) 
~[classes/:na]
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576) 
~[classes/:na]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546) 
~[classes/:na]
at org.apache.ignite.Ignition.start(Ignition.java:346) ~[classes/:na]
... 5 common frames omitted
29351 [Thread-11-bolt] ERROR backtype.storm.util - Halting process: ("Worker 
died")
java.lang.RuntimeException: ("Worker died")
at backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325) 
[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.RestFn.invoke(RestFn.java:423) [clojure-1.5.1.jar:na]
at 
backtype.storm.daemon.worker$fn__4694$fn__4695.invoke(worker.clj:493) 
[storm-core-0.9.5.jar:0.9.5]
at 
backtype.storm.daemon.executor$mk_executor_data$fn__3272$fn__3273.invoke(executor.clj:240)
 [storm-core-0.9.5.jar:0.9.5]
at backtype.storm.util$async_loop$fn__460.invoke(util.clj:473) 
[storm-core-0.9.5.jar:0.9.5]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]
[23:51:33,482][INFO ][Thread-2][G] Invoking shutdown hook...
[23:51:33,483][INFO ][Thread-1][G] Invoking shutdown hook...
[23:51:33,495][INFO ][Thread-2][GridTcpRestProtocol] Command protocol 
successfully stopped: TCP binary
[23:51:33,578][INFO ][Thread-2][GridCacheProcessor] Stopped cache: 
ignite-marshaller-sys-cache
[23:51:33,578][INFO ][Thread-2][GridCacheProcessor] Stopped cache: 
ignite-sys-cache
[23:51:33,578][INFO ][Thread-2][GridCacheProcessor] Stopped cache: 
ignite-atomics-sys-cache
[23:51:33,579][INFO ][Thread-2][GridCacheProcessor] Stopped cache: igniteCache


> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: 

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950050#comment-14950050
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

How to check data added in streamer.

StormStreamer.java
getStreamer().addData(k, igniteGrid.get(k));

When i try fetching data in Test class i am getting Null.

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950036#comment-14950036
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Ignore above stack trace.

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14946505#comment-14946505
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

[~glutters] Tests are continuously timing out  for me. Can you please check 
again?



> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14946541#comment-14946541
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

GitHub user chandresh-pancholi opened a pull request:

https://github.com/apache/ignite/pull/138

 [Ignite-429] Implement IgniteStormStreamer to stream data from Apache Storm

Added java1.7 compatibility and javadoc in StormSpout class.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chandresh-pancholi/ignite master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/138.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #138
commit 7fa633cfb0cfb8144e780d9572a3a4fbe518bbd4
Author: chandresh pancholi 
Date:   2015-10-07T08:52:12Z

Adding javadoc in StormSpout class and make streamer compatible with java1.7



> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944983#comment-14944983
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Anton,

Didn't get you. What do you mean by actual code?

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943993#comment-14943993
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

GitHub user chandresh-pancholi opened a pull request:

https://github.com/apache/ignite/pull/130

[Ignite-429] Implement IgniteStormStreamer to stream data from Apache Storm

I have made some refactor changes suggested by Gian/Anton.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chandresh-pancholi/ignite master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/130.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #130


commit 8420e109c4d07bbf438f17dc79268c39b47e76b2
Author: chandresh pancholi 
Date:   2015-09-15T12:50:30Z

ignite-429 feature fix

commit a5adeb4c7badd52dd7724fa5a9a9ba7924e934ed
Author: chandresh pancholi 
Date:   2015-09-16T13:19:37Z

Ignite code refactor and modification

commit c6335046a07d9859a46d078e6cd8d7d2a7011df2
Author: chandresh pancholi 
Date:   2015-09-21T11:59:24Z

Code refactor

commit 4596bedfbfc756d3974b4d2270401515fa618bb5
Author: chandresh pancholi 
Date:   2015-09-28T09:12:13Z

Work completed

commit 538986b186b3d89797a34fe35c8120fecaf9
Author: chandresh pancholi 
Date:   2015-09-29T11:37:17Z

Apache ignite-storm integration

commit 3f40de788e5a050bbefb69ac2517a625e72b5299
Author: chandresh pancholi 
Date:   2015-09-29T11:37:50Z

exclusion of zookeeper

commit aa59cdade93d41d877b1966c4851aa827981b73c
Author: chandresh pancholi 
Date:   2015-10-03T12:13:18Z

Implemented Refactor suggestion given by Anton in Ignite0429

commit 2e103b915ba88b38604030092f55ed1f04b14cfe
Author: chandresh pancholi 
Date:   2015-10-05T07:43:02Z

Code refactor in storm module suggested by Gian/Anton



> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14942267#comment-14942267
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Gian can you review my code before i make pull request?

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939682#comment-14939682
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Sure Gian!

> 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: Chandresh Pancholi
>
> 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] [Assigned] (IGNITE-533) Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Chandresh Pancholi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chandresh Pancholi reassigned IGNITE-533:
-

Assignee: Chandresh Pancholi

> Implement IgniteZeromqStreamer to stream data from ZeroMQ
> -
>
> Key: IGNITE-533
> URL: https://issues.apache.org/jira/browse/IGNITE-533
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [ZeroMQ|http://zeromq.org/] for more info.
> We should create {{IgniteZeroMqStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert ZeroMQ messages to Ignite data using an optional pluggable 
> converter. If not provided, we should have some default mechanism.
> * 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14910199#comment-14910199
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

I will update wiki document .

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900558#comment-14900558
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Gian,

I have included  your suggestions and wrote unit test as well but i am having 
problem with getStreamer() and getIgnite(). Its giving me null.

I have pushed the code(https://github.com/chandresh-pancholi/ignite). can you 
please check?

Thanks

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877242#comment-14877242
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

Hi Gian,
If you have some time,can you go through my code and check where am i making 
mistake?

> 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: Chandresh Pancholi
>
> 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-429) Implement IgniteStormStreamer to stream data from Apache Storm

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745372#comment-14745372
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

It would be great if you provide me your implementation. is it already pushed?

> 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: Chandresh Pancholi
>
> 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)