Re: Ignite inquiry

[Pavel Tupitsyn]

Hello Michael,

Thank you for your interest in the Apache Ignite project!

1. What is the pricing of the product? (1 server, 16 cores, 128 GB RAM, 3
TB SSD).
Apache Ignite is free to use without hardware limitations. Licensed under
Apache 2.0.
https://www.apache.org/licenses/LICENSE-2.0

2. Can it perform 100,000 transactions per second?
Yes

3. Can it store 1 billion records?
Yes

4. Does it support SQL-esque queries?
Yes https://apacheignite.readme.io/docs/distributed-sql

5. Does it support table creation and deletion via API or SQL command?
Yes https://apacheignite-sql.readme.io/docs/ddl

6. Does it support 100 concurrent accesses on a single node?
Yes (I guess, not 100% understand this question)

7. Can it be implemented on a single node?
Yes

8. Does it run native on Windows 10?
Yes

9. Can it utilize 100 GB of RAM?
Yes

10. Can it utilize 3 TB of disk space?
Yes

11. Is an API available for C# or .NET?
Yes, C#/.NET API is available in Server, Thick Client, and Thin Client
modes.
https://apacheignite-net.readme.io/docs

12. Has your company been in existence for over 10 years?
GridGain donated part of their source code to the Apache Software
Foundation in 2014,
and Apache Ignite project was born. GridGain has existed since 2007.


I hope this answers your questions.
In future, please prefer u...@ignite.apache.org address. dev@ignite is for
development discussions.

Thanks,
Pavel


On Sun, Jul 12, 2020 at 1:03 PM Piaget Modeler 
wrote:

> Hello,
>
> I hope this message finds you in good spirits.
>
> I'd like to get some information about Ignite, specifically:
>
> 1. What is the pricing of the product? (1 server, 16 cores, 128 GB RAM, 3
> TB SSD).
> 2. Can it perform 100,000 transactions per second?
> 3. Can it store 1 billion records?
> 4. Does it support SQL-esque queries?
> 5. Does it support table creation and deletion via API or SQL command?
> 6. Does it support 100 concurrent accesses on a single node?
> 7. Can it be implemented on a single node?
> 8. Does it run native on Windows 10?
> 9. Can it utilize 100 GB of RAM?
> 10. Can it utilize 3 TB of disk space?
> 11. Is an API available for C# or .NET?
> 12. Has your company been in existence for over 10 years?
>
> Kindly advise ASAP.
>
> Thank you.
>
> Michael S. P. Miller
> +1 310 728 0994
>
>

Re: Re[2]: IGNITE-6499 Compact NULL fields

[Ilya Kasnacheev]

Hello!

If we do improve it, I think we should go for a full re-think as opposed to
a single breaking change that doesn't actually improve that much.

Nevertheless, I think we can commit some improvements with opt-in
BinaryConfiguration.

Regards,
-- 
Ilya Kasnacheev


сб, 11 июл. 2020 г. в 01:27, steve.hostett...@gmail.com <
steve.hostett...@gmail.com>:

> Ok gotcha, so it is not going to make it.
>
> Just to note that we are dragging this since before v2.0 and just a
> reminder
> that someone else tried a similar thing before v2 and it got blocked
> because
> it was too much of a change for v2.
>
> Typically the type of things that we can never change because it is too
> much
> of an impact.
>
> BinaryObject format is not optimal far for it and if we cannot change it
> incrementally nor in a big bang...
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-13246) Implement EVT_BASELINE_XXX events

[Ivan Bessonov (Jira)]

Ivan Bessonov created IGNITE-13246:
--

 Summary: Implement EVT_BASELINE_XXX events
 Key: IGNITE-13246
 URL: https://issues.apache.org/jira/browse/IGNITE-13246
 Project: Ignite
  Issue Type: Improvement
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov


In order to notify external tools we need events EVT_BASELINE_CHANGED, 
EVT_BASELINE_AUTO_ADJUST_ENABLED_CHANGED and 
EVT_BASELINE_AUTO_ADJUST_AWAITING_TIME_CHANGED to correctly update baseline 
info on UI.



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

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

[Ilya Kasnacheev]

Hello!

We used to publish nightlies to some non-main repo but I'm afraid this may
be broken currently.

Regards,
-- 
Ilya Kasnacheev


пн, 13 июл. 2020 г. в 01:07, Saikat Maitra :

> Hi Ilya,
>
> Thank you for reviewing the changes. I have merged the PRs.
>
> I will need to look into how we can pull nightly snapshots build of
> ignite-core module for Travis build to pass.
>
> Travis build is currently failing as it is unable to pull 2.9.0-SNAPSHOT
> version.
>
> Regards,
> Saikat
>
> On Fri, Jul 10, 2020 at 5:55 AM Ilya Kasnacheev  >
> wrote:
>
> > Hello!
> >
> > I have checked it, looks OK. Please note that Travis fails in ignite-ext.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пт, 3 июл. 2020 г. в 21:50, Saikat Maitra :
> >
> > > Hi
> > >
> > > I have created PRs for the following jira issue.
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-12362
> > >
> > > IGNITE-12362 Migrate MQTT module to ignite-extensions
> > >
> > > PRs
> > > https://github.com/apache/ignite-extensions
> > > https://github.com/apache/ignite/pull/7950
> > >
> > >
> > > Please review and share your feedback.
> > >
> > > Regards,
> > > Saikat
> > >
> > > On Sun, Jun 21, 2020 at 3:44 PM Saikat Maitra  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I have created PRs for the following jira issue.
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-12362
> > > >
> > > > IGNITE-12362 Migrate MQTT module to ignite-extensions
> > > >
> > > > PRs
> > > > https://github.com/apache/ignite-extensions
> > > > https://github.com/apache/ignite/pull/7950
> > > >
> > > >
> > > > Please review and share your feedback.
> > > >
> > > > Regards,
> > > > Saikat
> > > >
> > > >
> > > >
> > >
> >
>

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[Ilya Kasnacheev]

Hello!

It seems that it works and we now have 2.9 nightlies.

Guys, can you please bump the master POM version to 2.10.0-SNAPSHOT?

Regards,
-- 
Ilya Kasnacheev


пт, 10 июл. 2020 г. в 17:43, Ilya Kasnacheev :

> Hello!
>
> I have also set up nightly builds to (hopefully) build 2.9
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 7 июл. 2020 г. в 17:04, Ilya Kasnacheev :
>
>> Hello!
>>
>> I have changed the schedule condition so ignite-2.9 will be run instead.
>> Please check if it works tomorrow.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> вт, 7 июл. 2020 г. в 16:42, Alex Plehanov :
>>
>>> Guys,
>>>
>>> Can somebody help with creating scheduled build triggers for nightly "Run
>>> All" on TC for "ignite-2.9" branch?
>>>
>>> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
>>> branch [1]. Do we still need it? Or just forgot to remove it after
>>> release?
>>>
>>> [1] :
>>>
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv
>>>
>>> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov :
>>>
>>> > Anton, thank you.
>>> >
>>> > Guys,
>>> >
>>> > I've cut the release branch. From now on please pin resolved in the
>>> master
>>> > branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
>>> > tickets to ignite-2.9 branch.
>>> >
>>> > As far as the release branch cut was delayed, I propose to move code
>>> > freeze dates by one week (to 17 July 2020). WDYT?
>>> >
>>> > I've moved long-time inactive non-blocker tickets (except documentation
>>> > related, we will deal with them later) from 2.9 release, please check
>>> your
>>> > Jira issues to have the correct "Fix version" field if your ticket is
>>> > planned to 2.9 release.
>>> >
>>> > All currently pinned to 2.9 issues can be found on the release page
>>> [1].
>>> >
>>> > I didn't get about [2] ticket mentioned in this thread, are we going to
>>> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
>>> clarify?
>>> >
>>> > [1]:
>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>>> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
>>> >
>>> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov :
>>> >
>>> >> You're now at the "Ignite Release Managers" group.
>>> >> Please check you gain access.
>>> >>
>>> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <
>>> plehanov.a...@gmail.com>
>>> >> wrote:
>>> >>
>>> >> > Guys,
>>> >> >
>>> >> > I've created the 2.9 release confluence page [1].
>>> >> > Also, I found that I don't have permission to Team City release
>>> tasks.
>>> >> Can
>>> >> > anyone give me such permissions?
>>> >> >
>>> >> > [1]:
>>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>>> >> >
>>> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <
>>> zaleslaw@gmail.com>:
>>> >> >
>>> >> > > Igniters
>>> >> > >
>>> >> > > Unfortunately, the ML model export/import feature
>>> >> > >  is under
>>> >> development
>>> >> > > yet.
>>> >> > > I need to delay it before the 2.10 release.
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <
>>> plehanov.a...@gmail.com>:
>>> >> > >
>>> >> > > > Denis,
>>> >> > > >
>>> >> > > > Yes, I still ready to manage it.
>>> >> > > > Today I will prepare a release page on wiki and will try to go
>>> over
>>> >> > > tickets
>>> >> > > > list.
>>> >> > > > Also, I have plans to cut the branch by the end of next week if
>>> >> there
>>> >> > are
>>> >> > > > no objections.
>>> >> > > >
>>> >> > > >
>>> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda :
>>> >> > > >
>>> >> > > > > Igniters,
>>> >> > > > >
>>> >> > > > > Are we moving forward with this release? Alex Plehanov, are
>>> you
>>> >> still
>>> >> > > > ready
>>> >> > > > > to manage it? It seems like everyone agreed with the timeline
>>> you
>>> >> > > > proposed
>>> >> > > > > in the very beginning.
>>> >> > > > >
>>> >> > > > > -
>>> >> > > > > Denis
>>> >> > > > >
>>> >> > > > >
>>> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <
>>> dma...@apache.org>
>>> >> > wrote:
>>> >> > > > >
>>> >> > > > > > Sergey, Ivan,
>>> >> > > > > >
>>> >> > > > > > Could you please check the questions below? If it's
>>> >> time-consuming
>>> >> > to
>>> >> > > > > > rework continuous queries, then the new mode can become
>>> >> available
>>> >> > in
>>> >> > > > the
>>> >> > > > > > experimental state and should not let register continuous
>>> >> queries
>>> >> > to
>>> >> > > > > avoid
>>> >> > > > > > potential deadlocks. Overall, this design gap in continuous
>>> >> queries
>>> >> > > was
>>> >> > > > > > like a bomb that has just detonated [1]. Anyway, this new
>>> >> > > connectivity
>>> >> > > > > mode
>>> >> > > > > > will be priceless even if you can't use continuous queries
>>> with
>>> >> > them
>>> >> > > > > > because right now we cannot even start a thick client
>>> inside of
>>> 

[jira] [Created] (IGNITE-13247) Calcite integration. Move QueryCursorEx.isQuery() flag to a proper place.

[Igor Seliverstov (Jira)]

Igor Seliverstov created IGNITE-13247:
-

 Summary: Calcite integration. Move QueryCursorEx.isQuery() flag to 
a proper place.
 Key: IGNITE-13247
 URL: https://issues.apache.org/jira/browse/IGNITE-13247
 Project: Ignite
  Issue Type: Improvement
Reporter: Igor Seliverstov


Since QueryCursorEx is used in continuous queries, we should move SQL query 
related flag to another place.



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

[jira] [Created] (IGNITE-13248) FileWriteAheadLogManager creates 0-length WAL segments and cannot start later

[Nikita Tolstunov (Jira)]

Nikita Tolstunov created IGNITE-13248:
-

 Summary: FileWriteAheadLogManager creates 0-length WAL segments 
and cannot start later
 Key: IGNITE-13248
 URL: https://issues.apache.org/jira/browse/IGNITE-13248
 Project: Ignite
  Issue Type: Bug
Reporter: Nikita Tolstunov
Assignee: Nikita Tolstunov


Setting IGNITE_WAL_MMAP to false and walMode to LOG_ONLY produces following 
exception on node start:
{code:java}
[2020-05-18 19:55:17,362][WARN ][main][FileWriteAheadLogManager] Failed to read 
file header 
[/home/sdanilov/Development/incubator-ignite/work/db/wal/node00-c81f5b62-2288-4268-9f7c-3d8f6a02777d/0001.wal].
 Skipping this file
java.io.EOFException: EOF at position [0] expected to read [1] bytes
at 
org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:121)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.readByte(SimpleFileInput.java:180)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.readUnsignedByte(SimpleFileInput.java:189)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.readFileDescriptor(FileWriteAheadLogManager.java:1180)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$1700(FileWriteAheadLogManager.java:157)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.scanMinMaxArchiveIndices(FileWriteAheadLogManager.java:1767)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.init(FileWriteAheadLogManager.java:1709)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.(FileWriteAheadLogManager.java:1701)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.(FileWriteAheadLogManager.java:1687)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.start0(FileWriteAheadLogManager.java:477)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:60)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:541)
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1927)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1164)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2072)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1741)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1155)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:675)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:600)
at org.apache.ignite.Ignition.start(Ignition.java:319)
at 
org.apache.ignite.examples.corrupt.ZeroLengthReproducer.main(ZeroLengthReproducer.java:64)
{code}



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

[jira] [Created] (IGNITE-13249) Update Ignite version to 2.10.0-SNAPSHOT

[Aleksey Plekhanov (Jira)]

Aleksey Plekhanov created IGNITE-13249:
--

 Summary: Update Ignite version to 2.10.0-SNAPSHOT
 Key: IGNITE-13249
 URL: https://issues.apache.org/jira/browse/IGNITE-13249
 Project: Ignite
  Issue Type: Task
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov


Master branch should have 2.10.0-SNAPSHOT version after release 2.9 branch has 
created.



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

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[Alex Plehanov]

Ilya,
Yes, it works, thank you.

I will update POM version today.

пн, 13 июл. 2020 г. в 16:01, Ilya Kasnacheev :

> Hello!
>
> It seems that it works and we now have 2.9 nightlies.
>
> Guys, can you please bump the master POM version to 2.10.0-SNAPSHOT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 10 июл. 2020 г. в 17:43, Ilya Kasnacheev :
>
> > Hello!
> >
> > I have also set up nightly builds to (hopefully) build 2.9
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 7 июл. 2020 г. в 17:04, Ilya Kasnacheev :
> >
> >> Hello!
> >>
> >> I have changed the schedule condition so ignite-2.9 will be run instead.
> >> Please check if it works tomorrow.
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> вт, 7 июл. 2020 г. в 16:42, Alex Plehanov :
> >>
> >>> Guys,
> >>>
> >>> Can somebody help with creating scheduled build triggers for nightly
> "Run
> >>> All" on TC for "ignite-2.9" branch?
> >>>
> >>> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
> >>> branch [1]. Do we still need it? Or just forgot to remove it after
> >>> release?
> >>>
> >>> [1] :
> >>>
> >>>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv
> >>>
> >>> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov :
> >>>
> >>> > Anton, thank you.
> >>> >
> >>> > Guys,
> >>> >
> >>> > I've cut the release branch. From now on please pin resolved in the
> >>> master
> >>> > branch tickets to 2.10 release in Jira and cherry-pick targeted to
> 2.9
> >>> > tickets to ignite-2.9 branch.
> >>> >
> >>> > As far as the release branch cut was delayed, I propose to move code
> >>> > freeze dates by one week (to 17 July 2020). WDYT?
> >>> >
> >>> > I've moved long-time inactive non-blocker tickets (except
> documentation
> >>> > related, we will deal with them later) from 2.9 release, please check
> >>> your
> >>> > Jira issues to have the correct "Fix version" field if your ticket is
> >>> > planned to 2.9 release.
> >>> >
> >>> > All currently pinned to 2.9 issues can be found on the release page
> >>> [1].
> >>> >
> >>> > I didn't get about [2] ticket mentioned in this thread, are we going
> to
> >>> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
> >>> clarify?
> >>> >
> >>> > [1]:
> >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >>> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
> >>> >
> >>> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov :
> >>> >
> >>> >> You're now at the "Ignite Release Managers" group.
> >>> >> Please check you gain access.
> >>> >>
> >>> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <
> >>> plehanov.a...@gmail.com>
> >>> >> wrote:
> >>> >>
> >>> >> > Guys,
> >>> >> >
> >>> >> > I've created the 2.9 release confluence page [1].
> >>> >> > Also, I found that I don't have permission to Team City release
> >>> tasks.
> >>> >> Can
> >>> >> > anyone give me such permissions?
> >>> >> >
> >>> >> > [1]:
> >>> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >>> >> >
> >>> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <
> >>> zaleslaw@gmail.com>:
> >>> >> >
> >>> >> > > Igniters
> >>> >> > >
> >>> >> > > Unfortunately, the ML model export/import feature
> >>> >> > >  is under
> >>> >> development
> >>> >> > > yet.
> >>> >> > > I need to delay it before the 2.10 release.
> >>> >> > >
> >>> >> > >
> >>> >> > >
> >>> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <
> >>> plehanov.a...@gmail.com>:
> >>> >> > >
> >>> >> > > > Denis,
> >>> >> > > >
> >>> >> > > > Yes, I still ready to manage it.
> >>> >> > > > Today I will prepare a release page on wiki and will try to go
> >>> over
> >>> >> > > tickets
> >>> >> > > > list.
> >>> >> > > > Also, I have plans to cut the branch by the end of next week
> if
> >>> >> there
> >>> >> > are
> >>> >> > > > no objections.
> >>> >> > > >
> >>> >> > > >
> >>> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda :
> >>> >> > > >
> >>> >> > > > > Igniters,
> >>> >> > > > >
> >>> >> > > > > Are we moving forward with this release? Alex Plehanov, are
> >>> you
> >>> >> still
> >>> >> > > > ready
> >>> >> > > > > to manage it? It seems like everyone agreed with the
> timeline
> >>> you
> >>> >> > > > proposed
> >>> >> > > > > in the very beginning.
> >>> >> > > > >
> >>> >> > > > > -
> >>> >> > > > > Denis
> >>> >> > > > >
> >>> >> > > > >
> >>> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <
> >>> dma...@apache.org>
> >>> >> > wrote:
> >>> >> > > > >
> >>> >> > > > > > Sergey, Ivan,
> >>> >> > > > > >
> >>> >> > > > > > Could you please check the questions below? If it's
> >>> >> time-consuming
> >>> >> > to
> >>> >> > > > > > rework continuous queries, then the new mode can become
> >>> >> available
> >>> >> > in
> >>> >> > > > the
> >>> >> > > > > > experimental state and should not let register continuous
> >>> >> queries
>

[jira] [Created] (IGNITE-13250) Use descriptive thread names for async file channels

[Nikita Tolstunov (Jira)]

Nikita Tolstunov created IGNITE-13250:
-

 Summary: Use descriptive thread names for async file channels
 Key: IGNITE-13250
 URL: https://issues.apache.org/jira/browse/IGNITE-13250
 Project: Ignite
  Issue Type: Bug
Reporter: Nikita Tolstunov
Assignee: Nikita Tolstunov


At now we have several async file channels which don't use any thread naming 
notation in their executor services, this causes some troubles identifying 
what's happening if you have a thread dump only.



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

[jira] [Created] (IGNITE-13251) Deadlock between grid-timeout-worker and a thread opening a communication connection.

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-13251:


 Summary: Deadlock between grid-timeout-worker and a thread opening 
a communication connection.
 Key: IGNITE-13251
 URL: https://issues.apache.org/jira/browse/IGNITE-13251
 Project: Ignite
  Issue Type: Bug
Reporter: Alexander Lapin


rid-timeout-worker is known to go into a deadlock state with other threads in a 
few scenarios.

The general scheme is:
1. A thread `T` is holding lock `L` and is trying to establish a communication 
connection, hanging in `safeTcpHandshake` method. Due to the logic of 
`safeTcpHandshake`, `grid-timeout-worker` needs to send a signal to `T` in 
order for it to proceed.

2. `grid-timeout-worker` is trying to acquire `L`. Hence, the deadlock.

It may include more threads. The lock `L` can be different: checkpoint lock, 
GridCacheMapEntry lock, etc.
 #  

 ## Example

The below example shows a lock between
 * `grid-timeout-worker` trying to acquire a cp read lock in a 
`dumpLongRunningTransactions`

 * `tcp-comm-worker` trying to establish a connection but hanging on socket 
read due to unstable network

 * checkpointer trying to start a checkpoint and acquire cp write lock

 * `utility` worker waiting for the connection to be established by 
`tcp-comm-worker` while holding cp read lock

{code:java}
Thread [name="grid-timeout-worker-#23", id=42, state=WAITING, blockCnt=6991, 
waitCnt=1746467]
Lock 
[object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@4545a8b9, 
ownerName=null, ownerId=-1]
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at 
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
at 
o.a.i.i.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1707)
at 
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:715)
at 
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:511)
at 
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.tryLocalGet(GridPartitionedSingleGetFuture.java:399)
at 
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:366)
at 
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:243)
at 
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:232)
at 
o.a.i.i.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:246)
at 
o.a.i.i.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4190)
at 
o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4171)
at 
o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1362)
at 
o.a.i.i.processors.task.GridTaskProcessor.saveTaskMetadata(GridTaskProcessor.java:908)
at 
o.a.i.i.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:746)
at 
o.a.i.i.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:477)
at 
o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:674)
at 
o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:479)
at o.a.i.i.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
at o.a.i.i.IgniteComputeImpl.callAsync(IgniteComputeImpl.java:794)
at 
o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningTransaction(GridCachePartitionExchangeManager.java:2115)
at 
o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations0(GridCachePartitionExchangeManager.java:2012)
- locked 
o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ActionLimiter@47b86e8f
at 
o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations(GridCachePartitionExchangeManager.java:2180)
at o.a.i.i.IgniteKernal$4.run(IgniteKernal.java:1478)
at 
o.a.i.i.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:410)
- locked 
o.a.i.i.processors.timeout.GridTimeoutProcessor$CancelableTask@67c951c7
at 
o.a.i.i.process

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

[Dmitriy Pavlov]

Hi Folks,

I've just found our doc still point and recommend using it.

I suggest removing the automatic RDBMS import option from Cache-Store
documentation:
https://apacheignite.readme.io/docs/3rd-party-store#automatic

Sincerely
Dmitriy Pavlov

ср, 20 мая 2020 г. в 01:49, Denis Magda :

> Igniters,
>
> The vote is over [1] with a decision to phase out Ignite Web Console by
> moving to a separate repository and stopping its development/maintenance
> officially. The following PMC members cast +1 binding votes:
>
>- Saikat Maitra
>- Alexey Zinoviev
>- Nikolay Izhikov
>
> There are no -1 votes thus we can proceed with the tool discontinuation
> procedure [2].
>
> [1]
>
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Stop-Maintenance-of-Ignite-WebConsole-td47451.html
> [2] https://issues.apache.org/jira/browse/IGNITE-13038
>
> -
> Denis
>

[jira] [Created] (IGNITE-13252) Provide the ability to cache strings

[Amelchev Nikita (Jira)]

Amelchev Nikita created IGNITE-13252:


 Summary: Provide the ability to cache strings
 Key: IGNITE-13252
 URL: https://issues.apache.org/jira/browse/IGNITE-13252
 Project: Ignite
  Issue Type: Sub-task
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita


Strings that performance statistics writes can be cached with id. It will 
reduce affect on performance.



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

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[Alexey Kuznetsov]

Alex,

Can you cherry-pick to Ignite 2.9 this issue:
https://issues.apache.org/jira/browse/IGNITE-13246 ?

This issue is about BASELINE events and it is very useful for notification
external tools about changes in baseline.

Thank you!

---
Alexey Kuznetsov