Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3209
---
Hi Denis,
but should we treat current behavior as a bug that should be fixed asap or
currently we should treat it as a known limitation?
Because now, IgniteOOM means that the whole cluster should be restarted.
Thanks,
Mikhail.
On Thu, Dec 14, 2017 at 2:03 AM, Denis Magda wrote:
> Hello Mikhail
Mikhail,
Here is the first idea that came to my mind. Before a transaction is
committed (or an atomic update is applied), we have all entries being
written on hands. We can estimate the maximum amount of memory required for
this to happen and make a reservation (one AtomicLong CAS) for this memory
Alexey,
but what if we have memory to save data on the primary node, but backup
node does
not have enough memory for this.
Then it will fail on backup and we again need to revert transaction on
primary which
means that we need to allocate extra memory for freelist again.
Do you think this will be
Vladimir Ozerov created IGNITE-7200:
---
Summary: SQL: Improvde DML encapsulation
Key: IGNITE-7200
URL: https://issues.apache.org/jira/browse/IGNITE-7200
Project: Ignite
Issue Type: Task
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3225
IGNITE-7200
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7200
Alternatively you can review and apply these
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/3226
IGNITE-6341: Direct IO implemented for file page store
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6341-1
A
Vasiliy Sisko created IGNITE-7201:
-
Summary: Web console: Auto check on leave of basic page
Key: IGNITE-7201
URL: https://issues.apache.org/jira/browse/IGNITE-7201
Project: Ignite
Issue Type:
Hi Igniters,
As far as I know, we planned to get the project compilable/runnable on Java
9 and then switch to Java 8 language features. But some tickets like [1]
require Java 8 to be fixed. It seems we are to switch source level of the
project to 1.8 first.
Thoughts?
[1] https://issues.apache.or
+1
Can we switch to Java8 right now and then support Java9?
That's the easiest way I think.
On Thu, Dec 14, 2017 at 1:50 PM, Andrey Kuznetsov wrote:
> Hi Igniters,
>
> As far as I know, we planned to get the project compilable/runnable on Java
> 9 and then switch to Java 8 language features. But
+1
Agree, I think changes will be less difficult if we go through 7/8 ->
8 -> 8/9 than 7/8 -> 7/8/9 ( -> possible 7/8/9/10 huh?) -> 8/9.
2017-12-14 14:18 GMT+03:00 Anton Vinogradov :
> +1
> Can we switch to Java8 right now and then support Java9?
> That's the easiest way I think.
>
> On Thu, Dec 1
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/3227
IGNITE-7021
IgniteOOM is not propogated to client in case of implicit transaction
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/ap
I agree with Alex.
Mikhail, you will have to allocate this "safe buffer" during prepare step.
I would add to Alex idea that each thread allocates its own "safe buffer"
and internal threads do not release this buffer and only enlarge if
necessary. Of course, if buffers occasionally grows too large
Dmitriy Pavlov created IGNITE-7202:
--
Summary: Include Ignite Direct IO plugin to binary distribution
Key: IGNITE-7202
URL: https://issues.apache.org/jira/browse/IGNITE-7202
Project: Ignite
I
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/3225
---
+1 Java 8 has a lot of APIs, we sometimes need it to improve our
performance.
чт, 14 дек. 2017 г. в 15:16, Дмитрий Рябов :
> +1
> Agree, I think changes will be less difficult if we go through 7/8 ->
> 8 -> 8/9 than 7/8 -> 7/8/9 ( -> possible 7/8/9/10 huh?) -> 8/9.
>
> 2017-12-14 14:18 GMT+03:00
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3228
Ignite 2.3.2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.3.2
Alternatively you can review and apply the
Thank you, Denis.
I added two additional fields for serialization into CacheMetrics and
I was worried about compatibility with old version (for example, when
partial cluster upgrade is in progress). But since Ignite does not
provide such feature as rolling upgrades, I think this question can be
co
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/3229
IGNITE-7182: Checkpoint pages: optimize and parallel sorting, fast start
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3230
Ignite 7181 1.8
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7181-1
Alternatively you can review and ap
Anton Vinogradov created IGNITE-7203:
Summary: Java 8 by default
Key: IGNITE-7203
URL: https://issues.apache.org/jira/browse/IGNITE-7203
Project: Ignite
Issue Type: Improvement
Got task IGNITE-7209. Started work on switching to java-1.8.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Sorry, I meant IGNITE-7203.
> On 14 Dec 2017, at 17:26, vveider wrote:
>
> Got task IGNITE-7209. Started work on switching to java-1.8.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Correct :)
Url is https://issues.apache.org/jira/browse/IGNITE-7203
On Thu, Dec 14, 2017 at 5:28 PM, Petr Ivanov wrote:
> Sorry, I meant IGNITE-7203.
>
> > On 14 Dec 2017, at 17:26, vveider wrote:
> >
> > Got task IGNITE-7209. Started work on switching to java-1.8.
> >
> >
> >
> > --
> > Sent
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3231
ignite-5874: Store TTL expire times in B+ tree on per-partition basis.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3232
IGNITE-6731: Dropping unnecessary PerfCounter invocations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ign
Alexei Scherbakov created IGNITE-7204:
-
Summary: Unexpected behavior if passing null to binaryObject.field
method
Key: IGNITE-7204
URL: https://issues.apache.org/jira/browse/IGNITE-7204
Project: I
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3233
IGNITE-6625 JDBC thin: support SSL connection to Ignite node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
Yury Babak created IGNITE-7205:
--
Summary: DataSet API
Key: IGNITE-7205
URL: https://issues.apache.org/jira/browse/IGNITE-7205
Project: Ignite
Issue Type: New Feature
Components: ml
Val, Thank you.
I fixed issues and answered questions from comments.
Please, take a look.
2017-12-13 3:28 GMT+03:00 Valentin Kulichenko :
> Hi Nikolay,
>
> I reviewed the code and left several comments in the ticket [1]. Please
> take a look.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-
Dmitry Karachentsev created IGNITE-7206:
---
Summary: Nodes may ping each other on stop for a
failureDetectionTimeout period
Key: IGNITE-7206
URL: https://issues.apache.org/jira/browse/IGNITE-7206
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3234
IGNITE-7206 - Stop pings if current node is stopping.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7206
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3218
---
Hi Peter,
Not being an expert in Linux packing system, the overall description looks
clear to me.
A minor comment, is that all ‘apache-ignite-fabric’ occurrences have to be
renamed to ‘apache-ignite’. Ignite is presently called as an in-memory
computing platform (that is also a questionable n
Vladimir,
No it’s crystal clear, thanks.
If this approach works only for Ignite persistence based deployment, how will
we handle locking for pure in-memory and caching of 3rd party databases
scenarios? As I understand the tuples still will be stored in the page memory
while there won’t be any
Yury,
As a ML component maintainer, please join this conversation.
Now there are some hacks in our build system because of ML that was always JDK
8 dependent. What needs to be done to obliterate the hacks and simplify the ML
assembly? This should be done as a part of the activity initiated by P
Thanks, Petr! Sounds like something we should have done a long time ago.
On Wed, Dec 13, 2017 at 11:24 PM, Petr Ivanov wrote:
> Hi, all!
>
>
> I’d like to initiate a process if integrating with Docker Hub on official
> level - as other Apache projects currently integrated (httpd / tomcat /
> mav
Submitted Ignite profile to Stackshare a couple of days ago. Waiting for an
approval… Hope it will get through quickly.
—
Denis
> On Nov 15, 2017, at 5:20 PM, Denis Magda wrote:
>
> Interesting source. Will look into it in a couple of days.
>
> Thanks for sharing.
>
> —
> Denis
>
>> On Nov
Folks,
Since 2.0 we have introduced PartitionLossPolicy which blocks access to
cache if data loss occurred. This is an awesome feature, however it is not
very clear how to use it properly.
First of all, there is no documentation. Ticket already exists though and
hopefully it will be completed soo
Valentin Kulichenko created IGNITE-7207:
---
Summary: Exchange worker dies if index contains non existent field
Key: IGNITE-7207
URL: https://issues.apache.org/jira/browse/IGNITE-7207
Project: Ignit
Vasiliy Sisko created IGNITE-7208:
-
Summary: Web console: Failed example on notebook page.
Key: IGNITE-7208
URL: https://issues.apache.org/jira/browse/IGNITE-7208
Project: Ignite
Issue Type:
Vasiliy Sisko created IGNITE-7209:
-
Summary: Web console: Show error when grid is not available
Key: IGNITE-7209
URL: https://issues.apache.org/jira/browse/IGNITE-7209
Project: Ignite
Issue T
Hi Anton,
I doubt it was merge conflict. Couple of days ago 'Ignite Start Nodes'
suite succeeded 1 time after unrelated changes, and now it is failing again.
2017-12-12 16:25 GMT+03:00 Anton Vinogradov :
> Hi,
>
> Seems we have merge conflict.
>
> https://ci.ignite.apache.org/viewType.html?build
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3235
IGNITE-7190 Docker Hub official repository deployment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7190
Alter
Prepared pull request to apache/ignite [1] with changes to meet the Docker
Hub requirements (best practices and other stuff).
Looking forward to see it in master ASAP to continue my work and prepare PRs
to Docker Hub's repositories.
[1] https://github.com/apache/ignite/pull/3235
--
Sent from:
45 matches
Mail list logo
