;>– PiClient – to perform actual loading and miscellaneous
> > operations
> > >>>>
t; >
> > Being a committer enables easier contribution to the project since there
> is
> > no need to go via the patch submission process. This should enable better
> > productivity.
> >
> > Vyacheslav, thanks for supporting the community and keep the pace!
&
Ilya Suntsov created IGNITE-12233:
-
Summary: Merge benchmarks sql index benchmarks from ignite-2.7 to
master
Key: IGNITE-12233
URL: https://issues.apache.org/jira/browse/IGNITE-12233
Project: Ignite
Ilya Suntsov created IGNITE-11319:
-
Summary: ignitevisorcmd can't handle incorrect !q parameter
Key: IGNITE-11319
URL: https://issues.apache.org/jira/browse/IGNITE-11319
Project: I
Ilya Suntsov created IGNITE-11306:
-
Summary: NativeSqlJoinQueryRangeBenchmark doesn't work
Key: IGNITE-11306
URL: https://issues.apache.org/jira/browse/IGNITE-11306
Project: Ignite
Ilya Suntsov created IGNITE-11307:
-
Summary: SqlNative benchmarks failed with more than 1 client
Key: IGNITE-11307
URL: https://issues.apache.org/jira/browse/IGNITE-11307
Project: Ignite
Ilya Suntsov created IGNITE-10919:
-
Summary: Implement .Net thin client benchmarks
Key: IGNITE-10919
URL: https://issues.apache.org/jira/browse/IGNITE-10919
Project: Ignite
Issue Type: Task
Ilya Suntsov created IGNITE-10918:
-
Summary: Implement C++, .Net thin benchmarks
Key: IGNITE-10918
URL: https://issues.apache.org/jira/browse/IGNITE-10918
Project: Ignite
Issue Type: Task
Ilya Suntsov created IGNITE-10842:
-
Summary: Exception during node stopping
Key: IGNITE-10842
URL: https://issues.apache.org/jira/browse/IGNITE-10842
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-10800:
-
Summary: Add wal_mode parameter to properties file
Key: IGNITE-10800
URL: https://issues.apache.org/jira/browse/IGNITE-10800
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-10170:
-
Summary: .NET: Services.ServicesTestAsync fails
Key: IGNITE-10170
URL: https://issues.apache.org/jira/browse/IGNITE-10170
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-10148:
-
Summary: Add aws s3 and elb configs to benchmarks/config
Key: IGNITE-10148
URL: https://issues.apache.org/jira/browse/IGNITE-10148
Project: Ignite
Issue
Ilya Suntsov created IGNITE-9784:
Summary: Performance drop on sql yardstick benchmarks
Key: IGNITE-9784
URL: https://issues.apache.org/jira/browse/IGNITE-9784
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-9534:
Summary: Wrong error message in bin/include/functions.sh
Key: IGNITE-9534
URL: https://issues.apache.org/jira/browse/IGNITE-9534
Project: Ignite
Issue Type
Dmitriy, congrats!
It is really great news!
On Fri, Aug 31, 2018, 02:30 Saikat Maitra wrote:
> Dmitriy,
>
> Congratulations !!!
>
> My best wishes :)
>
> Regards,
> Saikat
>
>
>
> On Thu, Aug 30, 2018 at 1:20 PM, Pavel Kovalenko
> wrote:
>
> > Dmitriy,
> >
> > Congratulations. This is very nice
Ilya Suntsov created IGNITE-9417:
Summary: IgniteSqlInsertIndexedValueBenchamrks failed with more
than one driver
Key: IGNITE-9417
URL: https://issues.apache.org/jira/browse/IGNITE-9417
Project
; > a branches comparision.
> > >
> > > So, my question is:
> > > Is there anybody at community able to perform benchmarks on real
> hardware
> > > and already have automation to compare 2 branches?
> > >
>
>
>
> --
> Best Regards, Vyacheslav D.
>
--
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com
x can be completed in second (please
> use same as you use to check the release)
> - in-memory
> - default
> - same you use at pre-release check.
>
> пт, 3 авг. 2018 г. в 15:38, Ilya Suntsov :
>
>> Anton,
>>
>> Please provide more details:
>>
>>
gt; Could you please check https://issues.apache.org/jira/browse/IGNITE-8446?
>>
>> We have to check
>> https://github.com/apache/ignite/tree/ignite-8446
>> vs
>> https://github.com/apache/ignite/tree/ignite-8446-master
>>
>> Only one benchmark is required: tx throughput
>>
>
--
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com
lkuznetsov...@gmail.com
>> > > > wrote:
>> > >
>> > > > Hi ,Igniters!
>> > > >
>> > > > Do we still need this ticket, about invoke metrics : [1] ?
>> > > >
>> > > > If yes, than could somebody review it ?
>> > > >
>> > > > If no, should we close this ticket ?
>> > > >
>> > > > [1] : https://issues.apache.org/jira/browse/IGNITE-6846
>> > > > --
>> > > >
>> > > > *Best Regards,*
>> > > >
>> > > > *Kuznetsov Aleksey*
>> > > >
>> > >
>> >
>>
>
--
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com
lease confirm that all changes [1] expected
> [1]
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
>
> ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov :
>
> > Anton,
> >
pacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > >> [2]
> > >>
> > >>
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_
> >> https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20IGNITE%20AND%
> > >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> > >> > 20closed%20or%20status%20%3D%20resolved)
> > >> >
> > >> > DEVNOTES
> > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> > >> >
> > >> > RELEASE NOTES
> > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> > >> >
> > >> > Please start voting.
> > >> >
> > >> > +1 - to accept Apache Ignite 2.6.0-RC1
> > >> > 0 - don't care either way
> > >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> > >> >
> > >> > This vote will go for 72 hours.
> > >> >
> > >>
> > >
> >
>
--
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com
Ilya Suntsov created IGNITE-8864:
Summary: sql-query-put x 5 performance drop
Key: IGNITE-8864
URL: https://issues.apache.org/jira/browse/IGNITE-8864
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-8733:
Summary: Add benchmarks for NodeJS thin client
Key: IGNITE-8733
URL: https://issues.apache.org/jira/browse/IGNITE-8733
Project: Ignite
Issue Type
Hi Brian,
I would like to add Apache Ignite (https://apacheignite.readme.io/docs)
client to YCSB repository.
Pull request passed all travis tests:
https://github.com/brianfrankcooper/YCSB/pull/1118
Could you please take a look at this PR?
--
Best Regards,
Ilya Suntsov
email: isunt
tion with incorrect one.
> >
> > вт, 10 апр. 2018 г. в 18:24, Dmitriy Setrakyan :
> >
> > > Ilya, can we find out why pure in-memory scenario also had a
> performance
> > > drop and which commit caused it? It should not be affected by changes
> in
> &g
gt;>>> What Ivan mentioned here as drop, in relation to old
> > mode
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> DEFAULT
> > >>>>>>>>>>>>>>>> (FSYNC
> > >>>>>>>>>>> now), is still significant perfromance boost.
> > >>>>>>>>>>>>>>>>> Sincerely,
> > >>>>>>>>>>>>>>>>>> Dmitriy Pavlov
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ср, 21 мар. 2018 г. в 17:56, Ivan Rakov <
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com
> > >>>>>>>>>>>>>>>> :
> > >>>>>>>>>> I've attached benchmark results to the JIRA ticket.
> > >>>>>>>>>>>> We observe ~7% drop in "fair" LOG_ONLY_SAFE mode,
> > >>>>>>>>>>>>>>>>>>> independent
> > >>>>>>>>>>>>>>>>> of
> > >>>>>>>>> WAL
> > >>>>>>>>>>> compaction enabled flag. It's pretty significant drop: WAL
> > >>>>>>>>>>>>>>>>> compaction
> > >>>>>>>>>>>>>>>>> itself gives only ~3% drop.
> > >>>>>>>>>>>>>>>>> I see two options here:
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> 1) Change LOG_ONLY behavior. That implies that we'll
> be
> > >>>>>>>>>>>>>>>>>>> ready
> > >>>>>>>>>>>>>>>>> to
> > >>>>>>>>> release
> > >>>>>>>>>>> AI 2.5 with 7% drop.
> > >>>>>>>>>>>>>>>>>> 2) Introduce LOG_ONLY_SAFE, make it default, add
> release
> > >>>>>>>>>>>>>>>>>>> note
> > >>>>>>>>>>>>>>>>> to AI
> > >>>>>>>>> 2.5
> > >>>>>>>>>>>>>>>>>> that we added power loss durability in default mode,
> but
> > >>>>>>>>>>>>>>>>> user
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> may
> > >>>>>>>>>>>>>>> fallback to previous LOG_ONLY in order to retain
> > >>>>>>>>>> performance.
> > >>>>>>>>>>>>>>>>> Thoughts?
> > >>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>>> Ivan Rakov
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> On 20.03.2018 16:00, Ivan Rakov wrote:
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> Val,
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> If a storage is in
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> corrupted state, does it mean that it needs to be
> > >>>>>>>>>>>>>>>>>>>>> completely
> > >>>>>>>>>>>>>>>>>>> removed
> > >>>>>>>>>> and
> > >>>>>>>>>>>>>>>>>> cluster needs to be restarted without data?
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> Yes, there's a chance that in LOG_ONLY all local data
> > >> will
> > >>>>>>>>>>>>>>>>>>>> be
> > >>>>>>>>>>>>>>>>>> lost,
> > >>>>>>>>>> but only in *power loss**/ OS crash* case.
> > >>>>>>>>>>>>>>>>> kill -9, JVM crash, death of critical system thread and
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> all
> > >>>>>>>>>>>>>>>>>> other
> > >>>>>>>>> cases that usually take place are variations of *process
> > >>>>>>>>>>>>>>>>>>>> crash*.
> > >>>>>>>>>>>>>>>>>> All
> > >>>>>>>>>>> WAL modes (except NONE, of course) ensure corruption-safety
> > >>>>>>>>>>>>>>>>> in
> > >>>>>>>>>>>>>>> case
> > >>>>>>>>> of
> > >>>>>>>>>>>>>>>>> process crash.
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> If so, I'm not sure any mode
> > >>>>>>>>>>>>>>>>>>>> that allows corruption makes much sense to me.
> > >>>>>>>>>>>>>>>>>>>>> It depends on performance impact of enforcing
> > >> power-loss
> > >>>>>>>>>>>>>>>>>>>> corruption
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> safety. Price of full protection from power loss is
> > high
> > >> -
> > >>>>>>>>>>>>>>>>> FSYNC
> > >>>>>>>>>>>>>> is
> > >>>>>>>>> way slower (2-10 times) than other WAL modes. The question is
> > >>>>>>>>>>>>>>>>> whether
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ensuring weaker guarantees (corruption can't happen,
> but
> > >>>>>>>>>>>>>>>>>> loss
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> of
> > >>>>>>>>>>>>>>> last
> > >>>>>>>>>> updates can) will affect performance as badly as strong
> > >>>>>>>>>>>>>>>>>> guarantees.
> > >>>>>>>>>>>>>>>>>> I'll share benchmark results soon.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> Ivan Rakov
> > >>>>>>>>>>>>>>>>>>>> On 20.03.2018 5:09, Valentin Kulichenko wrote:
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> Guys,
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> What do we understand under "data corruption" here?
> > If
> > >> a
> > >>>>>>>>>>>>>>>>>>>>> storage
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> is
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> in
> > >>>>>>>>>>>>>>>>>> corrupted state, does it mean that it needs to be
> > >> completely
> > >>>>>>>>>>>>>>>>>> removed
> > >>>>>>>>>>>>>>>>>>> and
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> cluster needs to be restarted without data? If so, I'm
> > not
> > >>>>>>>>>>>>>>>>>> sure
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> any
> > >>>>>>>>>> mode
> > >>>>>>>>>>>>>>>>>> that allows corruption makes much sense to me. How am
> I
> > >>>>>>>>>>>>>>>>>> supposed
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> to
> > >>>>>>>>>>> use a
> > >>>>>>>>>>>>>>>>>> database, if virtually any failure can end with
> complete
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> loss of
> > >>>>>>>>>>>>>>>>>>>>> data?
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> In any case, this definitely should not be a default
> > >>>>>>>>>>>>>>>>>> behavior.
> > >>>>>>>>>>>>>>>> If
> > >>>>>>>>> user ever
> > >>>>>>>>>>>>>>>>>> switches to corruption-unsafe mode, there should be a
> > >>>>>>>>>>>>>>>>>> clear
> > >>>>>>>>>>>>>>>>>>> warning
> > >>>>>>>>> about
> > >>>>>>>>>>>>>>>>>> this.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> -Val
> > >>>>>>>>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 1:06 AM, Ivan Rakov <
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com>
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>> Ticket to track changes:
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-7754
> > >>>>>>>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>>>>>> Ivan Rakov
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> On 16.03.2018 10:58, Dmitriy Setrakyan wrote:
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 12:55 AM, Ivan Rakov <
> > >>>>>>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>> Vladimir,
> > >>>>>>>>>>>>>>>>>>>> Unlike BACKGROUND, LOG_ONLY provides strict write
> > >>>>>>>>>>>>>>>>>>>>>>> guarantees
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> unless power
> > >>>>>>>>>>> loss has happened.
> > >>>>>>>>>>>>>>>>>>>>>>>> Seems like we need to measure performance
> > difference
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> to
> > >>>>>>>>>>>>>>>>>>>>>> decide
> > >>>>>>>>> whether do
> > >>>>>>>>>>>>>>>>>>>>> we need separate WAL mode. If it will be invisible,
> > >>>>>>>>>>>>>>>>>> we'll
> > >>>>>>>>>>>>>>>>>>>>>> just
> > >>>>>>>>>> fix
> > >>>>>>>>>>>>>>>>>>>>> these
> > >>>>>>>>>>>>>>>>>> bugs without introducing new mode; if it will be
> > >>>>>>>>>>>>>>>>>>>> perceptible,
> > >>>>>>>>>>>>>>>>>>>>>>>> we'll
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> continue the discussion about introducing
> > >>>>>>>>>>>>>>>>>>>>>> LOG_ONLY_SAFE.
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> Makes sense?
> > >>>>>>>>>>>>>>>>>>>> Yes, this sounds like the right approach.
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>
> >
> >
>
--
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com
Ilya Suntsov created IGNITE-7768:
Summary: No description for
org.apache.ignite.ml.nn.trainers.distributed
Key: IGNITE-7768
URL: https://issues.apache.org/jira/browse/IGNITE-7768
Project: Ignite
Ilya Suntsov created IGNITE-7410:
Summary: IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs
Key: IGNITE-7410
URL: https://issues.apache.org/jira/browse/IGNITE-7410
Project: Ignite
Ilya Suntsov created IGNITE-7245:
Summary: Missing description in javadoc for ignite-dev-utils
Key: IGNITE-7245
URL: https://issues.apache.org/jira/browse/IGNITE-7245
Project: Ignite
Issue
Ilya Suntsov created IGNITE-7244:
Summary: Missing README.txt for ignite-dev-utils module
Key: IGNITE-7244
URL: https://issues.apache.org/jira/browse/IGNITE-7244
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-7241:
Summary: Create shell (bat) script for run IgniteWalConverter
Key: IGNITE-7241
URL: https://issues.apache.org/jira/browse/IGNITE-7241
Project: Ignite
Issue
Ilya Suntsov created IGNITE-7240:
Summary: Upload ignite-dev-utils module in maven
Key: IGNITE-7240
URL: https://issues.apache.org/jira/browse/IGNITE-7240
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-7212:
Summary: Load stoped after server node kill
Key: IGNITE-7212
URL: https://issues.apache.org/jira/browse/IGNITE-7212
Project: Ignite
Issue Type: Bug
ENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE>
> >>> So it should be all good for inclusion.
> >>>
> >>> --
> >>> Ilya Kasnacheev.
> >>>
> >>> 2017-08-25 18:48 GMT+03:00 Denis Magda :
>
ENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE>
> >>> So it should be all good for inclusion.
> >>>
> >>> --
> >>> Ilya Kasnacheev.
> >>>
> >>> 2017-08-25 18:48 GMT+03:00 Denis Magda :
>
Ilya Suntsov created IGNITE-6561:
Summary: Include sqlline in Apache Ignite
Key: IGNITE-6561
URL: https://issues.apache.org/jira/browse/IGNITE-6561
Project: Ignite
Issue Type: Improvement
Ilya Suntsov created IGNITE-6478:
Summary: IndexOutOfBoundsException jdbc2
Key: IGNITE-6478
URL: https://issues.apache.org/jira/browse/IGNITE-6478
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-6479:
Summary: IndexOutOfBoundsException jdbc2
Key: IGNITE-6479
URL: https://issues.apache.org/jira/browse/IGNITE-6479
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-6457:
Summary: Incorrect exception when used schema name in lower case
Key: IGNITE-6457
URL: https://issues.apache.org/jira/browse/IGNITE-6457
Project: Ignite
Ilya Suntsov created IGNITE-6448:
Summary: Select * doesn't return new field name after concurrent
ALTER TABLE
Key: IGNITE-6448
URL: https://issues.apache.org/jira/browse/IGNITE-6448
Project: I
; Please start voting.
> >
> > +1 - to accept Apache Ignite 2.2.0-RC2
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 2.2.0-RC2 (explain why)
> >
> > This vote will go for 72 hours.
> >
>
--
Ilya Suntsov
EVNOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=DEVNOTES.txt;hb=refs/tags/2.2.0-rc1
> >
> > RELEASE NOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.2.0-rc1
> >
> &g
Ilya Suntsov created IGNITE-6315:
Summary: Exception during DistributedRegressionExample (ML)
Key: IGNITE-6315
URL: https://issues.apache.org/jira/browse/IGNITE-6315
Project: Ignite
Issue
; [3] https://dotnet.github.io/docfx/
> [4] https://issues.apache.org/jira/browse/IGNITE-6253
> [5] https://ptupitsyn.github.io/docfx-test/api/index.html
>
--
Ilya Suntsov
Ilya Suntsov created IGNITE-6226:
Summary: Review docs for integration with Apache Zeppelin
Key: IGNITE-6226
URL: https://issues.apache.org/jira/browse/IGNITE-6226
Project: Ignite
Issue Type
rview+sqlline+tool
The most problems with sqlline relate with some issues from our side or
some unsupported features.
Would be nice to add tool like this (sqlline or something else) in our
project.
Have you any objections or other thoughts?
--
Ilya Suntsov
Ilya Suntsov created IGNITE-6177:
Summary: Update docs for integration with Apache Zeppelin
Key: IGNITE-6177
URL: https://issues.apache.org/jira/browse/IGNITE-6177
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-6152:
Summary: Wrong response from grid via jdbc driver
Key: IGNITE-6152
URL: https://issues.apache.org/jira/browse/IGNITE-6152
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-6126:
Summary: Compilation error (yardstick repo)
Key: IGNITE-6126
URL: https://issues.apache.org/jira/browse/IGNITE-6126
Project: Ignite
Issue Type: Bug
Lgpl binaries should not to be in svn. This build will be removed.
15 июля 2017 г. 1:52 PM пользователь "Sergey Kozlov"
написал:
> Igniters
>
> Could someone explain why we include LGPL binary fabric [1] in the release?
> Either it was a mistake or we should upload also SHA1/MD5/ASC checksums as
Ilya Suntsov created IGNITE-5735:
Summary: NPE during populated data (CacheQueryDdlExample)
Key: IGNITE-5735
URL: https://issues.apache.org/jira/browse/IGNITE-5735
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-5538:
Summary: NPE (PersistentStoreExample)
Key: IGNITE-5538
URL: https://issues.apache.org/jira/browse/IGNITE-5538
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-5537:
Summary: bin/control.sh add validation of input parameters
Key: IGNITE-5537
URL: https://issues.apache.org/jira/browse/IGNITE-5537
Project: Ignite
Issue
Ilya Suntsov created IGNITE-5098:
Summary: Missed ignite-rocketmq/licenses/ignite-2.0.txt
Key: IGNITE-5098
URL: https://issues.apache.org/jira/browse/IGNITE-5098
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-5096:
Summary: Too many files with unapproved license
Key: IGNITE-5096
URL: https://issues.apache.org/jira/browse/IGNITE-5096
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-5022:
Summary: Duplicates of JVM OPTS [yardstick]
Key: IGNITE-5022
URL: https://issues.apache.org/jira/browse/IGNITE-5022
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-4913:
Summary: Update yardstick properties files
Key: IGNITE-4913
URL: https://issues.apache.org/jira/browse/IGNITE-4913
Project: Ignite
Issue Type: Improvement
Ilya Suntsov created IGNITE-4787:
Summary: Performance drop sql-merge-all 1.9 vs 1.8
Key: IGNITE-4787
URL: https://issues.apache.org/jira/browse/IGNITE-4787
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-4743:
Summary: Set AUTO_COPY to false when it wasn't define in
properties file
Key: IGNITE-4743
URL: https://issues.apache.org/jira/browse/IGNITE-4743
Project: I
Ilya Suntsov created IGNITE-4668:
Summary: Doesn't work "manual" yardsticks when ip of server/driver
not equal ip of ethernet interface
Key: IGNITE-4668
URL: https://issues.apache.org/jira/bro
Ilya Suntsov created IGNITE-4512:
Summary: Doesnt work sql-delete benchmark
Key: IGNITE-4512
URL: https://issues.apache.org/jira/browse/IGNITE-4512
Project: Ignite
Issue Type: Bug
Denis,
I think we can remove all configs except:
benchmark-multicast.properties
benchmark.properties
ignite-base-config.xml
ignite-localhost-config.xml
ignite-multicast-config.xml
2016-12-28 2:49 GMT+03:00 Denis Magda :
> I would have only those configs that are useful. Ilya Sunt
Ilya Suntsov created IGNITE-4373:
Summary: Performance drop tx-putAll 1.8.0 vs 1.7.0
Key: IGNITE-4373
URL: https://issues.apache.org/jira/browse/IGNITE-4373
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-4282:
Summary: Javadoc broken
Key: IGNITE-4282
URL: https://issues.apache.org/jira/browse/IGNITE-4282
Project: Ignite
Issue Type: Bug
Components
Ilya Suntsov created IGNITE-3814:
Summary: Unstable results of compute benchmarks
Key: IGNITE-3814
URL: https://issues.apache.org/jira/browse/IGNITE-3814
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-3387:
Summary: NPE deploy ignite with mesos
Key: IGNITE-3387
URL: https://issues.apache.org/jira/browse/IGNITE-3387
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-3176:
Summary: Need to create gc log for each client separately [
yardstick-ignite ]
Key: IGNITE-3176
URL: https://issues.apache.org/jira/browse/IGNITE-3176
Project
Ilya Suntsov created IGNITE-3148:
Summary: No description for package
org.apache.ignite.cache.jta.websphere in javadoc
Key: IGNITE-3148
URL: https://issues.apache.org/jira/browse/IGNITE-3148
Project
Ilya Suntsov created IGNITE-3106:
Summary: Yardstick can't parse /config/queries.txt with license
header
Key: IGNITE-3106
URL: https://issues.apache.org/jira/browse/IGNITE-3106
Project: I
Ilya Suntsov created IGNITE-3103:
Summary: No description in javadoc (kafka module)
Key: IGNITE-3103
URL: https://issues.apache.org/jira/browse/IGNITE-3103
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-3070:
Summary: Failed to fetch data from node at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor
Key: IGNITE-3070
URL: https://issues.apache.org/jira
Ilya Suntsov created IGNITE-2932:
Summary: IgniteFutureTimeoutException during the run of load test
(cache-tx-invoke)
Key: IGNITE-2932
URL: https://issues.apache.org/jira/browse/IGNITE-2932
Project
Ilya Suntsov created IGNITE-2896:
Summary: IgniteFutureTimeoutException during load test (yardstick)
Key: IGNITE-2896
URL: https://issues.apache.org/jira/browse/IGNITE-2896
Project: Ignite
Ilya Suntsov created IGNITE-2867:
Summary: IgniteConsistencyException during running load test
(cache-atomic-invoke-retry-validator)
Key: IGNITE-2867
URL: https://issues.apache.org/jira/browse/IGNITE-2867
Ilya Suntsov created IGNITE-2847:
Summary: Failed atomic-offheap-invoke-retry load test
Key: IGNITE-2847
URL: https://issues.apache.org/jira/browse/IGNITE-2847
Project: Ignite
Issue Type
Ilya Suntsov created IGNITE-2638:
Summary: "Connection to Ignite Web Agent is not established" form
not in focus
Key: IGNITE-2638
URL: https://issues.apache.org/jira/browse/IGNITE-2638
Ilya Suntsov created IGNITE-2327:
Summary: No error message when visorui connects to sequre grid
without permissions
Key: IGNITE-2327
URL: https://issues.apache.org/jira/browse/IGNITE-2327
Project
Ilya Suntsov created IGNITE-2176:
Summary: Not valid exceptions in case when example can't works
with remote node started with server classpath (Java 8)
Key: IGNITE-2176
URL: https://issues.apache.org/jira/b
Ilya Suntsov created IGNITE-2175:
Summary: Not valid exceptions in case when example can't works
with remote node started with server classpath (Java 7)
Key: IGNITE-2175
URL: https://issues.apache.org/jira/b
.sh out of the box, but
> if
> > > > user put example cache store factory class into \libs folder example
> > will
> > > > run.
> > > >
> > > > >>
> > > >
> > > >
> > >
> >
> org.apache.ignite.examples.binary.datagrid.store.auto.CacheBinaryAutoStoreExample
> > > > This example ALLOW to start remote nodes via ignite.sh.
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Ilya Suntsov
Ilya Suntsov created IGNITE-2158:
Summary: Null values in examples output
Key: IGNITE-2158
URL: https://issues.apache.org/jira/browse/IGNITE-2158
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-2128:
Summary: Incorrect output in CacheClientBinaryQueryExample
Key: IGNITE-2128
URL: https://issues.apache.org/jira/browse/IGNITE-2128
Project: Ignite
Issue
Ilya Suntsov created IGNITE-2078:
Summary: Need to clean cache after query in CacheQueryExample
Key: IGNITE-2078
URL: https://issues.apache.org/jira/browse/IGNITE-2078
Project: Ignite
Issue
Ilya Suntsov created IGNITE-2041:
Summary: CacheAutoStoreExample: Failed to find class with given
class loader for unmarshalling
Key: IGNITE-2041
URL: https://issues.apache.org/jira/browse/IGNITE-2041
Ilya Suntsov created IGNITE-2035:
Summary: Misprint in javadoc
Key: IGNITE-2035
URL: https://issues.apache.org/jira/browse/IGNITE-2035
Project: Ignite
Issue Type: Bug
Components
Ilya Suntsov created IGNITE-2034:
Summary: Need to print information about marshaller in log (for
yardstick-ignite)
Key: IGNITE-2034
URL: https://issues.apache.org/jira/browse/IGNITE-2034
Project
Ilya Suntsov created IGNITE-2024:
Summary: CacheAutoStoreExample: Failed to execute compound future
reducer
Key: IGNITE-2024
URL: https://issues.apache.org/jira/browse/IGNITE-2024
Project: Ignite
Ilya Suntsov created IGNITE-1521:
Summary: Exception when running sql benchmark on AWS
Key: IGNITE-1521
URL: https://issues.apache.org/jira/browse/IGNITE-1521
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-1490:
Summary: Memory leaks during load testing (+ nearcache)
Key: IGNITE-1490
URL: https://issues.apache.org/jira/browse/IGNITE-1490
Project: Ignite
Issue Type
Hi Igniters,
I plan to create 'Testing and benchmarking' page on Wiki in order for
everyone from community to be able to run benchmarks and get latest
information about performance of Apache Ignite.
Thoughts?
--
Ilya Suntsov
Ilya Suntsov created IGNITE-1368:
Summary: Unable to build apache ignite
Key: IGNITE-1368
URL: https://issues.apache.org/jira/browse/IGNITE-1368
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-1291:
Summary: Bad link on https://ignite.incubator.apache.org
Key: IGNITE-1291
URL: https://issues.apache.org/jira/browse/IGNITE-1291
Project: Ignite
Issue Type
94 matches
Mail list logo
