[GitHub] ignite pull request #4629: IGNITE-9382 Fixed data handling for multiple chun...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Apache Ignite 2.7 release

[Roman Shtykh]

Igniters,
I would like Mesos integration update be included in the upcoming release.Can 
anyone review prs for the following issues?
IGNITE-9388: mesos IgniteProvider tries to access obsolete ignite.run or 
download from slow archiveIGNITE-9408: Update mesos version

Roman Shtykh 

On Thursday, August 30, 2018, 9:25:43 p.m. GMT+9, Vyacheslav Daradur 
 wrote:  
 
 Hi Igniters!

I'm working on the following Service Grid tasks:
- IGNITE-8361 Use discovery messages for service deployment
- IGNITE-8362 Collect service deployment results asynchronously on coordinator
- IGNITE-8363 Handle topology changes during service deployment
- IGNITE-8364 Propagate deployed services to joining nodes
- IGNITE-8365 Introduce service failure events
- IGNITE-3392 Propagate service deployment results from assigned nodes
to initiator

Let's call them *phase 1* because the should be implemented together
(atomically).

I do my best to finish phase 1 for including to 2.7 release.

But I'm not sure that the solution will be fully completed till the
beginning of October.

On Wed, Aug 29, 2018 at 7:18 PM Nikolay Izhikov  wrote:
>
> Hell, Yakov
>
> I'm ok with your proposal.
>
>        * Scope freeze - September 17 - We should have a full list of tickets 
>for 2.7 here.
>        * Code freeze - October 01 - We should merge all 2.7 tickets to master 
>here.
>        * Vote on RC1 - October 11.
>        * Vote on release - October 15.
>
> В Ср, 29/08/2018 в 12:39 +0300, Yakov Zhdanov пишет:
> > Nikolay,
> >
> > I think we should have 2 weeks after code freeze which by the way may
> > include RC1 voting stage. This way I would like us to agree that release
> > candidate should be sent to vote on Oct, 11th and we can release on Oct,
> > 15th.
> >
> > What do you think?
> >
> > --Yakov



-- 
Best Regards, Vyacheslav D.  

[GitHub] ignite pull request #3871: IGNITE-8286: ScanQuery ignore setLocal with non l...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Compression prototype

[Dmitriy Setrakyan]

Hi Ilya,

This is very useful. Is the compression going to be per-page, in which case
the dictionary is going to be kept inside of a page? Or do you have some
other design in mind?

D.

On Mon, Sep 3, 2018 at 10:36 AM, Ilya Kasnacheev 
wrote:

> Hello again!
>
> I've been running various compression parameters through cod dataset.
>
> It looks like the best compression level in terms of speed is either 1 or
> 2.
> The default for Zstd seems to be 3 which would almost always perform worse.
> For best performance a dictionary of 1024 is optimal, for better
> compression
> one might choose larger dictionaries, 6k looks good but I will also run a
> few benchmarks on larger dicts. Unfortunately, Zstd crashes if sample size
> is set to more than 16k entries (I guess I should probe the max buffer size
> where problems begin).
>
> I'm attaching two charts which show what's we've got. Compression rate is a
> fraction of original records size. Time to run is wall clock time the test
> run. Reasonable compression will increase the run time twofold (of a
> program
> that only does text record parsing -> creates objects -> binarylizes them
> ->
> compresses -> decompresses). Notation: s{number of bin objects used to
> train}-d{dictionary length in bytes}-l{compression level}.
>  com/file/t374/chart1.png>
> Second one is basically a zoom in on the first.
>  com/file/t374/chart2.png>
> I think that in additional to dictionary compression we should have
> dictionary-less compression. On typical data of small records it shows
> compression rate of 0.8 ~ 0.65, but I can imagine that with larger
> unstructured records it can be as good as dict-based and much less of a
> hassle dictionary-processing-wise. WDYT?
> Sorry for the fine prints. I hope my charts will visible.
>
> You can see the updated code as pull request:
> https://github.com/apache/ignite/pull/4673
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #4675: IGNITE-9458: Changed behaviour of --mvcc flag in ...

[pavel-kuznetsov]

GitHub user pavel-kuznetsov opened a pull request:

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

IGNITE-9458: Changed behaviour of --mvcc flag in benchmark server.

Don't override ignite config's "mvccEnabled" property in benchmark server.

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

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

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

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


commit 2c69fbe538f66497a5b6cc1a1ac8900bd7efb7ef
Author: Pavel Kuznetsov 
Date:   2018-09-03T18:37:20Z

IGNITE-9458: Changed behaviour of --mvcc flag in benchmark server.




---

[jira] [Created] (IGNITE-9458) SQL benchmarks: absence of "--mvcc" benchmark flag should not overwrite config values

[Pavel Kuznetsov (JIRA)]

Pavel Kuznetsov created IGNITE-9458:
---

 Summary: SQL benchmarks: absence of "--mvcc" benchmark flag should 
not overwrite config values
 Key: IGNITE-9458
 URL: https://issues.apache.org/jira/browse/IGNITE-9458
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kuznetsov






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

Re: Compression prototype

[Ilya Kasnacheev]

Hello again!

I've been running various compression parameters through cod dataset.

It looks like the best compression level in terms of speed is either 1 or 2.
The default for Zstd seems to be 3 which would almost always perform worse.
For best performance a dictionary of 1024 is optimal, for better compression
one might choose larger dictionaries, 6k looks good but I will also run a
few benchmarks on larger dicts. Unfortunately, Zstd crashes if sample size
is set to more than 16k entries (I guess I should probe the max buffer size
where problems begin).

I'm attaching two charts which show what's we've got. Compression rate is a
fraction of original records size. Time to run is wall clock time the test
run. Reasonable compression will increase the run time twofold (of a program
that only does text record parsing -> creates objects -> binarylizes them ->
compresses -> decompresses). Notation: s{number of bin objects used to
train}-d{dictionary length in bytes}-l{compression level}.
 
Second one is basically a zoom in on the first.
 
I think that in additional to dictionary compression we should have
dictionary-less compression. On typical data of small records it shows
compression rate of 0.8 ~ 0.65, but I can imagine that with larger
unstructured records it can be as good as dict-based and much less of a
hassle dictionary-processing-wise. WDYT?
Sorry for the fine prints. I hope my charts will visible.

You can see the updated code as pull request:
https://github.com/apache/ignite/pull/4673

Regards,



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4647: IGNITE-9425 - Fix NPE on index rebuild

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Zookeeper mass timeouts

[Alexey Goncharuk]

Dmitriy,

The zookeeper timeouts were caused by my commit (I looked through the wrong
PR when was checking tests), already reverted from master.

As for the bot, does it already have the logic to detect continuous
timeouts and send notification only after a successful run? If not, I guess
we should put it on our helper roadmap because this will not be the last
timeout change.

--AG

вс, 2 сент. 2018 г. в 10:11, Dmitriy Pavlov :

> Hi,
>
> First of all I apologize for mass emails came from zookeeper timeout
> failures.
>
> Both failures and the bot should be researched. I believe we can improve
> the bot notification rules to avoid mass emails in case of flaky timeouts.
>
> I believe it is better solution to make rules perfect instated of creating
> separate channel.
>
> Sincerely,
> Dmitriy Pavlov
>

[GitHub] ignite pull request #4674: IGNITE-9419 Async wait for caches registration an...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-9419 Async wait for caches registration and save during PME.



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

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

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

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


commit 410a9a944f7cc98388b4c2bfa97a88f424a32c07
Author: Pavel Kovalenko 
Date:   2018-09-03T16:50:29Z

IGNITE-9419 Async wait for caches registration and save during PME.




---

Re: Failed to activate node components

[Ilya Kasnacheev]

Hello!

Whoa, you certainly should not get a JVM crash in this case. Can you please
attach your XML config (as a file)? I will fill an issue if able to
reproduce.

Regards,
-- 
Ilya Kasnacheev


пн, 3 сент. 2018 г. в 18:19, wt :

> I am getting the following error when starting a single node cluster
> (intellij) and then the instance crashes. I did have some persistence
> issues
> so cleaned up the work dir after which this started happening
>
> ignite-5885b9e6.log
> <
> http://apache-ignite-developers.2346864.n4.nabble.com/file/t604/ignite-5885b9e6.log>
>
>
> console output:
>
> "C:\Program Files\Java\jdk1.8.0_151\bin\java" "-javaagent:C:\Program
> Files\JetBrains\IntelliJ IDEA Community Edition
> 2017.3\lib\idea_rt.jar=51505:C:\Program Files\JetBrains\IntelliJ IDEA
> Community Edition 2017.3\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\charsets.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\deploy.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\access-bridge-64.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\cldrdata.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\dnsns.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\jaccess.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\jfxrt.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\localedata.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\nashorn.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\sunec.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\sunjce_provider.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\sunmscapi.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\sunpkcs11.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\ext\zipfs.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\javaws.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\jce.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\jfr.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\jfxswt.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\jsse.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\management-agent.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\plugin.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\resources.jar;C:\Program
> Files\Java\jdk1.8.0_151\jre\lib\rt.jar;C:\Program
>
> 

Re: Ignition.loadSpringBean("POC5-server.xml","grid.cfg") - error Failed to activate node components

[Ilya Kasnacheev]

Hello!

Obviously, your Ignite depends on other Spring beans, which are NOT loaded
alongside grid configuration in this case.

Move them to another spring context, start it first, and then use
IgnitionEx#start(IgniteConfiguration, GridSpringResourceContext).

.. or have your own Ignite Spring bean that does configuration modification
before starting Ignite.
-- 
Ilya Kasnacheev


пн, 3 сент. 2018 г. в 18:18, wt :

> I have a project that starts fine if i start it like this
>
> Ignite ig = Ignition.start("POC5-server.xml");
> ig.cluster().active(true);
>
> I need to however use the config file and also set other details before
> starting so When i do this i get an error:
>
> IgniteConfiguration cfg =
> Ignition.loadSpringBean("POC5-server.xml","grid.cfg");
> --set other things here (they are commented out in the code for now)
> Ignite ig =Ignition.start(cfg);
> ig.cluster().active(true);
>
> here is the error in the log file:
>
>
>
> [2018-09-03 14:20:18,866][INFO ][main][IgniteKernal%POC5]
>
> >>>__  
> >>>   /  _/ ___/ |/ /  _/_  __/ __/
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 2.6.0#20180710-sha1:669feacc
> >>> 2018 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
>
> [2018-09-03 14:20:18,882][INFO ][main][IgniteKernal%POC5] Config URL: n/a
> [2018-09-03 14:20:18,898][INFO ][main][IgniteKernal%POC5]
> IgniteConfiguration [igniteInstanceName=POC5, pubPoolSize=8, svcPoolSize=8,
> callbackPoolSize=8, stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4,
> igfsPoolSize=2, dataStreamerPoolSize=8, utilityCachePoolSize=8,
> utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8,
> igniteHome=c:\ignite\, igniteWorkDir=c:\ignite\work,
> mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@23529fee,
> nodeId=b36055b7-426d-4975-bf5b-cb54fbb06dbc,
> marsh=org.apache.ignite.internal.binary.BinaryMarshaller@3c73951,
> marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000,
> sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1,
> metricsUpdateFreq=2000, metricsExpTime=9223372036854775807,
> discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=0, ackTimeout=0,
> marsh=null, reconCnt=10, reconDelay=2000, maxAckTimeout=60,
> forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null],
> segPlc=STOP, segResolveAttempts=2, waitForSegOnStart=true,
> allResolversPassReq=true, segChkFreq=1, commSpi=TcpCommunicationSpi
> [connectGate=null, connPlc=null, enableForcibleNodeKill=false,
> enableTroubleshootingLog=false,
>
> srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@32b260fa
> ,
> locAddr=null, locHost=null, locPort=47100, locPortRange=100, shmemPort=-1,
> directBuf=true, directSndBuf=false, idleConnTimeout=60,
> connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768,
> sockRcvBuf=32768, msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null,
> shmemSrv=null, usePairedConnections=false, connectionsPerNode=1,
> tcpNoDelay=true, filterReachableAddresses=false, ackSndThreshold=32,
> unackedMsgsBufSize=0, sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1,
> boundTcpShmemPort=-1, selectorsCnt=4, selectorSpins=0, addrRslvr=null,
> ctxInitLatch=java.util.concurrent.CountDownLatch@581ac8a8[Count = 1],
> stopping=false,
>
> metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@6d4e5011
> ],
> evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@57d7f8ca,
> colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null],
> indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@662b4c69,
> addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=1,
> txCfg=org.apache.ignite.configuration.TransactionConfiguration@fa49800,
> cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED,
> p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100,
> timeSrvPortRange=100, failureDetectionTimeout=1,
> clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null,
>
> connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@71238fc2
> ,
> odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration
> [seqReserveSize=1000, cacheMode=PARTITIONED, backups=1, aff=null,
> grpName=null], classLdr=null, sslCtxFactory=null, platformCfg=null,
> binaryCfg=null, memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration
> [sysRegionInitSize=41943040, sysCacheMaxSize=104857600, pageSize=0,
> concLvl=0, dfltDataRegConf=DataRegionConfiguration [name=default,
> maxSize=1073741824, initSize=268435456, swapPath=null,
> pageEvictionMode=DISABLED, evictionThreshold=0.9, emptyPagesPoolSize=100,
> metricsEnabled=false, metricsSubIntervalCount=5,
> metricsRateTimeInterval=6, persistenceEnabled=true,
> checkpointPageBufSize=0], storagePath=null, checkpointFreq=18,
> lockWaitTime=1, checkpointThreads=4, checkpointWriteOrder=SEQUENTIAL,
> walHistSize=20, 

[jira] [Created] (IGNITE-9457) ODBC: Add connection attributes for streaming mode

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9457:
---

 Summary: ODBC: Add connection attributes for streaming mode
 Key: IGNITE-9457
 URL: https://issues.apache.org/jira/browse/IGNITE-9457
 Project: Ignite
  Issue Type: New Feature
  Components: odbc
Reporter: Igor Sapego


Currently, streaming could be enabled only with the \{{set streaming on}} SQL 
statement. Add connection string attributes, so the connection is opened with 
active streaming mode.

Suggested attributes list:

{\{streaming}}

{\{streamingBatchSize}}

{\{streamingFlushFrequency}}

{\{streamingPerNodeBufferSize}}

{\{streamingPerNodeParallelOperations}}

{\{streamingAllowOverwrite}}



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

[GitHub] ignite pull request #4673: Preliminary Binary Object compression with Zstd.

[alamar]

GitHub user alamar opened a pull request:

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

Preliminary Binary Object compression with Zstd.



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-compress-zstd-dict

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

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


commit 90fc26a2042c660b7c07031e42fc8cfd091b4412
Author: Ilya Kasnacheev 
Date:   2018-08-31T15:19:14Z

Preliminary Binary Object compression with Zstd.




---

[jira] [Created] (IGNITE-9456) ODBC: Implement asynchronous writing for streaming

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9456:
---

 Summary: ODBC: Implement asynchronous writing for streaming
 Key: IGNITE-9456
 URL: https://issues.apache.org/jira/browse/IGNITE-9456
 Project: Ignite
  Issue Type: Improvement
  Components: odbc
Reporter: Igor Sapego


Currently, ODBC driver waits for responses to streaming messages it sends to 
the server. Implementation of asynchronous sending of such messages could 
fasten data streaming.



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

[jira] [Created] (IGNITE-9455) Total allocated size memory metric is always zero for metastore data region.

[Pavel Pereslegin (JIRA)]

Pavel Pereslegin created IGNITE-9455:


 Summary: Total allocated size memory metric is always zero for 
metastore data region.
 Key: IGNITE-9455
 URL: https://issues.apache.org/jira/browse/IGNITE-9455
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Pavel Pereslegin


Persistence enabled and metrics for all regions enabled, but total allocated 
size is always zero for metastore data region 
Even if we change NO_OP allocated page tracker to a real page tracker in 
CacheStoreHolder this metric counts incorrectly, because this region is 
recreated,

Reproducer attached.



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

Hello!

[Ivan Bessonov]

I'm new to Ignite and I would like to join Apache Ignite development.
My JIRA's login is ibessonov

Re: Workflow improvement

[Dmitrii Ryabov]

Hi, Dmitriy,

I created a table with possible blockers [1] for the page with the latest
build analysis. Anton K. has reviewed it. Can you check and merge it?

Also, I created a button to notify PR about analisis results [2]. I used
GitHub statuses (example [3]), but to work it needs a token with push
permission. As Apache PMC, can you acquire such token? I think statuses are
much more notable than comments.

[1] https://issues.apache.org/jira/browse/IGNITE-9376
[2] https://issues.apache.org/jira/browse/IGNITE-9377
[3] https://github.com/SomeFire/ignite-teamcity-bot/pulls

2018-08-25 1:04 GMT+03:00 Dmitriy Pavlov :

> Not sure I understood what bot statistic reduction means.
>
> As far as I understood, you also mean locating failure automatically with
> re-runs on specific git revisions (hashes). I found it will be a good
> contribution to TC Bot for both flaky and non-flaky failures detection. E.g
> failure occurred after 10 commits merged to master. How to find out bad
> commit? Automatic location (analog of bisecting, but using TC test) will be
> really helpful. But it is not a simple contribution.
>
> пт, 24 авг. 2018 г. в 18:35, Dmitrii Ryabov :
>
> > Hi, Dmitriy,
> >
> > Good, I'll create tickets for this steps.
> >
> > Stable suites are a good idea, but also we need to do some actions when a
> > flaky test will appear in stable suite of master branch run. To find out
> a
> > guilty commit, we should run previous commits on empty TeamCity's queue.
> > This runs will reduce bot's statistics for the latest commits.
> >
> > 2018-08-24 16:32 GMT+03:00 Dmitriy Pavlov :
> >
> > > Hi Dmitriy,
> > >
> > > Sounds like a plan ;) I totally agree.
> > > Just one proposal: I would like to avoid hiding any test failures. 2
> > > separate tables named 'Possible Blockers' and 'Other failures' should
> be
> > > completely clear. Comment to PR can contain only first category.
> > >
> > > We had a private discussion with Anton K. and he proposed a very
> > > interesting thing, I would like to bring it here. We can add
> > configuration
> > > into TC bot and mark some tests and some suites as 'Known Stable' It
> > means
> > > that suite or test failure should be considered as a blocker for merge
> > > every time it fails, even if fail rate is non-zero. Very first list of
> > such
> > > suites are
> > >  - Build Apache Ignite
> > >  - License check
> > > And tests:
> > >  - .Net API Parity check
> > > Please share your vision.
> > >
> > > Meanwhile, I've updated the TC bot.
> > > - Underlying Apache Ignite DB was refactored to use lower partitions
> > count,
> > > so restart should be faster.
> > > - Now 100 builds are saved as our failure rate statistics basis.
> > Flakiness
> > > border was not changed, so more test now will be considered as flaky.
> > > - Now 4 builds required to be failed or timed out in a row before
> > > notification is sent.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 23 авг. 2018 г. в 17:09, Dmitrii Ryabov :
> > >
> > > > Hi, Dmitriy,
> > > >
> > > > I propose the next steps:
> > > >
> > > > 1. Show current 0% tests in a separate table at the top of the
> analysis
> > > > results page. Thus, we'll see most suspicious (new or very flaky)
> tests
> > > > firstly. Or we can hide other tests under "More >>" button, like top
> > long
> > > > running tests.
> > > > 2. Create a button by clicking on which the info about 0% tests will
> be
> > > > written in the PR.
> > > > 3. Replace button by webhook for TeamCity (for Run All), which will
> > start
> > > > analysis on TCH and write results in the PR.
> > > > 4. ...
> > > >
> > > > What do you think?
> > > >
> > > >
> > > > 2018-08-22 8:55 GMT+03:00 Dmitrii Ryabov :
> > > >
> > > > > I think we should check not N last runs, but all runs in last N
> days.
> > > > >
> > > > > A simple rule to detect flaky fails by hands - get test history
> > ordered
> > > > > by TEST_STATUS_DESC and check its date. As I see, we can get list
> of
> > > > > failures from TC. We don't need to check successfull runs, because
> > they
> > > > are
> > > > > uninformative for our needs.
> > > > >
> > > > > 2018-08-21 20:24 GMT+03:00 Dmitriy Pavlov :
> > > > >
> > > > >> Hi Dmitriy,
> > > > >>
> > > > >> The Bot is able to detect a frequent change of test status, but
> > > > currently
> > > > >> only 50 last runs count. Same is true for the failure rate.
> > > > >>
> > > > >> This value can be easily changed to 70 or 100, moreover, the auto
> > > > >> trigger feature gives us much more builds.
> > > > >>
> > > > >> We can improve these rules. We can add not only status change, but
> > > > status
> > > > >> change without any code changes. We can somehow save this data in
> > > > RunStat
> > > > >> class. Let's create a better rule, and later we can code it.
> > > > >>
> > > > >> Sincerely,
> > > > >> Dmitriy Pavlov
> > > > >>
> > > > >> вт, 21 авг. 2018 г. в 19:22, Dmitrii Ryabov <
> somefire...@gmail.com
> > >:
> > > > >>
> > > > >> > I think plugin will be more 

Failed to activate node components

[wt]

I am getting the following error when starting a single node cluster
(intellij) and then the instance crashes. I did have some persistence issues
so cleaned up the work dir after which this started happening

ignite-5885b9e6.log

  

console output:

"C:\Program Files\Java\jdk1.8.0_151\bin\java" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2017.3\lib\idea_rt.jar=51505:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2017.3\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\Java\jdk1.8.0_151\jre\lib\charsets.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\deploy.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\access-bridge-64.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\cldrdata.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\dnsns.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\jaccess.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\jfxrt.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\localedata.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\nashorn.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\sunec.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\sunjce_provider.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\sunmscapi.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\sunpkcs11.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\ext\zipfs.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\javaws.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\jce.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\jfr.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\jfxswt.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\jsse.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\management-agent.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\plugin.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\resources.jar;C:\Program
Files\Java\jdk1.8.0_151\jre\lib\rt.jar;C:\Program

Re: How can i make my custom plugin serializable - Failed to serialize object: plugins.CustomSecurityProcessor

[wt]

thanks, found the anonymous class and created new ones with serializable



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Ignition.loadSpringBean("POC5-server.xml","grid.cfg") - error Failed to activate node components

[wt]

I have a project that starts fine if i start it like this

Ignite ig = Ignition.start("POC5-server.xml");
ig.cluster().active(true);

I need to however use the config file and also set other details before
starting so When i do this i get an error:

IgniteConfiguration cfg =
Ignition.loadSpringBean("POC5-server.xml","grid.cfg");
--set other things here (they are commented out in the code for now)
Ignite ig =Ignition.start(cfg);
ig.cluster().active(true);

here is the error in the log file:



[2018-09-03 14:20:18,866][INFO ][main][IgniteKernal%POC5] 

>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.6.0#20180710-sha1:669feacc
>>> 2018 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

[2018-09-03 14:20:18,882][INFO ][main][IgniteKernal%POC5] Config URL: n/a
[2018-09-03 14:20:18,898][INFO ][main][IgniteKernal%POC5]
IgniteConfiguration [igniteInstanceName=POC5, pubPoolSize=8, svcPoolSize=8,
callbackPoolSize=8, stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4,
igfsPoolSize=2, dataStreamerPoolSize=8, utilityCachePoolSize=8,
utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8,
igniteHome=c:\ignite\, igniteWorkDir=c:\ignite\work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@23529fee,
nodeId=b36055b7-426d-4975-bf5b-cb54fbb06dbc,
marsh=org.apache.ignite.internal.binary.BinaryMarshaller@3c73951,
marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000,
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1,
metricsUpdateFreq=2000, metricsExpTime=9223372036854775807,
discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=0, ackTimeout=0,
marsh=null, reconCnt=10, reconDelay=2000, maxAckTimeout=60,
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null],
segPlc=STOP, segResolveAttempts=2, waitForSegOnStart=true,
allResolversPassReq=true, segChkFreq=1, commSpi=TcpCommunicationSpi
[connectGate=null, connPlc=null, enableForcibleNodeKill=false,
enableTroubleshootingLog=false,
srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@32b260fa,
locAddr=null, locHost=null, locPort=47100, locPortRange=100, shmemPort=-1,
directBuf=true, directSndBuf=false, idleConnTimeout=60,
connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768,
sockRcvBuf=32768, msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null,
shmemSrv=null, usePairedConnections=false, connectionsPerNode=1,
tcpNoDelay=true, filterReachableAddresses=false, ackSndThreshold=32,
unackedMsgsBufSize=0, sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1,
boundTcpShmemPort=-1, selectorsCnt=4, selectorSpins=0, addrRslvr=null,
ctxInitLatch=java.util.concurrent.CountDownLatch@581ac8a8[Count = 1],
stopping=false,
metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@6d4e5011],
evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@57d7f8ca,
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null],
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@662b4c69,
addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=1,
txCfg=org.apache.ignite.configuration.TransactionConfiguration@fa49800,
cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED,
p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100,
timeSrvPortRange=100, failureDetectionTimeout=1,
clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null,
connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@71238fc2,
odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration
[seqReserveSize=1000, cacheMode=PARTITIONED, backups=1, aff=null,
grpName=null], classLdr=null, sslCtxFactory=null, platformCfg=null,
binaryCfg=null, memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration
[sysRegionInitSize=41943040, sysCacheMaxSize=104857600, pageSize=0,
concLvl=0, dfltDataRegConf=DataRegionConfiguration [name=default,
maxSize=1073741824, initSize=268435456, swapPath=null,
pageEvictionMode=DISABLED, evictionThreshold=0.9, emptyPagesPoolSize=100,
metricsEnabled=false, metricsSubIntervalCount=5,
metricsRateTimeInterval=6, persistenceEnabled=true,
checkpointPageBufSize=0], storagePath=null, checkpointFreq=18,
lockWaitTime=1, checkpointThreads=4, checkpointWriteOrder=SEQUENTIAL,
walHistSize=20, walSegments=10, walSegmentSize=67108864, walPath=db/wal,
walArchivePath=db/wal/archive, metricsEnabled=false, walMode=LOG_ONLY,
walTlbSize=131072, walBuffSize=0, walFlushFreq=2000, walFsyncDelay=1000,
walRecordIterBuffSize=67108864, alwaysWriteFullPages=false,
fileIOFactory=org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory@16a0ee18,
metricsSubIntervalCnt=5, metricsRateTimeInterval=6,
walAutoArchiveAfterInactivity=-1, writeThrottlingEnabled=false,
walCompactionEnabled=false], activeOnStart=true, autoActivation=true,
longQryWarnTimeout=3000, 

[GitHub] ignite pull request #4672: IGNITE-9428: Fix broken MvccQueryTrackerImpl.onDo...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-9428: Fix broken MvccQueryTrackerImpl.onDone() semantic.

Signed-off-by: Andrey V. Mashenkov 

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

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

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

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


commit d3989bae08e2f7cdbc8677c4fae021efa7ef41f0
Author: Andrey V. Mashenkov 
Date:   2018-09-03T13:06:24Z

IGNITE-9428: Fix broken MvccQueryTrackerImpl.onDone() semantic.

Signed-off-by: Andrey V. Mashenkov 




---

[GitHub] ignite pull request #4671: Ignite 9448

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

Ignite 9448



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

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

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

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


commit 33d7c41b45b422845314e0c2ccebfd36a706d243
Author: vd-pyatkov 
Date:   2018-08-31T15:39:58Z

IGNITE-9448
Change ZooKeeper version to 3.4.13

commit f5983ccdb4d3b23141912f973b3c2f1de6d218e6
Author: vd-pyatkov 
Date:   2018-09-03T12:30:27Z

Fiexd Zookeeper tests.




---

Re: Hello

[Alexey Goncharuk]

Hello Maxim,

Welcome to the Ignite community! I've added you to the list of
contributors, you should now be able to assign tickets to yourself.

Get familiar with Apache Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

--AG

пн, 3 сент. 2018 г. в 15:21, Maxim.Pudov :

> I'm new to Ignite and I would like to join Apache Ignite development.
> My JIRA's login is Maxim.Pudov
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #4643: IGNITE-8886 Fix position calculation for mixed ra...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: find bugs code check

[Nikolai Kulagin]

Hi. Igniters!

I create two PR [1,2] for two issues: IGNITE-9165 (close streams) [3] and
IGNITE-9160 (fix equals methods) [4]. Can you please review it? The changes
are quite small, tests are ok, flacky as usual.

[1] https://github.com/apache/ignite/pull/4481
[2] https://github.com/apache/ignite/pull/4478
[3] https://jira.apache.org/jira/browse/IGNITE-9165
[4] https://jira.apache.org/jira/browse/IGNITE-9160



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4351: IGNITE-584 Correct results returned, while changi...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4670: IGNITE-9412: GDB convergence by error support

[avplatonov]

GitHub user avplatonov opened a pull request:

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

IGNITE-9412: GDB convergence by error support



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

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

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

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


commit 6049b8495605098562f4babecbc0f250136c6a00
Author: Alexey Platonov 
Date:   2018-08-31T14:19:24Z

initial commit

commit e60dee7e63d594da0b0d4ac4634028d011bc0a32
Author: Alexey Platonov 
Date:   2018-08-31T15:44:59Z

convergence iface [non-compilable]

commit ac235737444113efcd0859f9a15adc603fa1dbd5
Author: Alexey Platonov 
Date:   2018-09-03T11:04:50Z

several convergence algorithms implementation

commit c4fdb32abe2160fc5fb47c11bbb497f4f219df86
Author: Alexey Platonov 
Date:   2018-09-03T11:07:31Z

using mean conv strgy by default

commit 7181879a606f561b369f09771605de74797f0faa
Author: Alexey Platonov 
Date:   2018-09-03T12:44:23Z

add tests

commit 4035271b28dd92935546a3ea78b213abc638f15d
Author: Alexey Platonov 
Date:   2018-09-03T13:14:48Z

pre review checks

commit c2e5b581652c4bf626cb0241f2accba680b32727
Author: Alexey Platonov 
Date:   2018-09-03T13:25:13Z

pre review checks




---

[jira] [Created] (IGNITE-9454) SecurityPermissionSetBuilder fails to append system permission CACHE_CREATE

[Alexey Kukushkin (JIRA)]

Alexey Kukushkin created IGNITE-9454:


 Summary: SecurityPermissionSetBuilder fails to append system 
permission CACHE_CREATE
 Key: IGNITE-9454
 URL: https://issues.apache.org/jira/browse/IGNITE-9454
 Project: Ignite
  Issue Type: Bug
  Components: security
Affects Versions: 2.5
Reporter: Alexey Kukushkin
Assignee: Alexey Kukushkin


SecurityPermissionSetBuilder fails to append system permission CACHE_CREATE, 
CACHE_DESTROY and JOIN_AS_SERVER

+*Reproducer*+:

SecurityPermissionSetBuilder.create().appendSystemPermission(SecurityPermission.CACHE_CREATE)

The code above throw IgniteException saying that a security permission name 
should begin with either EVENTS_ or ADMIN_

*+Solution+:*

Update SecurityPermissionSetBuilder to:
 # allow system permissions CACHE_CREATE, CACHE_DESTROY and JOIN_AS_SERVER
 # restrict cache presmissions CACHE_CREATE, CACHE_DESTROY
 # add automated tests

 



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

[GitHub] ignite pull request #4669: IGNITE-7855: Supported streaming mode in ODBC

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-7855: Supported streaming mode in ODBC



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

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

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

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


commit 716ee2f4e639aeb0d327e7a16465deb01e4b4db6
Author: Igor Sapego 
Date:   2018-04-05T14:06:48Z

IGNITE-7855: Created SqlParser

commit 78a5877ebb568061378a916b212d80c689722f6d
Author: Igor Sapego 
Date:   2018-04-06T16:23:28Z

IGNITE-7855: Added Lexer

commit 6831ac6e5a511af7711ceab4353b0b60e30d4120
Author: Igor Sapego 
Date:   2018-04-17T15:27:55Z

IGNITE-7855: Implemented Lexer

commit 515e94d3834e437bcc131d385a93e684de678797
Author: Igor Sapego 
Date:   2018-04-18T10:18:37Z

IGNITE-7855: Fixes for tests

commit 8a30b6d9da606f912a708a1fd3f140e5b3f99003
Author: Igor Sapego 
Date:   2018-04-23T13:25:13Z

IGNITE-7855: fixes for tests

commit ba5c71a5e0903cc1bd1ad3217c5a0808432cf34a
Author: Igor Sapego 
Date:   2018-08-06T15:37:25Z

IGNITE-7855: Implemented SqlLexer

commit 72201dd7e6ced907847c9695f025c70ba00fb80d
Author: Igor Sapego 
Date:   2018-08-06T17:47:25Z

IGNITE-7855: Implemented SqlParser

commit 0af9faee77e79278fec4b983461c283c93430e46
Author: Igor Sapego 
Date:   2018-08-08T10:07:02Z

IGNITE-7855: Implemented parser

commit bfa0d111258b4cce465f35d7b3704764e9f941ad
Author: Igor Sapego 
Date:   2018-08-08T10:38:56Z

IGNITE-7855: Improvements for SET STREAMING command parsing

commit d46f73a1417ae2ab008e62ea5bd895201461a212
Author: Igor Sapego 
Date:   2018-08-08T11:48:12Z

IGNITE-7855: Implemented tests

commit 55c9cf479d4554bb7b45dfa6d0b4de89259a0f29
Author: Igor Sapego 
Date:   2018-08-09T09:21:19Z

IGNITE-7855: Added tests

commit 1f43744d5ac49ff6fe844bbfce0fbc0f79282b2f
Author: Igor Sapego 
Date:   2018-08-21T15:57:10Z

IGNITE-7855: Fixed SQL parser and lexer

commit d293626188d0f6103f21f0ad33c90db3c929bd1c
Author: Igor Sapego 
Date:   2018-08-22T14:33:59Z

IGNITE-7855: Added sql_utils

commit 655d3e01efa8ce28e2d12d6bb54973e8f7a45479
Author: Igor Sapego 
Date:   2018-08-22T14:36:17Z

IGNITE-7855: Minor fixes

commit 896f779e0950a31d2c0079469171cedea514a9d6
Author: Igor Sapego 
Date:   2018-08-22T15:16:58Z

IGNITE-7855: Expected abstraction implemented

commit 5a7a8c64121d7e61e1678d9076be3c85408ce9ad
Author: Igor Sapego 
Date:   2018-08-22T17:35:31Z

IGNITE-7855: Expected re-worked

commit 108a6af05ac3749363275e77ee13188894250f9e
Author: Igor Sapego 
Date:   2018-08-22T17:59:32Z

IGNITE-7855: Made Lexer non-throwable.

commit ff2251d6a6bc6fad5a91881067bc2b258a1c65f3
Author: Igor Sapego 
Date:   2018-08-23T12:57:12Z

IGNITE-7855: Implemented internal command verification

commit 7f52ce67261fd36e13e24084f9c89704073103af
Author: Igor Sapego 
Date:   2018-08-27T11:04:13Z

IGNITE-7855: Fix for statement

commit d4a1b035f27abf706c3391c0f88ede298e926a38
Author: Igor Sapego 
Date:   2018-08-27T16:26:03Z

IGNITE-7855: Save

commit 14cd1bd131dce4acdab6945bbe1e8623bfaf371c
Author: Igor Sapego 
Date:   2018-08-29T08:40:13Z

IGNITE-7855: Implemented Server side

commit 3bc805775a4f1166727220f49a53a57145fb2fe7
Author: Igor Sapego 
Date:   2018-08-30T15:59:33Z

IGNITE-7855: Implemented sync streaming on client side

commit 3af9c64145c6bf6d26ed8971237e1aecac9d8f01
Author: Igor Sapego 
Date:   2018-08-30T16:30:20Z

IGNITE-7855: Rebase-related fixes

commit 550163ba2c9fd062ab7cfc6c328250de4d22a374
Author: Igor Sapego 
Date:   2018-08-30T16:34:36Z

IGNITE-7855: Fixed minor bug

commit 7ed5a058af70e0d939a56caf70b0e0dfdd213696
Author: Igor Sapego 
Date:   2018-08-30T17:15:48Z

IGNITE-7855: Fixed bug

commit be6dad2561f37199b5ac2688a7408c05dfe9bd0a
Author: Igor Sapego 
Date:   2018-08-31T12:49:42Z

IGNITE-7855: Fixes

commit c4e3efe5991020f54068d0fa526ba42263c67693
Author: Igor Sapego 
Date:   2018-08-31T16:00:37Z

IGNITE-7855: Implemented encoding and decoding of stream messages

commit a60e08d891c2ea8fd8f2d8115820facd2dcac06e
Author: Igor Sapego 
Date:   2018-08-31T16:01:31Z

IGNITE-7855: Added streaming test

commit 5a97f55f0cfec4e0d1d939a40c22d159375f2cac
Author: Igor Sapego 
Date:   2018-08-31T16:02:17Z

IGNITE-7855: Fixed bug

commit 5ed1a4322e128bed2c40e46ac76757afa4e004e6
Author: Igor Sapego 
Date:   2018-08-31T16:49:49Z

IGNITE-7855: Improved test. Minor fixes




---

[jira] [Created] (IGNITE-9453) REST: UUID column type displayed like byte array

[Stepan Pilschikov (JIRA)]

Stepan Pilschikov created IGNITE-9453:
-

 Summary: REST: UUID column type displayed like byte array
 Key: IGNITE-9453
 URL: https://issues.apache.org/jira/browse/IGNITE-9453
 Project: Ignite
  Issue Type: Bug
  Components: rest
Affects Versions: 2.5
Reporter: Stepan Pilschikov


Case:
- Create table with uuid
{code:sql}
CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
{code}
- Execute `select * from test` query with rest
{code:bash}
curl 
"http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
{code}

Actual:
{code:json}
{
"successStatus": 0,
"sessionToken": null,
"error": null,
"response": {
"items": [],
"last": true,
"fieldsMetadata": [
{
"schemaName": "PUBLIC",
"typeName": "TEST",
"fieldName": "ID",
"fieldTypeName": "java.lang.Integer"
},
{
"schemaName": "PUBLIC",
"typeName": "TEST",
"fieldName": "FIELD",
"fieldTypeName": "java.lang.String"
},
{
"schemaName": "PUBLIC",
"typeName": "TEST",
"fieldName": "UUID",
"fieldTypeName": "[B"
}
],
"queryId": 0
}
}
{code}

Expected:
uuid was displayed somehow but not "[B"



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

[GitHub] ignite pull request #4668: Ignite 2.5.1 p13 zk test

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

Ignite 2.5.1 p13 zk test



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.5.1-p13-zk-test

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

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


commit 553e0ff7c2fdecd5d4a64afd88d93e3ccffbe37a
Author: Dmitriy Govorukhin 
Date:   2018-04-20T13:20:00Z

IGNITE-8077 Introduced additional transaction metrics - Fixes #3879.

Signed-off-by: Alexey Goncharuk 

commit d2332c4865445f372f6ce0ba70b7da1fec987a8f
Author: Andrey Kuznetsov 
Date:   2018-04-20T16:51:59Z

IGNITE-8303 Avoided failure handler invocation when exchange-worker 
terminates before reconnect.

Signed-off-by: Andrey Gura 

commit 1d42f48cc8a39c3de9cac0e434f527ab4041479b
Author: Pavel Tupitsyn 
Date:   2018-04-11T08:51:45Z

IGNITE-7222 .NET: Ignore missing 
IgniteConfiguration.CommunicationFailureResolver

commit 744662e071f9c963cf494f78ad54b503851e5c4a
Author: Alexey Goncharuk 
Date:   2018-04-22T17:07:28Z

IGNITE-8353 Fixed serialVersionUID for AbstractEvictionPolicy

commit bfed389fb6f3437eee20bc6baf2b7e725f9fb6a7
Author: Alexey Goncharuk 
Date:   2018-04-23T08:04:28Z

IGNITE-8077 Do not attempt to clean up work directory on running grid in 
ConfigVariationTests

commit 628f3fb33416e6e5c963450d5544ac32b6ecfe4a
Author: Aleksey Plekhanov 
Date:   2018-04-23T09:32:18Z

IGNITE-8190 Print out an information message when local node is not in 
baseline

Signed-off-by: Andrey Gura 

commit c2a8bbc6b7ca500a2b7e485c16664b440439e602
Author: Aleksey Plekhanov 
Date:   2018-04-23T09:55:25Z

IGNITE-8191 Print out information when cluster is not activated

Signed-off-by: Andrey Gura 

commit 3c3a24e84a9a9f07d0833b29524de244930634c3
Author: Nikolay Izhikov 
Date:   2018-04-20T08:23:42Z

IGNITE-7077: Implementation of Spark query optimization. - Fixes #3397.

Signed-off-by: Nikolay Izhikov 

commit d7962f83f14292a571016b79af594ceefe632d83
Author: Alexey Goncharuk 
Date:   2018-04-20T16:17:32Z

IGNITE-7077 Fixed header licenses

commit 2497fe376ffa7df65381f2c91151b6f7fccaf212
Author: Aleksey Plekhanov 
Date:   2018-04-23T10:27:51Z

IGNITE-8192 Print out information on how many nodes left until 
auto-activation

Signed-off-by: Andrey Gura 

commit 9e3daf6aafd48ad93086f8e7968fb376f03f4519
Author: Andrey Gura 
Date:   2018-04-23T13:31:57Z

IGNITE-8228 Print out information about configured failure handler

commit ee1e089a8cded02e51063602cb8c470a2aad4fa7
Author: Ilya Lantukh 
Date:   2018-04-23T14:39:57Z

IGNITE-8323 Fixed discovery event listener calls - Fixes #3890.

Signed-off-by: Alexey Goncharuk 

commit 5a981c9f38abfc37934d7f3c19e87f8cd5f586c2
Author: tledkov-gridgain 
Date:   2018-04-23T15:20:21Z

IGNITE-8355 Fixed NPE on concurrent nodes start - Fixes #3899.

Signed-off-by: Alexey Goncharuk 

commit 46bff2b143db5c6819222477348c9c7b539934ac
Author: Aleksei Scherbakov 
Date:   2018-04-23T15:59:04Z

IGNITE-6827 Configurable rollback for long running transactions before 
partition exchange
IGNITE-7910 Improved transaction debugging support

Signed-off-by: Andrey Gura 

commit 9cbe870642941a68a688d4a1654e7302a48e79bd
Author: Alexey Goncharuk 
Date:   2018-04-23T16:39:01Z

IGNITE-6083 Null value may be passed to the entry processor on existing key

commit 3425ef5e1d0e03a30a4060e5e3f3bcb0076c99c9
Author: Ivan Daschinskiy 
Date:   2018-04-23T17:37:09Z

IGNITE-7786 Added ping timeout and ping interval to control.sh

Signed-off-by: Andrey Gura 

commit 1eaa39c2fbbdcc116b39d11317d067da3cbca270
Author: Alexey Goncharuk 
Date:   2018-04-24T07:42:55Z

IGNITE-8369 Fixed ZookeeperDiscoveryImpl to use j.u.c.ConcurrentHashMap

commit dd356ddbd9e37f78c8312d770ca8578a15d96ec9
Author: Alexey Goncharuk 
Date:   2018-04-24T09:33:58Z

IGNITE-7786 Fixed javadoc

commit 0ad44bc27bc79630b03748b060aa2503e0830d31
Author: Alexey Goncharuk 
Date:   2018-04-24T10:26:12Z

IGNITE-8369 Fixed ZkCommunicationErrorProcessFuture to use 
j.u.c.ConcurrentHashMap

commit 198d6d2a6c66100a38212373e61014e746b364e3
Author: Pavel Kovalenko 
Date:   2018-04-24T13:08:21Z

IGNITE-8339 Fixed partition state detection on activation - Fixes #3885.

Signed-off-by: Alexey Goncharuk 

commit b4bf53f81a4ed06b61ca207ce33ba5e859e6ce40
Author: Alexey Goncharuk 
Date:   2018-04-24T17:57:56Z

IGNITE-8082 Fixed build (added javadoc)

commit b96445247a547e538d923f6898b85bde1b8b17b9
Author: Alexey Goncharuk 
Date:   2018-04-25T09:30:09Z

ignite-2.5.1 Fixed version for backward compatibility

commit 

Hello

[Maxim.Pudov]

I'm new to Ignite and I would like to join Apache Ignite development. 
My JIRA's login is Maxim.Pudov



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-9452) Correct GridInternalTaskUnusedWalSegmentsTest after merging IGNITE-6552

[Ivan Daschinskiy (JIRA)]

Ivan Daschinskiy created IGNITE-9452:


 Summary: Correct GridInternalTaskUnusedWalSegmentsTest after 
merging IGNITE-6552
 Key: IGNITE-9452
 URL: https://issues.apache.org/jira/browse/IGNITE-9452
 Project: Ignite
  Issue Type: Test
Reporter: Ivan Daschinskiy
Assignee: Ivan Daschinskiy
 Fix For: 2.8


After merging  IGNITE-6552 need to correct 
GridInternalTaskUnusedWalSegmentsTest a little bit.



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

[GitHub] ignite pull request #4335: IGNITE-8823 Quick fix.

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

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


---

[GitHub] ignite pull request #4667: IGNITE-8823 Quick fix.

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-8823 Quick fix.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8823-true

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

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


commit b907d2a8329d58acca77049de580c345a3dee27d
Author: Andrey Kuznetsov 
Date:   2018-09-03T11:21:23Z

IGNITE-8823 Quick fix.




---

[jira] [Created] (IGNITE-9451) Cache API update Cache.size according to SNAPSHOT isolation

[Ivan Pavlukhin (JIRA)]

Ivan Pavlukhin created IGNITE-9451:
--

 Summary: Cache API update Cache.size according to SNAPSHOT 
isolation
 Key: IGNITE-9451
 URL: https://issues.apache.org/jira/browse/IGNITE-9451
 Project: Ignite
  Issue Type: Task
  Components: mvcc
Reporter: Ivan Pavlukhin


In scope of supporting Cache API for MVCC caches we should ensure that 
Cache.size is updated consistently and only on transaction commit.



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

[GitHub] ignite pull request #4662: IGNITE-9396 ML Examples: can't run examples, not ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: [MTCGA]: new failures in builds [1757777] needs to be handled

[Alexey Goncharuk]

Petr,

Can you by any chance check if rackspace tests have actual keys? I've
created a ticket for the failing test [1].

[1] https://issues.apache.org/jira/browse/IGNITE-9444

пт, 31 авг. 2018 г. в 11:44, Alexey Goncharuk :

> The failure is not related to the change (verified in a separate branch
> with revert) and seems to be related to some change in rackspace
> infrastructure. Will create a ticket and mute the test.
>
> пт, 31 авг. 2018 г. в 0:07, :
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *New test failure in master
>> TcpDiscoveryCloudIpFinderSelfTest.testRackspace
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3102247230760992596=%3Cdefault%3E=testDetails
>>  Changes may led to failure were done by
>>  - irakov
>> http://ci.ignite.apache.org/viewModification.html?modId=829932=false
>>
>> - If your changes can led to this failure(s), please create issue
>> with label MakeTeamCityGreenAgain and assign it to you.
>> -- If you have fix, please set ticket to PA state and write to
>> dev list fix is ready
>> -- For case fix will require some time please mute test and set
>> label Muted_Test to issue
>> - If you know which change caused failure please contact change
>> author directly
>> - If you don't know which change caused failure please send
>> message to dev list to find out
>> Should you have any questions please contact dev@ignite.apache.org
>> Best Regards,
>> MTCGA.Bot
>> Notification generated at Fri Aug 31 00:06:59 MSK 2018
>>
>

[jira] [Created] (IGNITE-9450) Web console: remove manual rendering from ignite-icon directive

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-9450:


 Summary: Web console: remove manual rendering from ignite-icon 
directive
 Key: IGNITE-9450
 URL: https://issues.apache.org/jira/browse/IGNITE-9450
 Project: Ignite
  Issue Type: Improvement
Reporter: Ilya Borisov
Assignee: Ilya Borisov


When making the ignite-icon directive, I had to manually render SVGs because at 
that moment we had to support IE11 and it doesn't support SVG directive 
template namespace. Since IE11 support has been dropped, we can safely use 
regular AngularJS template there and clean the code a bit. I think this change 
will also fix invisible icons in TestCafe E2E tests.



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

Re: Table Names in Spark Catalog

[Stuart Macdonald]

Nikolay, Val, it would be good if we could reach agreement here so that I
can make the necessary modifications before the 2.7 cutoff.

Nikolay - would you be comfortable if I went ahead and made database=schema?

Stuart.

On Mon, Aug 27, 2018 at 10:22 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Nikolay,
>
> I think it's actually pretty unfortunate that Spark uses term "database"
> here, as it essentially refers to a schema in my view. Usually, database is
> something you create a physical connection to, and connection is bind to
> that database. To connect to another database you need to create a new
> connection. In Spark, however, you can switch between "databases" within a
> single session, which looks really weird to me because it's usually a
> characteristic of a schema. Having said that, I understand your concern,
> but I don't think there is an ideal solution.
>
> As for your approach, I still don't understand how it will allow to fully
> support schemas in catalog.
> - How will you get a list of tables within a particular schema? In other
> words, what would listTables() method return?
> - How will you switch between the schemas?
> - Etc.
>
> I still think assuming database=schema is the best we can do here, but I
> would be happy to hear another opinions from other community members.
>
> OPTION_SCHEMA should definitely be introduced though (I thought we already
> did, no?). CREATE TABLE will be supported with this ticket:
> https://issues.apache.org/jira/browse/IGNITE-5780. For now we will have to
> throw an exception if custom schema name is provided when creating a Spark
> session, but table does not exist yet.
>
> -Val
>
> On Sun, Aug 26, 2018 at 7:56 AM Nikolay Izhikov 
> wrote:
>
> > Igniters,
> >
> > Personally, I don't like the solution with database == schema name.
> >
> > 1. I think we should try to use the right abstractions.
> > schema == database doesn't sound right for me.
> >
> > Do you want to answer to all of our users something like that:
> >
> > - "How I can change Ignite SQL schema?"
> > - "This is obvious, just use setDatabase("MY_SCHEMA_NAME")".
> >
> > 2. I think we restrict whole solution with that decision.
> > If Ignite will support multiple databases in the future we just don't
> have
> > a place for it.
> >
> > I think we should do the following:
> >
> > 1. IgniteExternalCatalog should be able to return *ALL* tables
> > within Ignite instance.
> > We shouldn't restrict tables list by schema by default.
> > We should return tables with schema name - `schema.table`
> >
> > 2. We should introduce `OPTION_SCHEMA` for a dataframe to specify
> > a schema.
> >
> > There is an issue with the second step: We can't use schema name
> > in `CREATE TABLE` clause.
> > This is restriction of current Ignite SQL.
> >
> > I propose to make the following:
> >
> > 1. For all write modes that requires the creation of table we
> > should disallow usage of table outside of `SQL_PUBLIC`
> > or usage of `OPTION_SCHEMA`. We should throw proper exception for
> > this case.
> >
> > 2. Create a ticket to support `CREATE TABLE` with custom schema
> > name.
> >
> > 3. After resolving ticket from step 2 we can add full support of
> > custom schema to Spark integration.
> >
> > 4. We should throw an exception if user try to use setDatabase.
> >
> > Is that makes sense for you?
> >
> > В Вс, 26/08/2018 в 14:09 +0100, Stuart Macdonald пишет:
> > > I'll go ahead and make the changes to represent the schema name as the
> > > database name for the purposes of the Spark catalog.
> > >
> > > If anyone knows of an existing way to list all available schemata
> within
> > an
> > > Ignite instance please let me know, otherwise the first task will be
> > > creating that mechanism.
> > >
> > > Stuart.
> > >
> > > On Fri, Aug 24, 2018 at 6:23 PM Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > Nikolay,
> > > >
> > > > If there are multiple configuration in XML, IgniteContext will always
> > use
> > > > only one of them. Looks like current approach simply doesn't work. I
> > > > propose to report schema name as 'database' in Spark. If there are
> > multiple
> > > > clients, you would create multiple sessions and multiple catalogs.
> > > >
> > > > Makes sense?
> > > >
> > > > -Val
> > > >
> > > > On Fri, Aug 24, 2018 at 12:33 AM Nikolay Izhikov <
> nizhi...@apache.org>
> > > > wrote:
> > > >
> > > > > Hello, Valentin.
> > > > >
> > > > > > catalog exist in scope of a single IgniteSparkSession> (and
> > therefore
> > > > >
> > > > > single IgniteContext and single Ignite instance)?
> > > > >
> > > > > Yes.
> > > > > Actually, I was thinking about use case when we have several Ignite
> > > > > configuration in one XML file.
> > > > > Now I see, may be this is too rare use-case to support.
> > > > >
> > > > > Stuart, Valentin, What is your proposal?
> > > > >
> > > > > В 

[jira] [Created] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-9449:
---

 Summary: Lazy unmarshalling of discovery events in TcpDiscovery
 Key: IGNITE-9449
 URL: https://issues.apache.org/jira/browse/IGNITE-9449
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.6, 2.5, 2.4
Reporter: Pavel Kovalenko
 Fix For: 2.7


Currently disco-msg-worker thread spend major part of time on disocvery message 
unmarshalling before send it to the next node. In most cases this is 
unnecessary and message can be send immediately after receiving and notyfing 
discovery-event-worker.
Responsibility of unmarshalling should moved to discovery-event-worker thread 
and this improvement will significantly reduce latency of sending custom 
messages across ring.  



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

[GitHub] ignite pull request #4666: Ignite 1.8.20

[dmekhanikov]

GitHub user dmekhanikov opened a pull request:

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

Ignite 1.8.20

Created for testing

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

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

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

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


commit 5ac9afc719138e37a7d97d9d9db05243eee9a942
Author: Evgenii Zhuravlev 
Date:   2017-06-22T09:36:14Z

IGNITE-5399 add test to testsuite

commit a935d40a80e2f928a84a145aba540a45b156687f
Author: Evgenii Zhuravlev 
Date:   2017-06-22T12:10:32Z

GG-12256 Minor fixes

commit 7e2468770a4eb47a4f61204d8c2000b6ab67c967
Author: nikolay_tikhonov 
Date:   2017-06-22T13:13:01Z

IGNITE-GG-12197 Fixed "Ignore events for discarded update in CLOCK mode".

Signed-off-by: nikolay_tikhonov 

commit 5858efd406bb54352de14a0a7e7f21c2ac7bf899
Author: sboikov 
Date:   2016-12-16T16:23:29Z

IGNITE-2412 - Do not acquire asyncSemaphore for synchronous operations 
(cherry-picked from master)

(cherry picked from commit 82b4073)

commit 113a1380da34ea804d68757d39926da97dee09b6
Author: Alexey Goncharuk 
Date:   2017-06-13T05:20:22Z

GG-12355: Backported IO latency test.

commit 540ca449f1bd2386d3ba0722afb21dd3a504d044
Author: Alexey Goncharuk 
Date:   2017-06-13T17:55:38Z

GG-12355: Added discovery ring latency test + made it available from MBean 
(cherry-picked from master).

commit 0fc6271d8e39125bf5ee341e50a2665a04fc8b1e
Author: Andrey V. Mashenkov 
Date:   2017-06-21T10:42:12Z

GG-12350: GridDhtAtomicSingleUpdateRequest misses topologyVersion() method 
override.

commit f8224d13cf9a6432ba65e0016370ba51bbb544e9
Author: Alexey Goncharuk 
Date:   2017-06-15T19:49:45Z

GG-12299: Make sure concurrent type registrations do not trigger multiple 
cache updates.

commit 4ffc3acfa1bc43bea8c79bfd1864787c15cfc4de
Author: Alexey Goncharuk 
Date:   2017-06-20T04:59:09Z

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store 
exception.

commit 8cd9e829380f4c91cc9bb126169863286d1cb323
Author: Andrey V. Mashenkov 
Date:   2017-06-21T12:40:14Z

GG-12353: Added local binary context flag.

Backport of IGNITE-5223 with fixes.

commit 9036ad239d68eff663bc73a81baab2826b054d9a
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:25:31Z

Added MBean for system cache executors.

commit ed34a5dc681ea8f284f4d25c5575ad46569cc600
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:33:55Z

Partial fix of IGNITE-5562.

commit d427021f329292fb69d348ba949ad1f8f1e9089e
Author: Andrey V. Mashenkov 
Date:   2017-06-21T16:30:27Z

IGNITE-5552: ServiceProcessor recalculates all service assignments even if 
there is a pending topology change.

commit f1b9cdc0716a1b23f54d68ce0fe19eb85107567d
Author: Alexey Goncharuk 
Date:   2017-06-14T18:37:54Z

GG-12354: Partial fix of IGNITE-5473: Introduce troubleshooting logger.

commit beb2409cfe2045789443d47de735d879961d371e
Author: Andrey V. Mashenkov 
Date:   2017-06-23T09:26:06Z

GG-12352: Forcible node drop makes cluster instable in some cases.
Disable forcible node drop by default.

commit 802f18fc250cbae8959192c78bb28dc525ed3cf7
Author: AMRepo 
Date:   2017-06-22T21:24:57Z

Fix compilation

commit 39d2dec85a3c571dfdb1cd6189b53ae2413a5d22
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:41:30Z

Merge branch 'ignite-1.7.12-b2' into ignite-1.8.8

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/internal/GridTopic.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/IgniteIoTestMessage.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/service/GridServiceProcessor.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/task/GridTaskThreadContextKey.java
#   
modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite5.java

commit 96445156143b46b664f785b353463dd435ac342d
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:42:44Z

Merge remote-tracking branch 'origin/ignite-1.8.8' into ignite-1.8.8

# Conflicts:
#   

[GitHub] ignite pull request #4665: IGNITE-9426 IgniteAtomicSequence benchmarks

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-9426 IgniteAtomicSequence benchmarks



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

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

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

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


commit e26c20b807c5daeea43fcdfdbdb820847762b101
Author: Dmitriy Govorukhin 
Date:   2018-09-03T08:03:25Z

IGNITE-9426 add benchmarks




---

Re: Python thin client

[Dmitry Melnichuk]

Hello, Nikolay!

Thank you for your interest in Python thin client.

The traceback suggests that you using Python 2.7. Unfortunately, my 
client supports only Python versions 3.4 and later.


Since you are using the latest Ubuntu OS, chances are you already have a 
recent Python 3 installed. Try `pip3`.


On 9/3/18 4:25 PM, Nikolay Izhikov wrote:

Hello, Dmitry.

I tried to build your lib locally and it failed.
Error message and pip version are below.

Seems, we have to fix developer instructions.
Do we need specific version of pip or something?
I tried to use default versions.
I using Ubuntu Linux.

dragon:~/src/ignite/modules/platforms/python:[IGNITE-7782]$ pip install -v -e .
Obtaining file:///home/dragon/src/ignite/modules/platforms/python
   Running setup.py 
(path:/home/dragon/src/ignite/modules/platforms/python/setup.py) egg_info for 
package from file:///home/dragon/src/ignite/modules/platforms/python
 Running command python setup.py egg_info
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/dragon/src/ignite/modules/platforms/python/setup.py", line 20
 def is_a_requirement(line: str) -> bool:
  ^
 SyntaxError: invalid syntax
Cleaning up...
Command "python setup.py egg_info" failed with error code 1 in 
/home/dragon/src/ignite/modules/platforms/python/
Exception information:
Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 215, in main
 status = self.run(options, args)
   File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 353, 
in run
 wb.build(autobuilding=True)
   File "/usr/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build
 self.requirement_set.prepare_files(self.finder)
   File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 380, in 
prepare_files
 ignore_dependencies=self.ignore_dependencies))
   File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 518, in 
_prepare_file
 abstract_dist.prep_for_dist()
   File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 129, in 
prep_for_dist
 self.req_to_install.run_egg_info()
   File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 439, in 
run_egg_info
 command_desc='python setup.py egg_info')
   File "/usr/lib/python2.7/dist-packages/pip/utils/__init__.py", line 725, in 
call_subprocess
 % (command_desc, proc.returncode, cwd))
InstallationError: Command "python setup.py egg_info" failed with error code 1 
in /home/dragon/src/ignite/modules/platforms/python/
dragon:~/src/ignite/modules/platforms/python:[IGNITE-7782]$ apt-cache policy 
python-pip
python-pip:
   Установлен: 9.0.1-2.3~ubuntu1
   Кандидат:   9.0.1-2.3~ubuntu1
   Таблица версий:
  *** 9.0.1-2.3~ubuntu1 500
 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
Packages
 100 /var/lib/dpkg/status
  9.0.1-2 500
 500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
 500 http://ru.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
dragon:~/src/ignite/modules/platforms/python:[IGNITE-7782]$ uname -a
Linux newDragon 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

[GitHub] ignite pull request #4664: IGNITE-8987 Ignite hangs during getting of atomic...

[gromtech]

GitHub user gromtech opened a pull request:

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

IGNITE-8987 Ignite hangs during getting of atomic structure after…

…autoactivation

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

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

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

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


commit 574be81c62754efa760c94afd50f5e8727688f19
Author: Roman Guseinov 
Date:   2018-09-03T06:45:53Z

IGNITE-8987 Ignite hangs during getting of atomic structure after 
autoactivation




---

Re: Python thin client

[Nikolay Izhikov]

Hello, Dmitry.

I tried to build your lib locally and it failed.
Error message and pip version are below.

Seems, we have to fix developer instructions.
Do we need specific version of pip or something? 
I tried to use default versions.
I using Ubuntu Linux.

dragon:~/src/ignite/modules/platforms/python:[IGNITE-7782]$ pip install -v -e .
Obtaining file:///home/dragon/src/ignite/modules/platforms/python
  Running setup.py 
(path:/home/dragon/src/ignite/modules/platforms/python/setup.py) egg_info for 
package from file:///home/dragon/src/ignite/modules/platforms/python
Running command python setup.py egg_info
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/dragon/src/ignite/modules/platforms/python/setup.py", line 20
def is_a_requirement(line: str) -> bool:
 ^
SyntaxError: invalid syntax
Cleaning up...
Command "python setup.py egg_info" failed with error code 1 in 
/home/dragon/src/ignite/modules/platforms/python/
Exception information:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
  File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 353, in 
run
wb.build(autobuilding=True)
  File "/usr/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
  File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 380, in 
prepare_files
ignore_dependencies=self.ignore_dependencies))
  File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 518, in 
_prepare_file
abstract_dist.prep_for_dist()
  File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 129, in 
prep_for_dist
self.req_to_install.run_egg_info()
  File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 439, in 
run_egg_info
command_desc='python setup.py egg_info')
  File "/usr/lib/python2.7/dist-packages/pip/utils/__init__.py", line 725, in 
call_subprocess
% (command_desc, proc.returncode, cwd))
InstallationError: Command "python setup.py egg_info" failed with error code 1 
in /home/dragon/src/ignite/modules/platforms/python/
dragon:~/src/ignite/modules/platforms/python:[IGNITE-7782]$ apt-cache policy 
python-pip
python-pip:
  Установлен: 9.0.1-2.3~ubuntu1
  Кандидат:   9.0.1-2.3~ubuntu1
  Таблица версий:
 *** 9.0.1-2.3~ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
Packages
100 /var/lib/dpkg/status
 9.0.1-2 500
500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://ru.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
dragon:~/src/ignite/modules/platforms/python:[IGNITE-7782]$ uname -a
Linux newDragon 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

В Пн, 03/09/2018 в 16:10 +1000, Dmitry Melnichuk пишет:
> Hello, Igniters!
> 
> Please review my work on Ignite thin client library written in Python 3.
> 
> Pull request:
> https://github.com/apache/ignite/pull/4278
> 
> Jira issue with initial proposal:
> https://issues.apache.org/jira/browse/IGNITE-7782
> 
> The documentation is temporarily available at:
> https://apache-ignite-binary-protocol-client.readthedocs.io/
> 
> It covers installation, requirements, API specification, coding 
> examples, instructions on how to run tests and build the documentation 
> itself.
> 
> Dmitry

signature.asc
Description: This is a digitally signed message part

Python thin client

[Dmitry Melnichuk]

Hello, Igniters!

Please review my work on Ignite thin client library written in Python 3.

Pull request:
https://github.com/apache/ignite/pull/4278

Jira issue with initial proposal:
https://issues.apache.org/jira/browse/IGNITE-7782

The documentation is temporarily available at:
https://apache-ignite-binary-protocol-client.readthedocs.io/

It covers installation, requirements, API specification, coding 
examples, instructions on how to run tests and build the documentation 
itself.


Dmitry