GitHub user pvinokurov opened a pull request:
https://github.com/apache/ignite/pull/4338
IGNITE-8968 Failed to shutdown node due to "Error saving backup value"
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
Pavel Vinokurov created IGNITE-8968:
---
Summary: Failed to shutdown node due to "Error saving backup value"
Key: IGNITE-8968
URL: https://issues.apache.org/jira/browse/IGNITE-8968
Project: Ignite
Hi Anton,
I checked your last comments in the ticket and left some responses. Please
check them and let me know
Thanks,
Amir
P.S. do you mind to have a chat/call through gitter/Skype to discuss the
details? Sometimes 5 minutes of chat can be more productive than long
running email chains. Please
I have received the attachments.
在 2018/7/10 上午6:23, Prachi Garg 写道:
I already sent him the export, but the attachments were huge. I think
that's why the email reply was not received by the dev list.
-P
On Mon, Jul 9, 2018 at 2:33 PM, Dmitry Pavlov wrote:
Igniters, was this question solved?
Denis Magda created IGNITE-8967:
---
Summary: Automatic Handling of Long Stop-the-World Pauses
Key: IGNITE-8967
URL: https://issues.apache.org/jira/browse/IGNITE-8967
Project: Ignite
Issue Type: N
I already sent him the export, but the attachments were huge. I think
that's why the email reply was not received by the dev list.
-P
On Mon, Jul 9, 2018 at 2:33 PM, Dmitry Pavlov wrote:
> Igniters, was this question solved? Is it possible to do such export?
>
> пт, 1 июн. 2018 г. в 19:40, 李玉珏@
Igniters,
Let me share some great news with you. ASF shared annual report [1] for
2018:
- Top 5 Apache developer email lists: *Ignite (1st!)*, Kafka, Tomcat,
Beam, and James
- Top 5 Apache user email lists: Lucene/Solr, *Ignite (2nd!)*, Flink,
Kafka, and Cassandra
- Top 5 Apache re
Igniters, was this question solved? Is it possible to do such export?
пт, 1 июн. 2018 г. в 19:40, 李玉珏@163 <18624049...@163.com>:
> Prachi,
>
>
> Can you help to export all the latest version of all documents to me?
> I am ready to make a synchronization of the chinese version of the
> document.
>
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4328
---
Done. Thank you for contribution and for review.
пн, 9 июл. 2018 г. в 12:37, Vyacheslav Daradur :
> Now changes look good to me.
>
> Dmitry, could you help with a final review and merge, please?
> On Mon, Jul 9, 2018 at 9:30 AM Vyacheslav Daradur
> wrote:
> >
> > Hi,
> >
> > I've commented your
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4337
IGNITE-8869: cancel patch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8869-revert
Alternatively you can re
I also tend to agree about updating checklist
About suite timeouts, I suspect there is one problem introduced recently
within 3 days, which caused this mass timeouts.
I hope Igniters will find out reason soon. In relation to compute we have
only 2 possible cause:
Ivan Daschinskiy (idaschinskiy) 2
If clientFailureDetectionTimeout is not set on server node, will it
use failureDetectionTimeout
instead?
Either way, this configuration seems to be a bit confusing, but I don't
think we can change it now. Let's just make sure it's properly documented.
-Val
On Mon, Jul 9, 2018 at 5:47 AM Stanisla
Hi Amir,
I reviewed the change and commented in the ticket.
-Val
On Fri, Jul 6, 2018 at 4:18 PM Amir Akhmedov
wrote:
> Igniters,
>
> Please review my changes. That's a simple change, a setter method was
> added.
>
> Thanks,
> Amir
>
Sounds reasonable.
I've satrted Data Structures suite hang investigation [1].
Igniters, especially commiters,
I know, you're busy, but it will be a great help to the project in case you
fix at least one hang per person.
[1] https://issues.apache.org/jira/browse/IGNITE-8783
пн, 9 июл. 2018 г. в 1
Hi folks,
My vote goes to the three-digits releases numbering - X.Y.Z. If we decide
to introduce betas or early access binaries then the version can be
extended to X.Y.Z-beta or X.Y.Z-ea.
--
Denis
On Fri, Jul 6, 2018 at 7:06 AM Dmitry Karachentsev <
dkarachent...@gridgain.com> wrote:
> Hi Dmitr
Prachi, thanks!
Documentation looks good now.
Best Regards,
Ivan Rakov
On 09.07.2018 22:06, Prachi Garg wrote:
Ivan,
I have fixed the documentation for baseline topology. Please review -
https://apacheignite.readme.io/v2.5/docs/baseline-topology#section-cluster-activation
-P
On Thu, Jul 5
Ivan,
I have fixed the documentation for baseline topology. Please review -
https://apacheignite.readme.io/v2.5/docs/baseline-topology#section-cluster-activation
-P
On Thu, Jul 5, 2018 at 11:55 AM, Prachi Garg wrote:
> Thanks Ivan. I will fix the doc accordingly.
>
> On Thu, Jul 5, 2018 at 5:3
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4336
IGNITE-7743: applied changes from outdated pull request
Fixed outdated pull request https://github.com/apache/ignite/pull/3761/files
You can merge this pull request into a Git repository by
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4335
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
Alternatively you can revi
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4270
---
Hi Ilya,
Welcome to the Apache Ignite Сommunity. I added you to the list of
contributord, so you could assign issue to yourself.
Looking forward to your contributions!
Sincerely,
Dmitriy Pavlov
P.S. Additional references for you that should boost your onboarding.
Please subscribe to both dev a
Hi Igniters,
Let's back to discussion of review checklist. Can we add more clarification
about running all suites on TeamCity?
My suggestion is: “All test suites MUST be run on TeamCity [3] before merge
to master, there MUST NOT be any test failures * and any tests\suites with
“execution timeouts
Awesome!
Thanks, Andrey!
> On 9 Jul 2018, at 18:57, Andrey Gura wrote:
>
> POM is updated in master branch.
>
> And no more commits to ignite-2.6 branch.
> On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote:
>>
>> Andrey,
>>
>> Answered at the same [1] issue.
>> Anyway, we have to increm
Thank you!
пн, 9 июл. 2018 г. в 18:57, Andrey Gura :
> POM is updated in master branch.
>
> And no more commits to ignite-2.6 branch.
> On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote:
> >
> > Andrey,
> >
> > Answered at the same [1] issue.
> > Anyway, we have to increment version now. We
POM is updated in master branch.
And no more commits to ignite-2.6 branch.
On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote:
>
> Andrey,
>
> Answered at the same [1] issue.
> Anyway, we have to increment version now. We had to do this at the moment
> we created ignite-2.6 branch.
> In case y
Greetings, Apache software enthusiasts!
(You’re getting this because you’re on one or more dev@ or users@ lists
for some Apache Software Foundation project.)
ApacheCon North America, in Montreal, is now just 80 days away, and
early bird prices end in just two weeks - on July 21. Prices will b
Alexei Scherbakov created IGNITE-8966:
-
Summary: IgnitePdsContinuousRestartTest is often timed out in
master
Key: IGNITE-8966
URL: https://issues.apache.org/jira/browse/IGNITE-8966
Project: Ignite
Andrey,
Answered at the same [1] issue.
Anyway, we have to increment version now. We had to do this at the moment
we created ignite-2.6 branch.
In case you have some issues with increment, I can do this by myself.
[1] https://issues.apache.org/jira/browse/IGNITE-7823
пн, 9 июл. 2018 г. в 16:35,
Hello Igniters,
Each cache group has “rebalance order” property. As javadoc for
getRebalanceOrder() says: “Note that cache with order {@code 0} does not
participate in ordering. This means that cache with rebalance order {@code
0} will never wait for any other caches. All caches with order {@code
I will side with Anton.
In any case right after branch creation, master version should be incremented.
Or version increase is planned right after 2.6 release?
> On 9 Jul 2018, at 16:32, Andrey Gura wrote:
>
> Anton,
>
> while version number is frequently used in Ignite code base I believe
>
Anton,
while version number is frequently used in Ignite code base I believe
that it's bad approach. See my comment to IGNITE-7823 [1] issue.
[1] https://issues.apache.org/jira/browse/IGNITE-7823
On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov wrote:
>
> Igniters,
>
> Ignite version still 2.6.0-
Yakov,
We can introduce several modes:
1) initial loading which replaces data (allowOverwrite=true) with initial
version or leaves it as is (allowOverwrite=false) and requires exclusive table
lock (fastest one)
2) continuous loading which has its own version and links the data as regular
trans
GitHub user andrewmed opened a pull request:
https://github.com/apache/ignite/pull/4334
IGNITE-8957: fix assert when histMap is empty
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8957
Alternative
Vladislav Pyatkov created IGNITE-8965:
-
Summary: Add logs in SegmentReservationStorage on exchange process
Key: IGNITE-8965
URL: https://issues.apache.org/jira/browse/IGNITE-8965
Project: Ignite
Server will use its failureDetectionTimeout when talking to servers and
clientFailureDetectionTimeout when talking to clients.
E.g. a Communication link from server to server uses a failureDetectionTimeout,
and server to client uses a clientFailureDetectionTimeout.
Client will use its failureDet
Alexey Kuznetsov created IGNITE-8964:
Summary: Web Console: Refactor versionService.since() method
Key: IGNITE-8964
URL: https://issues.apache.org/jira/browse/IGNITE-8964
Project: Ignite
Dmitriy,
Rollback from remote filter uses rollbackOnlyProxy [1], that's a special
proxy allows rollback from another thread.
It was specially designed to rollback transactions by "label" if necessary.
So, I'm just finishing "label feature" to make it more useful at real
production.
Here's the exa
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4333
IGNITE-8926 : Fixed deadlock when binary metadata got updated while holding
topology read lock.
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
I left a comments on jira. can you clarify it,please?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Stan, feel free to file the ticket. Just make sure to add detailed
description to it. Your suggestion seems to make sense.
--Yakov
Vasiliy Sisko created IGNITE-8963:
-
Summary: Web console: Wrong layout in caches table for long cache
name
Key: IGNITE-8963
URL: https://issues.apache.org/jira/browse/IGNITE-8963
Project: Ignite
> What is the difference between a lifecycle even and regular events?
Lifecycle events should be used when there is no opportunity for Ignite to
fire regular event, e.g. node stops or is not started yet. Please see
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/lifecycle/Lifec
Vasiliy Sisko created IGNITE-8962:
-
Summary: Web console: Failed to load blob on configuration pages
Key: IGNITE-8962
URL: https://issues.apache.org/jira/browse/IGNITE-8962
Project: Ignite
Is
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4332
IGNITE-8953 Retry to start up MBean server on other port.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8953
A
Hello everyone!
My name is Ilya. I want to contribute to Apache Ignite and want to start with
this issue - IGNITE-8923.
My JIRA ID is imurchenko. Any help on this will be appreciated.
Thanks!
Sergey created IGNITE-8961:
--
Summary: service deployment
Key: IGNITE-8961
URL: https://issues.apache.org/jira/browse/IGNITE-8961
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Vasiliy Sisko created IGNITE-8960:
-
Summary: Web console: Error in log on transition from advanced
page to
Key: IGNITE-8960
URL: https://issues.apache.org/jira/browse/IGNITE-8960
Project: Ignite
Igor,
I can't say if I agree with any of the suggestions. I would like us to
start from answering the question - what is data streamer used for?
First of all, for initial data loading. This should be super fast mode
probably ignoring all transactional semantics, but providing certain
guarantees f
Now changes look good to me.
Dmitry, could you help with a final review and merge, please?
On Mon, Jul 9, 2018 at 9:30 AM Vyacheslav Daradur wrote:
>
> Hi,
>
> I've commented your PR on the GitHub.
>
>
> On Mon, Jul 9, 2018 at 5:21 AM kcheng.mvp wrote:
> >
> > Dear igniters,
> >
> > does anyone
Ilya Borisov created IGNITE-8959:
Summary: Web console: agent manager modal throws an error
Key: IGNITE-8959
URL: https://issues.apache.org/jira/browse/IGNITE-8959
Project: Ignite
Issue Type:
Hi Igniters,
You know, we're currently developing fair MVCC for transactional caches (
https://issues-test.apache.org/jira/plugins/servlet/mobile#issue/IGNITE-4191
).
At now we're trying to make work IgniteDataStreamer with MVCC.
The problem is that MVCC requires linking between versions for che
Ilya Borisov created IGNITE-8958:
Summary: Web console: upgrade to AngularJS 1.7
Key: IGNITE-8958
URL: https://issues.apache.org/jira/browse/IGNITE-8958
Project: Ignite
Issue Type: Improvemen
53 matches
Mail list logo
