Web Console updated

[Alexey Kuznetsov]

Hello everyone.

I would like to announce that we updated Web Console (
https://console.gridgain.com) to new version.

What's new:
1. Added a lot of properties to cluster and caches configuration wizards.
2. Redesigned Queries screen: spitted SQL and Scan queries into different
blocks.
3. Improved import schema from database.
4. Improved XML and Java code generation.
5. Implemented Queries monitoring screen (available since Ignite 1.8 and
GridGain 7.7.4).
 This screen allow to track what queries were executed in cluster and their
metrics (with execution plan). To enable this metric, you need to set
"queryDetailMetricsSize"
to value greater then zero.


  
  
 
  
  
   
 
6. Many minor bug fixes and improvements.

-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-4472) Web Console: Implement usage tracing

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-4472:


 Summary: Web Console: Implement usage tracing
 Key: IGNITE-4472
 URL: https://issues.apache.org/jira/browse/IGNITE-4472
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin


We need to track some kind of "activity scores" for users.
Activities:
# Configuration
# SQL
# Demo

And show that score on admin panel.

May be this could be implemented by some library.




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

Re: Capacity Planning - Calculating Memory Usage

[Alexandr Kuramshin]

Hi Val,

the understanding is simple.

When you enables the single index on entry class you get "First index
overhead" per entry.

When you enables two indices on entry class you get "First index overhead"
+ "Next index overhead" per entry.

With three indices you get "First index overhead" + 2 * "Next index
overhead", and so on...

Each annotated field with @QuerySqlField is an index, except multiple
fields annotated with @QuerySqlField.Group.

Another way to defining indices is to use property "queryEntities" and it's
subproperty "indexes". See the article [1]

[1] https://apacheignite.readme.io/docs/indexes

2016-12-20 8:38 GMT+07:00 Valentin Kulichenko :

> Alexandr,
>
> Can you please clarify what is "First index overhead" and "Next index
> overhead"? Generally, I think overhead provided by indexes should be
> described in more details, now it's not very clear what happens when
> indexes are added.
>
> Also the calculation example should be a separate section.
>
> -Val
>
> On Wed, Dec 14, 2016 at 1:07 AM, Alexandr Kuramshin 
> wrote:
>
> > Thank you, Andrey,
> >
> > I'll do additional tests with expire policy and update the article.
> >
> > 2016-12-13 22:10 GMT+07:00 Andrey Mashenkov  >:
> >
> > > Alexandr,
> > >
> > > In addition. If expire policy is configured, there is additional
> overhead
> > > to entries can be tracked by TtlManager.
> > > This overhead is OnHeap and does not depend on cache MemoryMode (until
> > > Ignite-3840 will be in master).
> > >
> > > For now overhead is about 32-40 bytes (EntryWrapper itself) + (40-48)
> > bytes
> > > (ConcurrentSkipList node) per entry.
> > >
> > >
> > >
> > > On Tue, Dec 13, 2016 at 10:37 AM, Alexandr Kuramshin <
> > ein.nsk...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hello, Igniters,
> > > >
> > > > I'd like to represent updated article [1] about the subject.
> > > >
> > > > And I'll very appreciate your comments and questions about it.
> > > >
> > > > Please review.
> > > >
> > > > [1] http://apacheignite.gridgain.org/docs/capacity-planning
> > > >
> > > > --
> > > > Thanks,
> > > > Alexandr Kuramshin
> > > >
> > >
> > >
> > >
> > > --
> > > С уважением,
> > > Машенков Андрей Владимирович
> > > Тел. +7-921-932-61-82
> > >
> > > Best regards,
> > > Andrey V. Mashenkov
> > > Cerr: +7-921-932-61-82
> > >
> >
> >
> >
> > --
> > Thanks,
> > Alexandr Kuramshin
> >
>



-- 
Thanks,
Alexandr Kuramshin

Re: Google Summer Of Code 2017

[Valentin Kulichenko]

I can take over DataFrames integration as I already did some investigation
in this area. Spark also has GraphX and GraphFrames for graph processing,
we can think about integration with them as well.

Machine learning also sounds very interesting.

-Val

On Wed, Dec 21, 2016 at 4:22 PM, Dmitriy Setrakyan 
wrote:

> I can also do mentoring for any of the listed features.
>
> On Wed, Dec 21, 2016 at 2:50 PM, Denis Magda  wrote:
>
> > Alex, thanks for bringing this out!
> >
> > This is a great opportunity for our community to find talented students
> > who are capable of adding new features to Ignite. I can take care of all
> > the paperwork. The features list won’t be a big deal as well. But we need
> > mentors who will voluntarily dedicate their time helping the
> participants.
> >
> > Well, here is a list of features that pop up immediately out of my head
> > and that I would like to offer to GSoC (Google Summer Of Code).
> > Native client for Python (data grid, compute grid, continuous queries).
> > Native client for Node.JS (https://issues.apache.org/
> > jira/browse/IGNITE-961  >)
> > Kubernetis integration (IGNITE-4159  > jira/browse/IGNITE-4159>).
> > Spark Data Frames API implementation.
> > Machine Learning Grid implementation or integration with Spark MLib.
> >
> > Any other features?
> >
> > As for the mentoring I can take over one or two of the following -
> > Kubernetis, Machine Learning or Node.JS.
> >
> > Is there anyone else who can try a role of a mentor?
> >
> > —
> > Denis
> >
> > > On Dec 19, 2016, at 8:15 PM, Alexey Kuznetsov 
> > wrote:
> > >
> > > Igniters!
> > >
> > > What do you think about participating in Google Summer Of Code 2017?
> > > See: https://developers.google.com/open-source/gsoc
> > >
> > > The Google Summer of Code, often abbreviated to GSoC, is an
> international
> > > annual program, first held from May to August 2005, in which Google
> > awards
> > > stipends (of US$5,500, as of 2016 ) to all students who successfully
> > > complete a requested free and open-source software coding project
> during
> > > the summer.
> > >
> > > Students will work on some issues in Ignite.
> > > Ignite community will provide mentors for those students and answer
> > > students questions on dev list.
> > > Google will pay students. :)
> > >
> > > We need to prepare list of tasks that will be useful for Ignite and
> could
> > > be finished in three months by students.
> > >
> > > What do you think?
> > > --
> > > Alexey Kuznetsov
> >
> >
>

Re: Google Summer Of Code 2017

[Dmitriy Setrakyan]

I can also do mentoring for any of the listed features.

On Wed, Dec 21, 2016 at 2:50 PM, Denis Magda  wrote:

> Alex, thanks for bringing this out!
>
> This is a great opportunity for our community to find talented students
> who are capable of adding new features to Ignite. I can take care of all
> the paperwork. The features list won’t be a big deal as well. But we need
> mentors who will voluntarily dedicate their time helping the participants.
>
> Well, here is a list of features that pop up immediately out of my head
> and that I would like to offer to GSoC (Google Summer Of Code).
> Native client for Python (data grid, compute grid, continuous queries).
> Native client for Node.JS (https://issues.apache.org/
> jira/browse/IGNITE-961 )
> Kubernetis integration (IGNITE-4159  jira/browse/IGNITE-4159>).
> Spark Data Frames API implementation.
> Machine Learning Grid implementation or integration with Spark MLib.
>
> Any other features?
>
> As for the mentoring I can take over one or two of the following -
> Kubernetis, Machine Learning or Node.JS.
>
> Is there anyone else who can try a role of a mentor?
>
> —
> Denis
>
> > On Dec 19, 2016, at 8:15 PM, Alexey Kuznetsov 
> wrote:
> >
> > Igniters!
> >
> > What do you think about participating in Google Summer Of Code 2017?
> > See: https://developers.google.com/open-source/gsoc
> >
> > The Google Summer of Code, often abbreviated to GSoC, is an international
> > annual program, first held from May to August 2005, in which Google
> awards
> > stipends (of US$5,500, as of 2016 ) to all students who successfully
> > complete a requested free and open-source software coding project during
> > the summer.
> >
> > Students will work on some issues in Ignite.
> > Ignite community will provide mentors for those students and answer
> > students questions on dev list.
> > Google will pay students. :)
> >
> > We need to prepare list of tasks that will be useful for Ignite and could
> > be finished in three months by students.
> >
> > What do you think?
> > --
> > Alexey Kuznetsov
>
>

Re: Google Summer Of Code 2017

[Denis Magda]

Alex, thanks for bringing this out!

This is a great opportunity for our community to find talented students who are 
capable of adding new features to Ignite. I can take care of all the paperwork. 
The features list won’t be a big deal as well. But we need mentors who will 
voluntarily dedicate their time helping the participants.

Well, here is a list of features that pop up immediately out of my head and 
that I would like to offer to GSoC (Google Summer Of Code).
Native client for Python (data grid, compute grid, continuous queries).
Native client for Node.JS (https://issues.apache.org/jira/browse/IGNITE-961 
)
Kubernetis integration (IGNITE-4159 
).
Spark Data Frames API implementation.
Machine Learning Grid implementation or integration with Spark MLib.

Any other features?

As for the mentoring I can take over one or two of the following - Kubernetis, 
Machine Learning or Node.JS.

Is there anyone else who can try a role of a mentor?

—
Denis

> On Dec 19, 2016, at 8:15 PM, Alexey Kuznetsov  wrote:
> 
> Igniters!
> 
> What do you think about participating in Google Summer Of Code 2017?
> See: https://developers.google.com/open-source/gsoc
> 
> The Google Summer of Code, often abbreviated to GSoC, is an international
> annual program, first held from May to August 2005, in which Google awards
> stipends (of US$5,500, as of 2016 ) to all students who successfully
> complete a requested free and open-source software coding project during
> the summer.
> 
> Students will work on some issues in Ignite.
> Ignite community will provide mentors for those students and answer
> students questions on dev list.
> Google will pay students. :)
> 
> We need to prepare list of tasks that will be useful for Ignite and could
> be finished in three months by students.
> 
> What do you think?
> -- 
> Alexey Kuznetsov

Re: Ignite Shutdown Hook

[Denis Magda]

Please share the thread dumps with us.

—
Denis

> On Dec 21, 2016, at 6:35 AM, hemanta  wrote:
> 
> Thank you for your reply. It is stuck at Ignite. 
> If in last line of public static void main() I add code to stop Ignite then
> everything works fine. But I have so many stand alone classes (public static
> void main) that run as a part of upgrade that I can not add Ignition.stop()
> in all of them. So, I was looking at option of shutdown hook which is not
> working with Ignite.
> 
> I see lots of IgniteThread in threaddump. 
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Shutdown-Hook-tp13198p13239.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Hello

[Denis Magda]

Alexander,

Thanks for the details. Now I see what you’re talking about. Agree, it makes 
sense to support this. Could you initiate a dedicated discussion on the dev 
list proposing this to the community and sharing design/implementations details 
if any? This discussion named “Hello” is not the place for this :)

—
Denis

> On Dec 21, 2016, at 1:42 AM, Александр Меньшиков  wrote:
> 
> Denis,
> 
> Thanks for your reply.
> 
> My question is not about data locality. As far as I know nodes are connected 
> in a ring. For example if i have 6 nodes, with names A, B, C, D, E, and F 
> they can connect in ring any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc. And if some node falls out of topology neighboring nodes must reconnect. 
> If nodes A,B and C located in the same physical location, and D, E and F in 
> another, and in some time one physical location is not available in another, 
> we can get different number of reconnections. Best case scenario if we have 
> ring like A-B-CxD-E-FxA ('x' mean disconnect) -- then we get only one 
> reconnect (C reconnect to A or F reconnect to D -- depending on what part of 
> the cluster we leave alive). But now possible that case AxFxBxExCxDxA -- then 
> we get a lot of reconnections (A to B, B to C, C to A -- in general n/2 
> reconnections, where n -- number of nodes). And i think to add something to 
> ensure that we always have good sorting of nodes connections (A-B-C-...-Z-A).
> 
> 2016-12-20 23:05 GMT+03:00 Denis Magda  >:
> Alexander,
> 
> CC-ing the dev list to keep everyone in track.
> 
> I hope the case you’re talking about can be already implemented by the usage 
> of RendezvousAffinityFunction.setAffinityBackupFilter(…) method [1]. This 
> method gives you a way to control a locality of your primary and backup 
> nodes. Depending on the filter implementation specific nodes might end up in 
> one physical location while the rest in the others.
> 
> [1] 
> https://ignite.apache.org/releases/1.7.0/javadoc/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html
>  
> 
> 
> —
> Denis
> 
>> On Dec 20, 2016, at 7:02 AM, Александр Меньшиков > > wrote:
>> 
>> I think in near time i will take some "newbie" tickets, but for future want 
>> to ask about ring topology in Ignite. In case where we have big physically 
>> stretched claster ring can be not optimal. For example: Node-1 in 1-physical 
>> location, Node-2 in  2-physical location,  Node-3 in 1-physical location,  
>> Node-4 in  2-physical location and ect. So if one physical location to fall 
>> out of the cluster, we get more breaks in ring than the theoretical minimum. 
>> I want to add an additional order in the process of constructing a ring so 
>> that ensure physically close nodes were close in topology.
>> 
>> 2016-11-24 0:01 GMT+03:00 Denis Magda > >:
>> Here are some ticket you may want to start with
>> https://ignite.apache.org/community/contribute.html#pick-ticket 
>> 
>> 
>> —
>> Denis
>> 
>>> On Nov 23, 2016, at 5:33 AM, Dmitriy Setrakyan >> > wrote:
>>> 
>>> Hi Alex,
>>> 
>>> Welcome to the Ignite community!
>>> 
>>> Once you are familiar with the contribution process, please see if there is
>>> a specific Jira ticket you would like work on. We will help you get started.
>>> 
>>> D.
>>> 
>>> On Wed, Nov 23, 2016 at 2:24 AM, Vladislav Pyatkov >> >
>>> wrote:
>>> 
 Please read https://ignite.apache.org/community/contribute.html#contribute 
 
 
 Looking forward for your contributions!
 
 On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков 
> 
 wrote:
 
> I want to contribute.
> 
> 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov  >:
> 
>> Hi Alex,
>> 
>> This is Apache Ignite development community.
>> Are you want to contribute to Ignite or you are have any suggestion?
>> 
>> On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков <
>> sharple...@gmail.com >
>> wrote:
>> 
>>> Hello
>>> 
>> 
> 
 
>> 
>> 
> 
> 

Re: Diagram for RDBMS Schema Import with Web Console

[Denis Magda]

Thanks guys, I’ve sent an updated version to the designer.

—
Denis

> On Dec 20, 2016, at 7:21 PM, Alexey Kuznetsov  wrote:
> 
> Denis,
> 
> I attached slightly corrected diagram:
> https://issues.apache.org/jira/secure/attachment/12844178/SchemaImport-2.png
> 
> On Wed, Dec 21, 2016 at 8:35 AM, Dmitriy Setrakyan 
> wrote:
> 
>> Thanks, Denis! The diagram you created looks nice.
>> 
>> On Tue, Dec 20, 2016 at 11:53 AM, Denis Magda  wrote:
>> 
>>> Igniters,
>>> 
>>> Alexey Kuznetsov has contributed the documentation which describes how to
>>> import a database schema converting it into Ignite’s configuration and
>>> project files
>>> https://apacheignite-mix.readme.io/v1.8/docs/web-console <
>>> https://apacheignite-mix.readme.io/v1.8/docs/web-console>
>>> 
>>> The last thing to do before we can make this doc public is to prepare a
>>> fancy diagram. Presently we use this template
>>>  <
>>> https://files.readme.io/50cff50-SchemaImport.png>
>> 50cff50-SchemaImport.png
>>> 
>>> 
>>> I’m prepared a sketch for a designer. Please provide your
>>> comments/thoughts before I sent it out to that person.
>>> https://issues.apache.org/jira/secure/attachment/12844119/
>>> WP_20161220_11_33_55_Pro.jpg >> a/secure/attachment/12844119/WP_20161220_11_33_55_Pro.jpg>
>>> 
>>> —
>>> Denis
>> 
> 
> 
> 
> -- 
> Alexey Kuznetsov

[jira] [Created] (IGNITE-4471) ODBC: Can not retrieve table metadata.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-4471:
---

 Summary: ODBC: Can not retrieve table metadata.
 Key: IGNITE-4471
 URL: https://issues.apache.org/jira/browse/IGNITE-4471
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 1.8
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.0


{{SQLTables}} always returns set of empty strings currently.



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

Re: Why our functional interfaces are serializable?

[Dmitriy Setrakyan]

I would agree only for internal Ignite classes. If we touch public classes,
we risk breaking backward compatibility.

On Wed, Dec 21, 2016 at 1:21 AM, Sergi Vladykin 
wrote:

> Agree, but we use some of them on public API for distributed operations and
> they have to be Serializable.
>
> Sergi
>
> 2016-12-21 12:06 GMT+03:00 Vladimir Ozerov :
>
> > Folks,
> >
> > We have more than 1500 classes (mostly anonymous) implementing functional
> > interfaces. Most common are *IgnitePredicate*, *IgniteClosure*, etc..
> >
> > Question: why these interfaces are Serializable? A lot of classes which
> > implement these interfaces are never meant to be serialized.
> >
> > I propose to remove Serializable from all functional interfaces.
> >
> > Vladimir.
> >
>

Re: Ignite Shutdown Hook

[hemanta]

Thank you for your reply. It is stuck at Ignite. 
If in last line of public static void main() I add code to stop Ignite then
everything works fine. But I have so many stand alone classes (public static
void main) that run as a part of upgrade that I can not add Ignition.stop()
in all of them. So, I was looking at option of shutdown hook which is not
working with Ignite.

I see lots of IgniteThread in threaddump. 



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Shutdown-Hook-tp13198p13239.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #1224: Ignite-2795

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #976: Ignite 2560 2

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #980: Ignite 3597

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1016: IGNITE-2881 : SPI queries not working

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1031: IGNITE-2833 : GridCacheTtlManager pending queue r...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1370: IGNITE-4142: Assertion in ClientImpl.updateMetric...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1372: IGNITE-4142: Assertion in ClientImpl.updateMetric...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-4142: Assertion in ClientImpl.updateMetrics()



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4142-1

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

https://github.com/apache/ignite/pull/1372.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 #1372


commit 6319c3b9e6a187157435ecf848dc0d82717484cb
Author: Andrey V. Mashenkov 
Date:   2016-12-21T16:53:08Z

Fixed.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1371: IGNITE-2793 Added support for byte arrays to ODBC

[skalashnikov]

GitHub user skalashnikov opened a pull request:

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

IGNITE-2793 Added support for byte arrays to ODBC



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

$ git pull https://github.com/gridgain/apache-ignite ignite-2793

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

https://github.com/apache/ignite/pull/1371.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 #1371


commit b0a7e0a01f6dafd33137ebd87e7b41d32074ede4
Author: skalashnikov 
Date:   2016-12-20T17:51:46Z

IGNITE-2793 Added SQL_C_BINARY support

commit 787590ef33a523a05b0ea4e40e511ddc7e9993ba
Author: skalashnikov 
Date:   2016-12-21T11:48:39Z

IGNITE-2793 fixed some tabs, added parameter tests

commit d93b7815c2bcd77a43baaa4281c02aa2fe419010
Author: skalashnikov 
Date:   2016-12-21T16:37:33Z

IGNITE-2793 Done




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1298: IGNITE-3886 .NET: Build script

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-4470) ODBC: Add support for logger configuration

[Sergey Kalashnikov (JIRA)]

Sergey Kalashnikov created IGNITE-4470:
--

 Summary: ODBC: Add support for logger configuration
 Key: IGNITE-4470
 URL: https://issues.apache.org/jira/browse/IGNITE-4470
 Project: Ignite
  Issue Type: Improvement
  Components: odbc
Affects Versions: 1.8
Reporter: Sergey Kalashnikov
Assignee: Sergey Kalashnikov
 Fix For: 2.0


Users of ODBC driver should be able to configure logging without driver 
recompilation.
Logger should be setup with via connection string parameter.



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

[jira] [Created] (IGNITE-4469) Hadoop: better defaults to memory page size and message size.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4469:
---

 Summary: Hadoop: better defaults to memory page size and message 
size.
 Key: IGNITE-4469
 URL: https://issues.apache.org/jira/browse/IGNITE-4469
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Minor
 Fix For: 2.0


Currently we have too low shuffle message size and too low initial memory 
buffer size - 128Kb and 32Kb respectively. 

As we target big data use case, it makes sense to make these properties bigger. 
According to several experiments, good size is 1Mb each.



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

Re: Hello

[Александр Меньшиков]

Denis,

Thanks for your reply.

My question is not about data locality. As far as I know nodes are
connected in a ring. For example if i have 6 nodes, with names A, B, C, D,
E, and F they can connect in ring any possible way: A-B-C-D-E-F-A, or
A-F-B-E-C-D-A, etc. And if some node falls out of topology neighboring
nodes must reconnect. If nodes A,B and C located in the same physical
location, and D, E and F in another, and in some time one physical location
is not available in another, we can get different number of reconnections.
Best case scenario if we have ring like A-B-CxD-E-FxA ('x' mean disconnect)
-- then we get only one reconnect (C reconnect to A or F reconnect to D --
depending on what part of the cluster we leave alive). But now possible
that case AxFxBxExCxDxA -- then we get a lot of reconnections (A to B, B to
C, C to A -- in general n/2 reconnections, where n -- number of nodes). And
i think to add something to ensure that we always have good sorting of
nodes connections (A-B-C-...-Z-A).

2016-12-20 23:05 GMT+03:00 Denis Magda :

> Alexander,
>
> CC-ing the dev list to keep everyone in track.
>
> I hope the case you’re talking about can be already implemented by the
> usage of RendezvousAffinityFunction.setAffinityBackupFilter(…) method
> [1]. This method gives you a way to control a locality of your primary and
> backup nodes. Depending on the filter implementation specific nodes might
> end up in one physical location while the rest in the others.
>
> [1] https://ignite.apache.org/releases/1.7.0/javadoc/org/
> apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html
>
> —
> Denis
>
> On Dec 20, 2016, at 7:02 AM, Александр Меньшиков 
> wrote:
>
> I think in near time i will take some "newbie" tickets, but for future
> want to ask about ring topology in Ignite. In case where we have big
> physically stretched claster ring can be not optimal. For example: Node-1
> in 1-physical location, Node-2 in  2-physical location,  Node-3 in
> 1-physical location,  Node-4 in  2-physical location and ect. So if one
> physical location to fall out of the cluster, we get more breaks in ring
> than the theoretical minimum. I want to add an additional order in the
> process of constructing a ring so that ensure physically close nodes were
> close in topology.
>
> 2016-11-24 0:01 GMT+03:00 Denis Magda :
>
>> Here are some ticket you may want to start with
>> https://ignite.apache.org/community/contribute.html#pick-ticket
>>
>> —
>> Denis
>>
>> On Nov 23, 2016, at 5:33 AM, Dmitriy Setrakyan 
>> wrote:
>>
>> Hi Alex,
>>
>> Welcome to the Ignite community!
>>
>> Once you are familiar with the contribution process, please see if there
>> is
>> a specific Jira ticket you would like work on. We will help you get
>> started.
>>
>> D.
>>
>> On Wed, Nov 23, 2016 at 2:24 AM, Vladislav Pyatkov > >
>> wrote:
>>
>> Please read https://ignite.apache.org/community/contribute.html#contribu
>> te
>>
>> Looking forward for your contributions!
>>
>> On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков <
>> sharple...@gmail.com
>>
>>
>> wrote:
>>
>> I want to contribute.
>>
>> 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov :
>>
>> Hi Alex,
>>
>> This is Apache Ignite development community.
>> Are you want to contribute to Ignite or you are have any suggestion?
>>
>> On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков <
>> sharple...@gmail.com>
>> wrote:
>>
>> Hello
>>
>>
>>
>>
>>
>>
>
>

Re: Why our functional interfaces are serializable?

[Sergi Vladykin]

Agree, but we use some of them on public API for distributed operations and
they have to be Serializable.

Sergi

2016-12-21 12:06 GMT+03:00 Vladimir Ozerov :

> Folks,
>
> We have more than 1500 classes (mostly anonymous) implementing functional
> interfaces. Most common are *IgnitePredicate*, *IgniteClosure*, etc..
>
> Question: why these interfaces are Serializable? A lot of classes which
> implement these interfaces are never meant to be serialized.
>
> I propose to remove Serializable from all functional interfaces.
>
> Vladimir.
>

Why our functional interfaces are serializable?

[Vladimir Ozerov]

Folks,

We have more than 1500 classes (mostly anonymous) implementing functional
interfaces. Most common are *IgnitePredicate*, *IgniteClosure*, etc..

Question: why these interfaces are Serializable? A lot of classes which
implement these interfaces are never meant to be serialized.

I propose to remove Serializable from all functional interfaces.

Vladimir.

[jira] [Created] (IGNITE-4468) RoundRobinLoadBalancingSpi‘s documentation and Javadoc description incorrectly

[Yujue Li (JIRA)]

Yujue Li created IGNITE-4468:


 Summary: RoundRobinLoadBalancingSpi‘s documentation and Javadoc 
description incorrectly
 Key: IGNITE-4468
 URL: https://issues.apache.org/jira/browse/IGNITE-4468
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 1.8
Reporter: Yujue Li
Priority: Minor
 Fix For: 1.9


Class RoundRobinLoadBalancingSpi
Description of the perTask attribute in this class is confusing.
Some places describe the default value of true, some places describe the 
default value of false, and from the source code analysis, the default value 
should be false.
I hope the community can unify the adjustment of Javadoc and related documents.



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