Re: TeamCity permissions

[Pavel Petroshenko]

Thank you, Denis! I need to have a role to be able to temporary rearrange
builds in the TC build queue for testing and CI integration purposes.

Vitaly, I would appreciate any help.

Thanks,
P.


On Fri, May 18, 2018 at 10:49 AM, Denis Magda  wrote:

> Hi Pavel,
>
> All the accounts are assigned Project developer role on TC that should
> provide anything you need to manage builds there.
>
> What specifically are you looking for? Please elaborate so that Vitaly can
> grant more permissions.
>
> Vitaly, please keep an eye on the conversation.
>
> --
> Denis
>
>
> On Fri, May 18, 2018 at 9:44 AM, Pavel Petroshenko 
> wrote:
>
> > Hi,
> >
> > Can anyone please grant TC permissions to manage jobs (reorder, etc) to:
> >
> > ekaterina.vergizova
> > alexey.kosenchuk
> > pavel.petroshenko
> >
> > Thanks!
> > p.
> >
>

Re: Request for contributors permissions

[Denis Magda]

Hello Uday and welcome!

I've added you to the contributors' list in JIRA.

Speaking about ELB Target Group based discovery, is it the same as this
type of ELB discovery already supported by Ignite?
https://apacheignite-mix.readme.io/docs/amazon-aws#amazon-elb-based-discovery



On Fri, May 18, 2018 at 8:48 AM, uday kale  wrote:

> Hi,
>
> My name is Uday Kale. Username: *uday*. I want to add support for Node
> discovery through AWS Application ELB Target Group.
>
> Best Regards,
> Uday
>

Re: Request to contribute

[Denis Magda]

Hi Ray,

You're in.

--
Denis

On Fri, May 18, 2018 at 8:31 AM, Ray  wrote:

> Hello Alexey,
>
> My jira id is ldz, sorry for the confusion.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Baseline topology documentation clarified: usage scenarios and definition

[Denis Magda]

Ivan,

Do you have any diagrams for the baseline topology? I do know you gave some
talks on it, so there should be something.

--
Denis

On Fri, May 18, 2018 at 5:20 AM, Dmitriy Setrakyan 
wrote:

> Great docs! Any chance we could add some pictures to illustrate the concept
> better.
>
> On Fri, May 18, 2018 at 2:15 AM, Denis Magda  wrote:
>
> > Igniters,
> >
> > With the help of Stanislav Lukyanov and Ivan Rakov, we could make our
> > baseline topology documentation much better and vivid. Check up the new
> > sections that did a better job explaining the topology, cover common
> usage
> > scenarious and explain how to trigger the rebalancing programmatically if
> > it's not expected that the baseline topology's node count to be recovered
> > soon:
> >
> >- https://apacheignite.readme.io/v2.4/docs/cluster-
> >activation#section-baseline-topology
> > activation#section-baseline-topology>
> >- https://apacheignite.readme.io/v2.4/docs/cluster-
> >activation#section-usage-scenarios
> > activation#section-usage-scenarios>
> >- https://apacheignite.readme.io/v2.4/docs/cluster-
> >activation#section-triggering-rebalancing-programmatically
> > activation#section-triggering-rebalancing-programmatically>
> >
> > --
> > Denis
> >
>

Re: TeamCity permissions

[Denis Magda]

Hi Pavel,

All the accounts are assigned Project developer role on TC that should
provide anything you need to manage builds there.

What specifically are you looking for? Please elaborate so that Vitaly can
grant more permissions.

Vitaly, please keep an eye on the conversation.

--
Denis


On Fri, May 18, 2018 at 9:44 AM, Pavel Petroshenko 
wrote:

> Hi,
>
> Can anyone please grant TC permissions to manage jobs (reorder, etc) to:
>
> ekaterina.vergizova
> alexey.kosenchuk
> pavel.petroshenko
>
> Thanks!
> p.
>

[GitHub] ignite pull request #3672: IGNITE-6113 Backport to 2.4.4

[Jokser]

Github user Jokser closed the pull request at:

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


---

[GitHub] ignite pull request #3791: IGNITE-8116 Historical rebalance fixes

[Jokser]

Github user Jokser closed the pull request at:

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


---

[GitHub] ignite pull request #4019: IGNITE-8405 Backport to 2.4

[Jokser]

Github user Jokser closed the pull request at:

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


---

TeamCity permissions

[Pavel Petroshenko]

Hi,

Can anyone please grant TC permissions to manage jobs (reorder, etc) to:

ekaterina.vergizova
alexey.kosenchuk
pavel.petroshenko

Thanks!
p.

[GitHub] ignite pull request #3767: IGNITE-8085

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4026: IGNITE-8531 Fixed NPE if checkpoint has no pages ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Request for contributors permissions

[uday kale]

Hi,

My name is Uday Kale. Username: *uday*. I want to add support for Node
discovery through AWS Application ELB Target Group.

Best Regards,
Uday

[GitHub] ignite pull request #4027: IGNITE-605: remove todo as no needs

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Request to contribute

[Ray]

Hello Alexey,

My jira id is ldz, sorry for the confusion.





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

[GitHub] ignite pull request #4025: IGNITE-8528: Example fixed

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4027: IGNITE-605: remove todo as no needs

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

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

IGNITE-605: remove todo as no needs



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

$ git pull https://github.com/Mmuzaf/ignite ignite-605

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

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


commit 2de80dd4c8d33653be29c847243caf33dbbf767f
Author: Maxim Muzafarov 
Date:   2018-05-18T14:06:11Z

IGNITE-605: remove todo as no needs




---

[GitHub] ignite pull request #4010: IGNITE-8491

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4026: IGNITE-8531 Fixed NPE if checkpoint has no pages ...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-8531 Fixed NPE if checkpoint has no pages to write, but has 
partitions to destroy



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

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

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

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


commit b42b933b62b7f79dfb8355b1e6e4254dcb9e2842
Author: Pavel Kovalenko 
Date:   2018-05-18T13:43:20Z

IGNITE-8531 Fixed NPE if checkpoint has no pages to write, but has 
partitions to destroy.




---

[GitHub] ignite pull request #3996: IGNITE-8381 testNodeSingletonDeploy in Basic 2 ha...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4025: IGNITE-8528: Example fixed

[nizhikov]

GitHub user nizhikov opened a pull request:

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

IGNITE-8528: Example fixed



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

$ git pull https://github.com/nizhikov/ignite IGNITE-8528

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

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


commit 2d3f5f66650f4f3e3a8af2ee013b8e0958209fb1
Author: Nikolay Izhikov 
Date:   2018-05-18T12:27:10Z

IGNITE-8528: Example fixed

commit c620b76efc45db6231ffaf2911e1b60d6909c5fe
Author: Nikolay Izhikov 
Date:   2018-05-18T12:27:39Z

IGNITE-8528: Example fixed




---

[GitHub] ignite pull request #4024: IGNITE-7818

[1vanan]

GitHub user 1vanan opened a pull request:

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

IGNITE-7818



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

$ git pull https://github.com/1vanan/ignite IGNITE-7818

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

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


commit bd5fce8c99477abaabe5d3242d5a95c5b7988920
Author: Fedotov 
Date:   2018-05-08T09:21:05Z

change javaDoc in IgniteDataStreamer

commit 833a468aa5a05c478bf1231f313692d496f879c1
Author: Fedotov 
Date:   2018-05-18T12:18:24Z

remove assertion




---

Re: Baseline topology documentation clarified: usage scenarios and definition

[Dmitriy Setrakyan]

Great docs! Any chance we could add some pictures to illustrate the concept
better.

On Fri, May 18, 2018 at 2:15 AM, Denis Magda  wrote:

> Igniters,
>
> With the help of Stanislav Lukyanov and Ivan Rakov, we could make our
> baseline topology documentation much better and vivid. Check up the new
> sections that did a better job explaining the topology, cover common usage
> scenarious and explain how to trigger the rebalancing programmatically if
> it's not expected that the baseline topology's node count to be recovered
> soon:
>
>- https://apacheignite.readme.io/v2.4/docs/cluster-
>activation#section-baseline-topology
>
> 
>- https://apacheignite.readme.io/v2.4/docs/cluster-
>activation#section-usage-scenarios
>
> 
>- https://apacheignite.readme.io/v2.4/docs/cluster-
>activation#section-triggering-rebalancing-programmatically
>
> 
>
> --
> Denis
>

[GitHub] ignite pull request #4023: IGNITE-5990

[voipp]

GitHub user voipp opened a pull request:

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

IGNITE-5990



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

$ git pull https://github.com/voipp/ignite IGNITE-5990

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

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


commit d8896a9d7548a1f9c3ca1228629d7e1790e68303
Author: voipp 
Date:   2018-05-18T12:10:24Z

IGNITE-5990




---

Re: Request to contribute

[Alexey Goncharuk]

Hello Ray,

I was not able to find your ID in apache Jira, can you please double-check?

--AG

2018-05-18 9:06 GMT+03:00 Ray :

> Hello Ignite community,
>
> I'd like to do an enhancement on Ignite, my JIRA id is ldzhjn.
> Please grant permissions.
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-8531) NPE is thrown on destroying empty partition

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8531:
---

 Summary: NPE is thrown on destroying empty partition
 Key: IGNITE-8531
 URL: https://issues.apache.org/jira/browse/IGNITE-8531
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Sergey Chugunov
Assignee: Pavel Kovalenko


Improvement IGNITE-8320 introduced situation when NPE may happen: in case of 
destroying empty partition checkpoint record isn't logged to WAL but code 
attempts to create checkpoint marker anyway which leads to NPE.

We need to allow checkpointing empty partitions.



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

[jira] [Created] (IGNITE-8530) Exchange hangs during start/restart stress test

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-8530:
-

 Summary: Exchange hangs during start/restart stress test
 Key: IGNITE-8530
 URL: https://issues.apache.org/jira/browse/IGNITE-8530
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.4
Reporter: Mikhail Cherkasov
 Attachments: LocalRunner.java, Main2.java

Please see attached test, it starts N_CORES*2+2 nodes first and after this 
starts N_CORES*2 threads with while(true) cycle in which closes and starts 
nodes with small random pause.

After couple minutes it hangs with Failed to wait for partition map exchange.

 



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

[jira] [Created] (IGNITE-8529) Implement testing framework for checking delta records consistency

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-8529:
--

 Summary: Implement testing framework for checking delta records 
consistency
 Key: IGNITE-8529
 URL: https://issues.apache.org/jira/browse/IGNITE-8529
 Project: Ignite
  Issue Type: New Feature
  Components: persistence
Reporter: Ivan Rakov


We use sharp checkpointing of page memory in persistent mode. That implies that 
we write two types of record to write-ahead log: logical (e.g. data records) 
and phyisical (page snapshots + binary delta records). Physical records are 
applied only when node crashes/stops during ongoing checkpoint. We have the 
following invariant: checkpoint #(n-1) + all physical records = checkpoint #n.
If correctness of physical records is broken, Ignite node may recover with 
incorrect page memory state, which in turn can bring unexpected delayed errors. 
However, consistency of physical records is poorly tested: only small part of 
our autotests perform node restarts, and even less part of them performs node 
stop when ongoing checkpoint is running.
We should implement abstract test that:
1. Enforces checkpoint, freezes memory state at the moment of checkpoint.
2. Performs necessary test load.
3. Enforces checkpoint again, replays WAL and checks that page store at the 
moment of previous checkpoint with all applied physical records exactly equals 
to current checkpoint state.
Except for checking correctness, test framework should do the following:
1. Gather statistics (like histogram) for types of wriiten physical records. 
That will help us to know what types of physical records are covered by test.
2. Visualize expected and actual page state (with all applied physical records) 
if incorrect page state is detected.
Regarding implementation, I suppose we can use checkpoint listener mechanism to 
freeze page memory state at the moment of checkpoint.



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

[GitHub] ignite pull request #4022: IGNITE-8476 added covering test

[glukos]

GitHub user glukos opened a pull request:

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

IGNITE-8476 added covering test



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

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

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

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


commit a70cfc938de4433aa8dbf488d9d87c37dd7a4f55
Author: Ivan Rakov 
Date:   2018-05-18T09:47:28Z

IGNITE-8476 added covering test




---

[jira] [Created] (IGNITE-8528) Peer deployment does not work for continuous query transformers

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8528:


 Summary: Peer deployment does not work for continuous query 
transformers
 Key: IGNITE-8528
 URL: https://issues.apache.org/jira/browse/IGNITE-8528
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk






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

[jira] [Created] (IGNITE-8527) Show actual rebalance starting in logs

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-8527:
---

 Summary: Show actual rebalance starting in logs
 Key: IGNITE-8527
 URL: https://issues.apache.org/jira/browse/IGNITE-8527
 Project: Ignite
  Issue Type: Improvement
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko


We should increase level of logging from DEBUG to INFO for message:

{noformat}
if (log.isDebugEnabled())
log.debug("Requested rebalancing [from node=" + 
node.id() + ", listener index=" + topicId + " " + demandMsg.rebalanceId() + ", 
partitions count=" + stripePartitions.get(topicId).size() + " (" + 
stripePartitions.get(topicId).partitionsList() + ")]");

{noformat}

to have actual rebalancing start time.



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

[GitHub] ignite pull request #4021: IGNITE-6010

[NSAmelchev]

GitHub user NSAmelchev opened a pull request:

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

IGNITE-6010



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

$ git pull https://github.com/NSAmelchev/ignite ignite-6010

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

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


commit 2944e81ebe8199737a77ec233b71b30a66eb0219
Author: NSAmelchev 
Date:   2018-05-17T14:14:34Z

Fix test




---

[jira] [Created] (IGNITE-8526) Create web-agent docker image for k8s deployment

[Roman Guseinov (JIRA)]

Roman Guseinov created IGNITE-8526:
--

 Summary: Create web-agent docker image for k8s deployment
 Key: IGNITE-8526
 URL: https://issues.apache.org/jira/browse/IGNITE-8526
 Project: Ignite
  Issue Type: Improvement
  Components: UI
Reporter: Roman Guseinov
Assignee: Peter Ivanov
 Attachments: Dockerfile

Currently, apacheignite/web-console-standalone is not enough to run web-console 
in Kubernetes environment. The only way to connect a cluster from web console 
is to use web-agent. That's why we need a docker image which we can configure 
(grid and console addresses, security tokens) and run on k8s env.

Dockerfile example is attached.



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

[GitHub] ignite pull request #3982: IGNITE-8464 removed file format after archive

[asfgit]

Github user asfgit closed the pull request at:

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


---

Request to contribute

[Ray]

Hello Ignite community,

I'd like to do an enhancement on Ignite, my JIRA id is ldzhjn.
Please grant permissions.

Thanks



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