Ah, thanks for the great explanation. Any particular reason that the
job(s) you described should not be Samza jobs?
We're started experimenting with such jobs for Druid and Elasticsearch.
For Elasticsearch, the Samza job containers join the Elasticsearch cluster
as transport nodes and use the Jav
Nice. Thanks Yan!
On Tue, Mar 31, 2015 at 3:24 PM, Yan Fang wrote:
> Cool.
>
> * Published to maven, it's already there.
> * Uploaded to dist/release. It may take a while for mirrors to pick it up.
> * Updated the downloading page in
> https://issues.apache.org/jira/browse/SAMZA-624
> ** Will p
Chris -
Wulp, now I feel like a moron, but at least things are running now! Thanks
a lot for helping me diagnose that. On to the next problem...
Andrew Sannier
On 3/31/15, 4:21 PM, "Chris Riccomini" wrote:
>Hey Andrew,
>
>It looks like your attachment was stripped by Apache's mailing server
Hey Yan,
Based on this:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20INFRA%20AND%20component%20%3D%20Blogs
It looks like you'll need to open an INFRA ticket to get your blog account.
=)
Cheers,
Chris
On Tue, Mar 31, 2015 at 3:24 PM, Yan Fang wrote:
> Cool.
>
> * Published to m
Cool.
* Published to maven, it's already there.
* Uploaded to dist/release. It may take a while for mirrors to pick it up.
* Updated the downloading page in
https://issues.apache.org/jira/browse/SAMZA-624
** Will publish the website after mirrors pick up the 0.9.0 release
** In terms of the blog,
Hey Andrew,
It looks like your attachment was stripped by Apache's mailing server.
Looking at the info you pasted, I can tell you that YARN is most likely
unable to provision your containers due to space constraint. Here's the
issue:
Memory Used: 1 GB
Memory Total: 1.76 GB
The YARN AM and YARN c
Thanks so much for getting back to me, Chris.
I’ve attached the AM log from my most recent attempt to run the
hello-samza wikipedia-feed task. I’ve been using pretty small nodes to
keep costs down while I test and so forth, so that makes a lot of sense
(though I definitely hoped I’d configured app
Hey Andrew,
I'm wondering if your YARN cluster doesn't have enough memory to fit both
the AM and its containers. The fact that the AM UI shows no running
containers is suspicious. Can you check these four settings in your YARN
RM's UI:
Memory Used
Memory Total
Memory Reserved
VCores Used
Something to add here: there are a couple of weird things in the Samza
Application Master web UI: Application master task ID is -1, which seems
odd, and the Running Containers table is completely empty. How could YARN
call a task “Running” if there’s no container?
Thanks,
Andrew Sannier
On 3/
Hey Yan/Jakob,
Awesome, thanks! Yan, feel free to finish up the release. :) Very cool!
Cheers,
Chris
On Tue, Mar 31, 2015 at 1:27 PM, Jakob Homan wrote:
> Correct. All that's necessary for a release is a
> more-+1s-than--1s-from-PMC-members vote, and then we can go ahead with
> distribution,
Correct. All that's necessary for a release is a
more-+1s-than--1s-from-PMC-members vote, and then we can go ahead with
distribution, publicity, etc.
-jg
On 31 March 2015 at 12:44, Chris Riccomini wrote:
> Hey Yan,
>
> Let's confirm with Jakob. I *think* we don't need any intervention from
> Apa
Hi all -
Thanks in advance for your help; I have been totally stuck on this for a
couple of days.
I have a small YARN cluster with one ResourceManager and one NodeManager
as well as one Zookeeper node and one Kafka node - trying to keep the
number of moving parts to a minimum. I¹ve been following
Hey Yan,
Let's confirm with Jakob. I *think* we don't need any intervention from
Apache. We should be able to move forward with the release. @Jakob, can you
confirm this?
Cheers,
Chris
On Tue, Mar 31, 2015 at 11:17 AM, Yan Fang wrote:
> Hi all,
>
> After 72+ hours, we got +4 binding votes (Chr
Hi all,
After 72+ hours, we got +4 binding votes (Chris, Jakob, Chinmay, Yan) , +2
non-binding votes (Roger, Yi Pan). The release vote passes.
@Chris, Do we need the vote from apache general mailing list? Or I can go
ahead to update to release dist, update download page, publish 0.8.0
binaries to
Hi, Shekar,
For windowing and SQL-like features, please watch the following tickets:
SAMZA-552, SAMZA-561, SAMZA-562. As Chris said, we are still actively
design and develop those features in samza-sql branch, and will merge it
back to the master in a later point.
Cheers!
-Yi
On Tue, Mar 31, 20
Thanks for your reply Roger! Very insightful (:
> 6. If there was a highly-optimized and reliable way of ingesting
> partitioned streams quickly into your online serving system, would that
> help you leverage Samza more effectively?
>> 6. Can you elaborate please?
Sure. The feature set I have in
Hey Shekar,
The full list of 0.9.0 features and fixes is here:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20%3D%200.9.0%20AND%20status%20in%20(Resolved%2C%20Closed)
Re: SQL and windowing, most of that work has been done in isolation in the
samza-sql bran
Perfect Chris. We will test out the latest version. Did not get a chance to
test it.
On the same note, as I have not caught up with 0.9.0, is there anyway to
get the feature list or some release notes for 0.9.0. I am interested with
the windowing and SQL like capabilities.
- Shekar
On Tue, Mar 31
Hi Harlan and Vladimir,
I think the idea of serving data directly off of Samza has been mentioned a few
times, but there are certain caveats that make this a risky proposition. For
example:
* Samza does not have the same uptime constraints as a dedicated data
serving platform. While I'm a
Hey Jordi,
Thanks for this! I've copied your pastebin script, and put it on:
https://issues.apache.org/jira/browse/SAMZA-189
So that we don't lose track of it.
Cheers,
Chris
On Tue, Mar 31, 2015 at 3:48 AM, Jordi Blasi Uribarri
wrote:
> Hi,
>
> I am not sure what is the correct way of doin
Of say yes, is been a few days with little traffic on the topic.
On Mar 31, 2015 9:18 AM, "Chris Riccomini" wrote:
> Hey all,
>
> Is the vote done?
>
> Cheers,
> Chris
>
> On Mon, Mar 30, 2015 at 2:10 PM, Chris Riccomini
> wrote:
>
> > +1
> >
> > 1. Validated hello-samza works with 0.9.0 Maven b
Hi Felix,
1,3. We're experimenting with both Druid and Elasticsearch for this. We're
using Samza to enrich user activity and system performance events then
index them in Druid +/or Elasticsearch depending on the use case.
2. These are internal BI/Operations applications
4. We're still getting up
Hey Shekar,
Are you running with 0.8.0 when you run these tests? If so, there are some
known issues where a Samza consumer can get stuck when brokers disappeared.
All known issues have been resolved in the 0.9.0 release, but they exist in
the 0.8.0 release.
Cheers,
Chris
On Mon, Mar 30, 2015 at
Hey all,
Is the vote done?
Cheers,
Chris
On Mon, Mar 30, 2015 at 2:10 PM, Chris Riccomini
wrote:
> +1
>
> 1. Validated hello-samza works with 0.9.0 Maven binaries.
> 2. Validated release-0.9.0-rc0 tag exists and has correct checksums.
> 3. Validated source release tarball builds, and has corre
This question kinda goes back to the one asked by Felix : "How do you serve
the data computed by Samza". If you're interested in that approach (which
involves exporting your state to some external serving layer) then you
should probably engage on that thread.
The approach you mentions is also in a
Hey,
I have samza job with a number of tasks, each of which holds some state
in its embedded store. I want to expose this store for reading to
outside world via some kind of RPC mechanism. What could be the best
solution for this?
The only solution which comes to my mind is to make my tasks,
Hi,
I am not sure what is the correct way of doing this (I am sure this is not it,
but anyway…). Following your advice I was able to get working Samza and now I
am trying to explore it’s full capabilities. As promised, the notes, quick
installation guide, I was writing in the process is in the
27 matches
Mail list logo
