Semen Boikov created IGNITE-1393:
Summary: AssertionError when stop node executing transaction
Key: IGNITE-1393
URL: https://issues.apache.org/jira/browse/IGNITE-1393
Project: Ignite
Issue Ty
Vladimir Ozerov created IGNITE-1392:
---
Summary: IGFS example configuration must have IPC endpoint enabled
by default.
Key: IGNITE-1392
URL: https://issues.apache.org/jira/browse/IGNITE-1392
Project:
Guys,
I want to drop it on the list and see what are the thoughts the PMC. I think
it would be very beneficial for the members of this community if we institute
a policy to have regular rotations of the Chair. We do this in Bigtop and it
works real well for a couple of reasons:
- it provides an o
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/69
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Thank you everyone.
@Murthy, Sure we can discuss and share.
Excellent Sergi.
I think, Jira issue tickets are the best way to get started. We can take an
issue and start with top down approach to understand the codebase and fix
the issue.
On Tue, Sep 8, 2015 at 5:46 PM, Raul Kripalani wrote:
>
On Tue, Sep 8, 2015 at 5:08 AM, Alexey Kuznetsov
wrote:
> And login form has 3 states: login, register and forgot password, it looks
> better as modal and not as usual page
>
I would leave it as is for now. I think we are walking into the "personal
taste" maze which could drag on forever, especi
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/76
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/77
IgniteCacheSslStartStopSelfTest Experiments (tmp PR 2)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incubator-ignite
IgniteCacheS
On Tue, Sep 8, 2015 at 8:07 AM, Andrey Kornev
wrote:
> Dmitriy,
>
> In case of topology changes, I'd prefer the services to stay on the same
> node they are currently on, as long as possible. In general, my goal is to
> keep the related singleton services together, and minimize their movements
>
Dmitriy,
In case of topology changes, I'd prefer the services to stay on the same node
they are currently on, as long as possible. In general, my goal is to keep the
related singleton services together, and minimize their movements between the
nodes. But if they have to move, they move as a gro
Alexey,
At the moment we limited by data format provided by Ignite Yardstick
framework.
On Tue, Sep 8, 2015 at 5:02 PM, Alexey Kuznetsov
wrote:
> Ilya,
>
> How about to google for how other projects do it and take useful ideas from
> them?
> For example: http://www.planetcassandra.org/nosql-per
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/76
IGNITE-1383 Ability to use apply-pull-request.sh script for non-master
branches
https://issues.apache.org/jira/browse/IGNITE-1383
You can merge this pull request into a Git repository by running:
Pavel Tupitsyn created IGNITE-1391:
---
Summary: Platform .Net: Messaging.RemoteListen causes deadlock
when remote node interop is initializing
Key: IGNITE-1391
URL: https://issues.apache.org/jira/browse/IGNITE-13
Dmitriy,
Good usability point, thanks.
Tomorrow I will add reminder for security token on pop that offer to
download the "ignite-web-agent" zip.
On Tue, Sep 8, 2015 at 9:01 PM, Dmitriy Setrakyan
wrote:
> Alexey,
>
> It sounds like a good improvement.
>
> You should also provide a way to view t
Alexey,
It sounds like a good improvement.
You should also provide a way to view the token on the "Load from Database"
or SQL pop up windows that offer to download the "ignite-web-agent" zip
file. Perhaps something like this:
* You will need your security token to access Ignite web console.
* To
Ilya,
How about to google for how other projects do it and take useful ideas from
them?
For example: http://www.planetcassandra.org/nosql-performance-benchmarks
On Tue, Sep 8, 2015 at 8:46 PM, Ilya Suntsov wrote:
> Hi Igniters,
> I plan to create 'Testing and benchmarking' page on Wiki in order
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
Excellent writeup, Sergi.
May I also add that apart from examples, it also helps to look at the unit
tests for the parts of the system you are trying to grasp or focus on (with
debugging enabled to walk through the code).
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise
That helps a lot. Thanks much for the information.
Murthy.
On Sep 8, 2015 7:59 AM, "Sergi Vladykin" wrote:
> Guys,
>
> The approach I'll suggest you will be quite common for fairly any code base
> you will work on.
>
> 1. Get familiar with current features, usage scenarios and respective
> publi
And login form has 3 states: login, register and forgot password, it looks
better as modal and not as usual page
On Tue, Sep 8, 2015 at 7:07 PM, Alexey Kuznetsov
wrote:
> We force user to click "Configure now" because I want to show landing page.
> This page will be reworked in a couple of days
We force user to click "Configure now" because I want to show landing page.
This page will be reworked in a couple of days and will describe Web
Control Center main features.
On Tue, Sep 8, 2015 at 3:28 PM, Vladimir Ozerov
wrote:
> "login force" => "login form".
>
> On Tue, Sep 8, 2015 at 11:28
Guys,
The approach I'll suggest you will be quite common for fairly any code base
you will work on.
1. Get familiar with current features, usage scenarios and respective
public APIs of the product.
You can look at http://ignite.apache.org/features.html and
http://ignite.apache.org/usecases.html
Semen Boikov created IGNITE-1390:
Summary: Use custom classes in failover tests instead of
strings/primitives
Key: IGNITE-1390
URL: https://issues.apache.org/jira/browse/IGNITE-1390
Project: Ignite
Absolutely, that makes sense. As a newbie, I am trying to understand where
I should start from to understand the framework. Probably anyone in here
can share that perspective, to get a handle of the different classes and
their purpose.
Thanks,
Murthy.
On Tue, Sep 8, 2015 at 7:18 AM, chandresh pan
Murthy/Sudhanshu,
IMO Please use ignite dev list for further discussion or communication your
discussion might help new contributors to early ramp up.
Thanks
On Tue, Sep 8, 2015 at 4:37 PM, Murthy Kakarlamudi wrote:
> Hello Sudhanshu,
> My name is Murthy. I also joined Ignite Dev group rece
>
> I am confused. Are we saying that we work with 2.7.0, but not 2.6.0? I this
> case I am OK disabling the Yarn module during the build. Nick, can you
> confirm?
>
Yes. Sergey Kozlov in first message describe how disable Yarn module during
the build.
Hello Sudhanshu,
My name is Murthy. I also joined Ignite Dev group recently and am
trying to understand it. Probably we can share our understandings before we
can contribute to issues. My id is ksa...@gmail.com. Please share your id
too.
Thanks,
Murthy.
On Mon, Sep 7, 2015 at 5:06 AM, Sudhans
Denis Magda created IGNITE-1389:
---
Summary: GridCacheAbstractFullApiSelfTest.testWithSkipStore fails
periodically on different configuration
Key: IGNITE-1389
URL: https://issues.apache.org/jira/browse/IGNITE-1389
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/75
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/75
IGNITE-1388 Platform .Net: cache.Invoke result in async mode should have an
error flag
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupits
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/74
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Pavel Tupitsyn created IGNITE-1388:
---
Summary: Platform .Net: cache.Invoke result in async mode should
have an error flag
Key: IGNITE-1388
URL: https://issues.apache.org/jira/browse/IGNITE-1388
Proj
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/74
IGNITE-1387 Platform .Net: cache.Invoke does not work with portable objects
without Java counterpart
You can merge this pull request into a Git repository by running:
$ git pull https://gith
Pavel Tupitsyn created IGNITE-1387:
---
Summary: Platform .Net: cache.Invoke does not work with portable
objects without Java counterpart
Key: IGNITE-1387
URL: https://issues.apache.org/jira/browse/IGNITE-1387
Denis Magda created IGNITE-1386:
---
Summary: IPC semaphores are not released on server endpoint abrupt
stop
Key: IGNITE-1386
URL: https://issues.apache.org/jira/browse/IGNITE-1386
Project: Ignite
Usability concern - why do we force user doing click on "Configure now"?
IMHO it is better to inline login force directly on the page.
On Tue, Sep 8, 2015 at 11:12 AM, Alexey Kuznetsov
wrote:
> My question is about this feature name: "Ignite Web Console" or "Ignite Web
> Control Center"?
>
> On
"login force" => "login form".
On Tue, Sep 8, 2015 at 11:28 AM, Vladimir Ozerov
wrote:
> Usability concern - why do we force user doing click on "Configure now"?
> IMHO it is better to inline login force directly on the page.
>
> On Tue, Sep 8, 2015 at 11:12 AM, Alexey Kuznetsov > wrote:
>
>> M
Hi, All,
I reworked Ignite Web Agent to use access token instead of account password.
Ignite Web Agent README.txt updated, new ZIP with updated Web Agent
uploaded to http://104.197.2.239/
Changes pushed to ignite-843 branch.
There were 2 reasons to do it:
1) Security. One could configure Web A
My question is about this feature name: "Ignite Web Console" or "Ignite Web
Control Center"?
On Tue, Sep 8, 2015 at 2:02 PM, Dmitriy Setrakyan
wrote:
> Igniters,
>
> Looks like the web console feature is becoming production ready:
> http://104.197.2.239/
>
> In my opinion, the ability to configu
Igniters,
Looks like the web console feature is becoming production ready:
http://104.197.2.239/
In my opinion, the ability to configure Ignite and run SQL queries on
Ignite clusters from a web console is a huge productivity boost and we
should try to get as many community members and users to st
40 matches
Mail list logo
