GitHub user a-polyakov opened a pull request:
https://github.com/apache/ignite/pull/4656
IGNITE-9440 control.sh --wal delete do not delete files
Do not delete the files by the utility on command "control.sh --wal delete".
Remain both checkpoints and wal in the archive.
You can
Alexand Polyakov created IGNITE-9440:
Summary: control.sh --wal delete do not delete files
Key: IGNITE-9440
URL: https://issues.apache.org/jira/browse/IGNITE-9440
Project: Ignite
Issue
Thank you, Denis
Regards,
Saikat
On Thu, Aug 30, 2018 at 7:01 PM, Denis Magda wrote:
> Hello Saikat,
>
> Hopefully, someone from the community will review the changes in the
> nearest time.
>
> --
> Denis
>
> On Thu, Aug 30, 2018 at 4:37 PM Saikat Maitra
> wrote:
>
> > Hello,
> >
> > The
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*Recently contributed test failed in master
GridIndexRebuildSelfTest.testMvccEnabled
Hello Saikat,
Hopefully, someone from the community will review the changes in the
nearest time.
--
Denis
On Thu, Aug 30, 2018 at 4:37 PM Saikat Maitra
wrote:
> Hello,
>
> The changes for IGNITE-3303 for IgniteSource is complete. This will help is
> streaming data from Ignite cluster and
Hello,
The changes for IGNITE-3303 for IgniteSource is complete. This will help is
streaming data from Ignite cluster and process, filter, transform and
publish it back to Ignite using IgniteSink or in any other data sink.
I was hoping if the changes can be approved I can go ahead merge the
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*Recently contributed test failed in master
GridIndexRebuildSelfTest.testMvccEnabled
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 to see such valuable community member in
> PMC role.
>
> чт, 30 авг. 2018 г. в 20:11, Dmitriy Govorukhin <
>
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
IgniteConfigurationParityTest.TestIgniteConfiguration
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4642
---
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
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
IgniteConfigurationParityTest.TestIgniteConfiguration
Dmitriy,
Congratulations. This is very nice to see such valuable community member in
PMC role.
чт, 30 авг. 2018 г. в 20:11, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:
> Dmitriy,
>
> My congratulations!
> Thank you for your work!
>
> On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov
>
Dmitriy,
Congratulations, you finally got it :)
чт, 30 авг. 2018 г. в 20:25, Ivan Rakov :
> Dmitriy,
>
> Congratulations! Your new role is well deserved, keep going!
>
> Best Regards,
> Ivan Rakov
>
> On 30.08.2018 1:20, Dmitriy Setrakyan wrote:
> > Dmitriy, congrats! Looking forward to many
Welcome Sergey! Added you to JIRA.
--
Denis
On Thu, Aug 30, 2018 at 10:16 AM antonovsergey93
wrote:
> Hello Team,
>
> I'd like to join to Apache Ignite development.
> Currently, I work on IGNITE-9438
> https://issues.apache.org/jira/browse/IGNITE-9438
>
> My Jira login is antonovsergey93
>
>
Andrew Mashenkov created IGNITE-9439:
Summary: Grid hangs after cache start failure.
Key: IGNITE-9439
URL: https://issues.apache.org/jira/browse/IGNITE-9439
Project: Ignite
Issue Type:
Dmitriy,
Congratulations! Your new role is well deserved, keep going!
Best Regards,
Ivan Rakov
On 30.08.2018 1:20, Dmitriy Setrakyan wrote:
Dmitriy, congrats! Looking forward to many contributions to come.
On Wed, Aug 29, 2018 at 12:35 PM, Denis Magda wrote:
The Project Management
Hello Team,
I'd like to join to Apache Ignite development.
Currently, I work on IGNITE-9438
https://issues.apache.org/jira/browse/IGNITE-9438
My Jira login is antonovsergey93
BR, Sergey Antonov
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Dmitriy,
My congratulations!
Thank you for your work!
On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov wrote:
> Dmitry,
>
> My congratulations!
> Thank you for guiding and helping the community members and me, in
> particular,
> to follow the Apache Way principles and also for your
Sergey Antonov created IGNITE-9438:
--
Summary: StandaloneWalRecordsIterator file descriptors leak
Key: IGNITE-9438
URL: https://issues.apache.org/jira/browse/IGNITE-9438
Project: Ignite
Dmitriy,
Yes, as you can see in the first message in this thread, request
*DynamicServicesChangeRequestBatchMessage* is a container which is
able to transfer several actions for batch operations like
deployAll/cancelAll.
Also, it will be possible to combine operations for *deploy* and
*undeploy*
Yury Babak created IGNITE-9437:
--
Summary: [ML] Add performance benchmarks
Key: IGNITE-9437
URL: https://issues.apache.org/jira/browse/IGNITE-9437
Project: Ignite
Issue Type: Improvement
I also hope that we have some batching API to allow deployment of multiple
services together, either on grid startup or during the call to "deploy..."
API.
D.
On Thu, Aug 30, 2018 at 5:04 AM, Vyacheslav Daradur
wrote:
> Hi Igniters!
>
> I had a private talk about new Service Grid design with:
Very nice! Looking forward to seeing this functionality in 2.7 release.
On Thu, Aug 30, 2018 at 5:22 AM, Yakov Zhdanov wrote:
> Great news, Vladimir! Congratulations!
>
> --Yakov
>
> 2018-08-30 15:15 GMT+03:00 Vladimir Ozerov :
>
> > Igniters,
> >
> > I am glad to announce that we finally
GitHub user dehasi opened a pull request:
https://github.com/apache/ignite/pull/4655
INGITE-9285 Add MaxAbs scaler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dehasi/ignite
feature/IGNITE-9285-add-abs-max-scaler
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4612
---
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/4606
---
Github user pavlukhin closed the pull request at:
https://github.com/apache/ignite/pull/4622
---
Github user pavlukhin closed the pull request at:
https://github.com/apache/ignite/pull/4631
---
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4654
IGNITE-8149: MVCC TX: Size method should use tx snapshot
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8149
Github user kukushal closed the pull request at:
https://github.com/apache/ignite/pull/4653
---
Andrew Mashenkov created IGNITE-9436:
Summary: Compute task may cause a deadlock on node stop.
Key: IGNITE-9436
URL: https://issues.apache.org/jira/browse/IGNITE-9436
Project: Ignite
Yes, of course I started with measuring of total iteration time. After that I
found that throughput is about 200Mb/s, then I started looking for a
bottleneck. Because "downloading" time is less than "waiting" time I
conclude that "waiting" step is bottleneck and so that this thread has been
GitHub user kukushal opened a pull request:
https://github.com/apache/ignite/pull/4653
Fixed Ignite Kafka Source Connector immediately existing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
In this case I would not advise to measure how long does it take to get the
first byte. We may set page size to 1 and get that byte very quickly, but
it doesn't help you to iterate over all results quickly. Correct
measurement here would be to calculate total iteration time. Provided that
object
To be precise it's not only about first page, it's about getting next pages
as well.
Regarding use case, in my client application I need to iterate over the
dataset stored in Apache Ignite as fast as it possible. It means I should
provide maximal throughput for simple "read all" operation.
--
Vladimir Ozerov created IGNITE-9435:
---
Summary: Document MVCC
Key: IGNITE-9435
URL: https://issues.apache.org/jira/browse/IGNITE-9435
Project: Ignite
Issue Type: Task
Components:
GitHub user voropava opened a pull request:
https://github.com/apache/ignite/pull/4652
IGNITE-9433 Extracted zip suffix constant
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9433
Alternatively
Anton,
I still struggle to understand the problem. Delay in getting the first
page is not a problem on its own. But it might be a problem for your use
case. My question is - what is the use case and what is your goal?
Minimal latency? Maximal throughout? Getting the first result ASAP? Getting
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4562
---
Github user voropava closed the pull request at:
https://github.com/apache/ignite/pull/4651
---
Andrew Mashenkov created IGNITE-9434:
Summary: Create suites for MVCC tests.
Key: IGNITE-9434
URL: https://issues.apache.org/jira/browse/IGNITE-9434
Project: Ignite
Issue Type: Task
GitHub user voropava opened a pull request:
https://github.com/apache/ignite/pull/4651
IGNITE-9433 Extractted zip suffix constant
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9433
Alternatively
Hi Team,
I'd like to join to Apache Ignite development.
Especially to the ML part.
Currently, I work on IGNITE-9433
https://issues.apache.org/jira/browse/IGNITE-9433
My Jira login is voropava
Best regards,
Pavel
Pavel Voronkin created IGNITE-9433:
--
Summary: Refactoring to improve constant usage for file suffixes
Key: IGNITE-9433
URL: https://issues.apache.org/jira/browse/IGNITE-9433
Project: Ignite
BTW, measurements for the example I've been talking above:
Page size 5 Mb, waiting time 119.85 ± 6.72 ms
Page size 10 Mb, waiting time 157.70 ± 15.35 ms
Page size 20 Mb, waiting time 204.50 ± 19.18 ms
Page size 50 Mb, waiting time 264.70 ± 22.30 ms
Page size 100 Mb, waiting time 463.35 ± 17.12 ms
I have already experimented with different page sizes and found out that
"downloading" time is relatively small compare to this "waiting" time, so
I've decided that this "waiting" is bottleneck and that's why I'm talking
about it and measuring it. In case of AWS 10Gbit network allows us to
receive
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3559
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3220
---
I am not sure what is the purpose of measuring receive time of the first
byte. Please try to measure time of getting the first page, or the whole
result set you are interested in.
The main purpose of page size is to better utilize network and decrease
number of request responses. If you are
Great news, Vladimir! Congratulations!
--Yakov
2018-08-30 15:15 GMT+03:00 Vladimir Ozerov :
> Igniters,
>
> I am glad to announce that we finally merged MVCC and transactional SQL
> support to master branch.
>
> This long journey started more than a year ago with multiple design
> brainstorm
Igniters,
I am glad to announce that we finally merged MVCC and transactional SQL
support to master branch.
This long journey started more than a year ago with multiple design
brainstorm sessions, conducted by Apache Ignite fellows - Semen Boikov,
Alexey Goncharuk, Sergi Vladykin.
As things had
Hi,
I prepared an example that reproduces what I'm talking about. Please take a
look:
https://github.com/dmitrievanthony/slow-scan-query-reproducer/blob/master/src/main/java/Client.java.
I calculate time between the has been sent and the result is ready to be
received (not fully received). And I
Anton Dmitriev created IGNITE-9432:
--
Summary: Investigate ability to make ScanQuery faster
Key: IGNITE-9432
URL: https://issues.apache.org/jira/browse/IGNITE-9432
Project: Ignite
Issue
Hi Igniters!
I had a private talk about new Service Grid design with: Alexey
Goncharuk, Vladimir Ozerov, Denis Mekhanikov, Nikolay Izhikov, Anton
Vinogradov and I'd like to share results.
Design looks good in general, but we have decided to improve the
unified flow of requests processing as
BTW, Taras has created the ticket
https://issues.apache.org/jira/browse/IGNITE-9379.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Dmitry,
My congratulations!
Thank you for guiding and helping the community members and me, in
particular,
to follow the Apache Way principles and also for your contribution.
On Wed, 29 Aug 2018 at 22:31 Denis Magda wrote:
> The Project Management Committee (PMC) for Apache Ignite
> has
Stanilovsky Evgeny created IGNITE-9431:
--
Summary: Documentation for zk paths used by ZookeeperDiscovery.
Key: IGNITE-9431
URL: https://issues.apache.org/jira/browse/IGNITE-9431
Project: Ignite
Hi everyone,
I think email from the bot is something exceptional. In this case author
and committer already ignored test failures. So dev list is the last hope
that someone can come and fix the failure.
Other emails come from human actions, so I'm happy that so many actions
occur in the
ARomantsov created IGNITE-9430:
--
Summary: Add ability to override all caches's "rebalanceThrottle"
option via JVM node option
Key: IGNITE-9430
URL: https://issues.apache.org/jira/browse/IGNITE-9430
> 2. MTCGA messages should mention the commiter and authors of the "bad"
commit.
But this is not always possible.
2018-08-30 13:04 GMT+03:00 Dmitrii Ryabov :
> Vladimir, your idea is good, but...
> 1. Who should be mentioned in messages like PR or JIRA ticket creation? As
> I see, only these
Vladimir, your idea is good, but...
1. Who should be mentioned in messages like PR or JIRA ticket creation? As
I see, only these messages clutter up the nabble.
2. MTCGA messages should mention the commiter and authors of the "bad"
commit.
2. Comments and changes in PR, tickets, and reviews
Huge +1 for separate channel for bots and direct notification.
On Thu, Aug 30, 2018 at 12:20 PM Vladimir Ozerov
wrote:
> This is somewhat controversial question. Some people has filters, some
> doesn't. And it s true that at the moment it is hard to find pieces of
> human communication in tons
This is somewhat controversial question. Some people has filters, some
doesn't. And it s true that at the moment it is hard to find pieces of
human communication in tons of automated e-mails (JIRA, GitHub, TC bot).
If to put JIRA and GitHub aside (let's do not mix things), personally
content of TC
Alexey Goncharuk created IGNITE-9429:
Summary:
GridCacheReplicatedDataStructuresFailoverSelfTest#testAtomicSequenceConstantTopologyChange
is flaky
Key: IGNITE-9429
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4646
---
Hi Dmitriy,
Why do you thing that results are not fetched to the client at this point?
We respond to the client with first page.
On Thu, Aug 23, 2018 at 5:22 PM dmitrievanthony
wrote:
> I checked and it looks like the result is the same (or even worse, I get
> 1150ms with page size 1000, but
Reference:
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheScanQueryRequest#process
On Thu, Aug 30, 2018 at 11:53 AM Vladimir Ozerov
wrote:
> Hi Dmitriy,
>
> Why do you thing that results are not fetched to the client at this point?
> We respond to the client with first
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4588
---
Roman Kondakov created IGNITE-9428:
--
Summary: MVCC TX: Multiple H2ResultSetIterator closing leads to
assertion in MvccProcessor
Key: IGNITE-9428
URL: https://issues.apache.org/jira/browse/IGNITE-9428
I guess, nobody uses it because it's flooded by bots.
It may be useful to lookup old threads for people, who are not subscribed
to the mailing list from the beginning of time.
Denis
чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan :
> Is anyone in the community using or was using Nabble for the
Stepan Pilschikov created IGNITE-9427:
-
Summary: SQL MVCC: old data read after parallel update with
autoCommit=false
Key: IGNITE-9427
URL: https://issues.apache.org/jira/browse/IGNITE-9427
73 matches
Mail list logo
