[jira] [Created] (IGNITE-13786) PDS defragmentation can inflate index size

[Ivan Bessonov (Jira)]

Ivan Bessonov created IGNITE-13786:
--

 Summary: PDS defragmentation can inflate index size
 Key: IGNITE-13786
 URL: https://issues.apache.org/jira/browse/IGNITE-13786
 Project: Ignite
  Issue Type: Bug
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov


For huge caches it is possible that defragmentation will lead to bigger indexes 
size.

The reason is that we only append new data to index trees and never insert into 
the middle, this leads to under-utilization of B+Tree pages space.



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

Re: Migrating NodeJS client to TypeScript

[Данилов Семён]

Yes, TS compiler produces JS files and TS-typings. Users that are already using 
JS version will have a seamless migration. Note: we'll have to publish compiled 
JS files along with typings.
 
-
Semyon.

01.12.2020, 09:59, "Ivan Daschinsky" :
>>  Is there any value in keeping both versions - the plain JavaScript one
>
> and the TypeScript specific
> Hi! No, there is no value. TS sources should be transpiled to JS before
> execution.
>
> вт, 1 дек. 2020 г. в 01:31, Denis Magda :
>
>>  Hi Semyon,
>>
>>  Is there any value in keeping both versions - the plain JavaScript one and
>>  the TypeScript specific?
>>
>>  -
>>  Denis
>>
>>  On Mon, Nov 30, 2020 at 12:16 PM Данилов Семён  wrote:
>>
>>  > Hello Igniters!
>>  >
>>  > I'd like to propose a big change for the nodejs thin client: a full
>>  > rewrite from JavaScript to TypeScript.
>>  >
>>  > Strong typing will not only help us in future while developing new
>>  > features, but will also indicate existing type inconsistencies (I know
>>  > there is a couple).
>>  > Also, we will have out of the box types for API documentation, which is
>>  > very handy for users.
>>  >
>>  > So what do you think?
>>  >
>>  > Kind regards,
>>  > Semyon.
>>  >
>
> --
> Sincerely yours, Ivan Daschinskiy

[RESULT][VOTE] Release Apache Ignite Streaming extensions 1.0.0 RC1

[Alexey Goncharuk]

The vote is closed now.

Vote result: Vote passed with 5 "+1" votes (3 binding and 2 non-binding
votes), no "0" and no "-1" votes.

+1 Votes:
Denis Magda (binding)
Saikat Maitra (binding)
Andrey Gura (binding)
Kirill Tkalenko
Konstantin Orlov

Vote thread
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-EXTENSION-Release-Apache-Ignite-Streaming-extensions-1-0-0-RC1-td50268.html

Re: Re[2]: 2.9.1 release scope and dates

[Yaroslav Molochkov]

Hi!
I see it's merged into 2.9.1 branch and master.

I guess that's it for the issues, I will run nightly tests again just to be
sure that everything is okay and we will proceed.

On Mon, Nov 30, 2020 at 7:31 PM Zhenya Stanilovsky
 wrote:

>
> hello !
> seems it [1] need to be included too, if it`s not too late, of course. May
> be you can bump reviewer somehow?)
>
> [1]  https://issues.apache.org/jira/browse/IGNITE-13765
>
> >Ivan, it's added, thanks for pointing that out
> >
> >On Mon, Nov 30, 2020 at 5:44 PM Ivan Daschinsky < ivanda...@gmail.com >
> wrote:
> >
> >> Yaroslav, could you explain why you decided to remove from scope
> >>  https://issues.apache.org/jira/browse/IGNITE-13699 ?
> >> This ticket also incorporate few fixes for metrics. Currently metrics
> is a
> >> little bit broken (JoinedCount shows invalid results for example)
> >>
> >>
> >> пн, 30 нояб. 2020 г. в 17:26, Yaroslav Molochkov <
> molochko...@gmail.com >:
> >>
> >> > Igniters, hello!
> >> >
> >> > First of all, sorry that the release process is taking so long.
> >> >
> >> > Secondly, the release build seems stable and no blockers were
> introduced
> >> > within that list
> >> > <
> >> >
> >>
> https://issues.apache.org/jira/browse/IGNITE-11312?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1%20and%20status%20%3D%20Resolved
> >> > >
> >> > (at
> >> > least on RunAll compared to 2.9)
> >> >
> >> > I've also prepared release notes:
> >> >
> >> > Ignite Core:
> >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi
> >> > * Added System view for binary metadata
> >> > * Added System view for metastorage items
> >> > * Added RebalancingPartitionsTotal metrics
> >> > * Improved checkpoint concurrent behaviour
> >> > * Fixed critical system error when unregister a JMX bean
> >> > * Fixed IgniteCache#isClosed() returns false on server node even if
> >> > the cache had been closed before
> >> > * Fixed inability to eagerly remove expired cache entries
> >> > * Fixed partial index rebuild issue in case indexed cache contains
> >> > different datatypes
> >> > * Fixed local metastorage system view error if unmarshallable values
> >> > present
> >> > * Fixed deadlock between grid-timeout-worker and a thread opening a
> >> > communication connection
> >> > * Fixed deadlock in IgniteServiceProcessor
> >> > * Fixed issue when rebalance future might hang in no final state
> >> > though all partitions are owned
> >> > * Fixed issue when scan query fails with an assertion error:
> Unexpected
> >> > row key
> >> > * Fixed issue with archiving and enabled wal compaction setting on
> >> > server restart
> >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE
> strategy
> >> > * Fixed synchronization problems when different classloaders are used
> >> > for deployment of same class
> >> > * Fixed exception on SQL caches when client reconnect
> >> > * Fixed deadlock on multiple cache delete
> >> > * Fixed NPE in IgniteServiceProcessor when destroying a cache
> >> > * Fixed issue when DurableBackgroundTask can abandon incomplete task
> >> > * Fixed issue related to cache interceptor deserialization on client
> >> nodes
> >> > * Fixed issue when control.sh doesn't start if JMX port was set
> >> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can
> >> > return invalid node as coordinator
> >> > * Fixed issue when valid blocking section in GridNioWorker and
> >> > GridNioClientWorker leads to false positive blocking thread detection
> >> > * Fixed several logging issues
> >> > * Fixed issue when exchange worker, waiting for new task from queue,
> >> > considered as blocked
> >> > * Fixed incorrect topology snapshot logger output about coordinator
> >> change
> >> > * Fixed slowdown during node initialization
> >> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal
> >> > and SystemViewMBean classes
> >> > * Removed unnecessary dependency to curator-client from and improved
> >> > ZookeeperDiscoverySpi
> >> > * Removed unnecessary failure trace in IgnitionEx
> >> >
> >> > Java thin-client:
> >> > * Fixed issue when thin client connect/disconnect during topology
> >> > update may lead to partition divergence in ignite-sys-cache
> >> > * Fixed issue when thin client silently closes channel after
> inactivity
> >> > * Fixed unsupported protocol version exception when getting cache
> >> > configuration from Java thin client
> >> >
> >> > JDBC:
> >> > * Fixed thin driver reports incorrect property names
> >> > * Updated JDBC metadata to match actual capabilities
> >> >
> >> > Ignite .NET:
> >> > * Improved slow Enum serialization
> >> > * Fixed issue when deserializing IBinaryObject containing an
> >> > IBinaryObject field fails
> >> > * Fixed issue TransactionImpl finalizer can crash the process
> >> > * Fixed child processes become zombies when persistence is used with
> >> > direct-io on Linux
> >> >
> >> > Ignite C++:
> >> > * Fixed issue when odbc-example loses values if run with 1 a

[jira] [Created] (IGNITE-13787) Init module must ask about ignite-work/ignite-bin paths

[Kirill Gusakov (Jira)]

Kirill Gusakov created IGNITE-13787:
---

 Summary: Init module must ask about ignite-work/ignite-bin paths
 Key: IGNITE-13787
 URL: https://issues.apache.org/jira/browse/IGNITE-13787
 Project: Ignite
  Issue Type: Sub-task
Reporter: Kirill Gusakov


If the user executes "module init" on a fresh machine, a prompt about suggested 
dirs should be provided. By default will be used ~/ignite-work and ~/ignite-bin



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

[jira] [Created] (IGNITE-13788) Additional maven repos must be supported for modules installation

[Kirill Gusakov (Jira)]

Kirill Gusakov created IGNITE-13788:
---

 Summary: Additional maven repos must be supported for modules 
installation
 Key: IGNITE-13788
 URL: https://issues.apache.org/jira/browse/IGNITE-13788
 Project: Ignite
  Issue Type: Sub-task
Reporter: Kirill Gusakov






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

[jira] [Created] (IGNITE-13789) Add 2.9.0 version to ducktape tests

[Maksim Timonin (Jira)]

Maksim Timonin created IGNITE-13789:
---

 Summary: Add 2.9.0 version to ducktape tests
 Key: IGNITE-13789
 URL: https://issues.apache.org/jira/browse/IGNITE-13789
 Project: Ignite
  Issue Type: New Feature
Reporter: Maksim Timonin
Assignee: Mikhail Filatov


Changes should be in:
 # docker
 # version.py
 # some existed tests?



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

[GitHub] [ignite-3] kgusakov closed pull request #3: IGNITE-13610 WIP Initial version of unified CLI tool

[GitBox]

kgusakov closed pull request #3:
URL: https://github.com/apache/ignite-3/pull/3


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (IGNITE-13790) Configured detection timeout at cellular switch test

[Anton Vinogradov (Jira)]

Anton Vinogradov created IGNITE-13790:
-

 Summary: Configured detection timeout at cellular switch test
 Key: IGNITE-13790
 URL: https://issues.apache.org/jira/browse/IGNITE-13790
 Project: Ignite
  Issue Type: Improvement
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov






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

[jira] [Created] (IGNITE-13791) NullPointerException when topology is unstable

[Pavel Vinokurov (Jira)]

Pavel Vinokurov created IGNITE-13791:


 Summary: NullPointerException when topology is unstable 
 Key: IGNITE-13791
 URL: https://issues.apache.org/jira/browse/IGNITE-13791
 Project: Ignite
  Issue Type: Bug
  Components: networking
Affects Versions: 2.9.1
Reporter: Pavel Vinokurov
 Attachments: UnstableServerTopology.java

Unstable topology with blinking server nodes leads to the critical system error:

{code:java}
SEVERE: Critical system error detected. Will be handled accordingly to 
configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, 
err=java.lang.NullPointerException]]
java.lang.NullPointerException
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:5096)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:3236)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2915)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:8064)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:3086)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7995)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)

Dec 01, 2020 8:22:55 PM java.util.logging.LogManager$RootLogger log
SEVERE: JVM will be halted immediately due to the failure: 
[failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, 
err=java.lang.NullPointerException]]
{code}




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

[jira] [Created] (IGNITE-13792) Reconnecting clients trigger failure handler

[Pavel Vinokurov (Jira)]

Pavel Vinokurov created IGNITE-13792:


 Summary: Reconnecting clients trigger failure handler
 Key: IGNITE-13792
 URL: https://issues.apache.org/jira/browse/IGNITE-13792
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.9
Reporter: Pavel Vinokurov
 Attachments: UnstableClients.java


{code:java}
Dec 01, 2020 9:38:29 PM java.util.logging.LogManager$RootLogger log
SEVERE: JVM will be halted immediately due to the failure: 
[failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class 
o.a.i.IgniteCheckedException: Affinity for topology version is not initialized 
[locNode=b50635ff-0324-431b-bc34-00a6cd36c9e3, grp=ignite-sys-cache, 
topVer=AffinityTopologyVersion [topVer=570, minorTopVer=0], 
head=AffinityTopologyVersion [topVer=569, minorTopVer=0], 
history=[AffinityTopologyVersion [topVer=551, minorTopVer=0], 
AffinityTopologyVersion [topVer=552, minorTopVer=0], AffinityTopologyVersion 
[topVer=553, minorTopVer=0], AffinityTopologyVersion [topVer=554, 
minorTopVer=0], AffinityTopologyVersion [topVer=555, minorTopVer=0], 
AffinityTopologyVersion [topVer=556, minorTopVer=0], AffinityTopologyVersion 
[topVer=557, minorTopVer=0], AffinityTopologyVersion [topVer=558, 
minorTopVer=0], AffinityTopologyVersion [topVer=559, minorTopVer=0], 
AffinityTopologyVersion [topVer=560, minorTopVer=0], AffinityTopologyVersion 
[topVer=561, minorTopVer=0], AffinityTopologyVersion [topVer=562, 
minorTopVer=0], AffinityTopologyVersion [topVer=563, minorTopVer=0], 
AffinityTopologyVersion [topVer=564, minorTopVer=0], AffinityTopologyVersion 
[topVer=565, minorTopVer=0], AffinityTopologyVersion [topVer=566, 
minorTopVer=0], AffinityTopologyVersion [topVer=567, minorTopVer=0], 
AffinityTopologyVersion [topVer=568, minorTopVer=0], AffinityTopologyVersion 
[topVer=569, minorTopVer=0]
{code}




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

Review needed: IGNITE-13572, Duplicates in select query during partition eviction for caches with 0 backups

[Konstantin Sirotkin]

Hi!

Please review the changes.

https://issues.apache.org/jira/browse/IGNITE-13572 


Thanks!

---
Best regards,
Konstantin Sirotkin | Senior Java Developer

[GitHub] [ignite-nodejs-thin-client] SammyVimes opened a new pull request #1: IGNITE-11032 Move to TypeScript

[GitBox]

SammyVimes opened a new pull request #1:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/1


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Re[2]: 2.9.1 release scope and dates

[Yaroslav Molochkov]

Guys,

can anyone grant me necessary permissions to create a wiki page with
release info, please?

On Tue, Dec 1, 2020 at 12:58 PM Yaroslav Molochkov 
wrote:

> Hi!
> I see it's merged into 2.9.1 branch and master.
>
> I guess that's it for the issues, I will run nightly tests again just to
> be sure that everything is okay and we will proceed.
>
> On Mon, Nov 30, 2020 at 7:31 PM Zhenya Stanilovsky
>  wrote:
>
>>
>> hello !
>> seems it [1] need to be included too, if it`s not too late, of course.
>> May be you can bump reviewer somehow?)
>>
>> [1]  https://issues.apache.org/jira/browse/IGNITE-13765
>>
>> >Ivan, it's added, thanks for pointing that out
>> >
>> >On Mon, Nov 30, 2020 at 5:44 PM Ivan Daschinsky < ivanda...@gmail.com >
>> wrote:
>> >
>> >> Yaroslav, could you explain why you decided to remove from scope
>> >>  https://issues.apache.org/jira/browse/IGNITE-13699 ?
>> >> This ticket also incorporate few fixes for metrics. Currently metrics
>> is a
>> >> little bit broken (JoinedCount shows invalid results for example)
>> >>
>> >>
>> >> пн, 30 нояб. 2020 г. в 17:26, Yaroslav Molochkov <
>> molochko...@gmail.com >:
>> >>
>> >> > Igniters, hello!
>> >> >
>> >> > First of all, sorry that the release process is taking so long.
>> >> >
>> >> > Secondly, the release build seems stable and no blockers were
>> introduced
>> >> > within that list
>> >> > <
>> >> >
>> >>
>> https://issues.apache.org/jira/browse/IGNITE-11312?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1%20and%20status%20%3D%20Resolved
>> >> > >
>> >> > (at
>> >> > least on RunAll compared to 2.9)
>> >> >
>> >> > I've also prepared release notes:
>> >> >
>> >> > Ignite Core:
>> >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi
>> >> > * Added System view for binary metadata
>> >> > * Added System view for metastorage items
>> >> > * Added RebalancingPartitionsTotal metrics
>> >> > * Improved checkpoint concurrent behaviour
>> >> > * Fixed critical system error when unregister a JMX bean
>> >> > * Fixed IgniteCache#isClosed() returns false on server node even if
>> >> > the cache had been closed before
>> >> > * Fixed inability to eagerly remove expired cache entries
>> >> > * Fixed partial index rebuild issue in case indexed cache contains
>> >> > different datatypes
>> >> > * Fixed local metastorage system view error if unmarshallable values
>> >> > present
>> >> > * Fixed deadlock between grid-timeout-worker and a thread opening a
>> >> > communication connection
>> >> > * Fixed deadlock in IgniteServiceProcessor
>> >> > * Fixed issue when rebalance future might hang in no final state
>> >> > though all partitions are owned
>> >> > * Fixed issue when scan query fails with an assertion error:
>> Unexpected
>> >> > row key
>> >> > * Fixed issue with archiving and enabled wal compaction setting on
>> >> > server restart
>> >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE
>> strategy
>> >> > * Fixed synchronization problems when different classloaders are used
>> >> > for deployment of same class
>> >> > * Fixed exception on SQL caches when client reconnect
>> >> > * Fixed deadlock on multiple cache delete
>> >> > * Fixed NPE in IgniteServiceProcessor when destroying a cache
>> >> > * Fixed issue when DurableBackgroundTask can abandon incomplete task
>> >> > * Fixed issue related to cache interceptor deserialization on client
>> >> nodes
>> >> > * Fixed issue when control.sh doesn't start if JMX port was set
>> >> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can
>> >> > return invalid node as coordinator
>> >> > * Fixed issue when valid blocking section in GridNioWorker and
>> >> > GridNioClientWorker leads to false positive blocking thread detection
>> >> > * Fixed several logging issues
>> >> > * Fixed issue when exchange worker, waiting for new task from queue,
>> >> > considered as blocked
>> >> > * Fixed incorrect topology snapshot logger output about coordinator
>> >> change
>> >> > * Fixed slowdown during node initialization
>> >> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal
>> >> > and SystemViewMBean classes
>> >> > * Removed unnecessary dependency to curator-client from and improved
>> >> > ZookeeperDiscoverySpi
>> >> > * Removed unnecessary failure trace in IgnitionEx
>> >> >
>> >> > Java thin-client:
>> >> > * Fixed issue when thin client connect/disconnect during topology
>> >> > update may lead to partition divergence in ignite-sys-cache
>> >> > * Fixed issue when thin client silently closes channel after
>> inactivity
>> >> > * Fixed unsupported protocol version exception when getting cache
>> >> > configuration from Java thin client
>> >> >
>> >> > JDBC:
>> >> > * Fixed thin driver reports incorrect property names
>> >> > * Updated JDBC metadata to match actual capabilities
>> >> >
>> >> > Ignite .NET:
>> >> > * Improved slow Enum serialization
>> >> > * Fixed issue when deserializing IBinaryObject containing an
>> >> > IBinaryObj