RE: unsubscribe

2016-12-08 Thread Chen, Yan I
I’m pretty sure I didn’t.

From: Nicholas Chammas [mailto:nicholas.cham...@gmail.com]
Sent: Thursday, December 08, 2016 10:56 AM
To: Chen, Yan I; Di Zhu
Cc: user @spark
Subject: Re: unsubscribe

Oh, hmm...

Did you perhaps subscribe with a different address than the one you're trying 
to unsubscribe from?

For example, you subscribed with 
myemail+sp...@gmail.com<mailto:myemail%2bsp...@gmail.com> but you send the 
unsubscribe email from myem...@gmail.com<mailto:myem...@gmail.com>
2016년 12월 8일 (목) 오전 10:35, Chen, Yan I 
<yani.c...@rbc.com<mailto:yani.c...@rbc.com>>님이 작성:
The reason I sent that email is because I did sent emails to 
user-unsubscr...@spark.apache.org<mailto:user-unsubscr...@spark.apache.org> and 
dev-unsubscr...@spark.apache.org<mailto:dev-unsubscr...@spark.apache.org> two 
months ago. But I can still receive a lot of emails every day. I even did that 
again before 10AM EST and got confirmation that I’m unsubscribed, but I still 
received this email.


From: Nicholas Chammas 
[mailto:nicholas.cham...@gmail.com<mailto:nicholas.cham...@gmail.com>]
Sent: Thursday, December 08, 2016 10:02 AM
To: Di Zhu
Cc: user @spark
Subject: Re: unsubscribe

Yes, sorry about that. I didn't think before responding to all those who asked 
to unsubscribe.

On Thu, Dec 8, 2016 at 10:00 AM Di Zhu 
<jason4zhu.bigd...@gmail.com<mailto:jason4zhu.bigd...@gmail.com>> wrote:
Could you send to individual privately without cc to all users every time?


On 8 Dec 2016, at 3:58 PM, Nicholas Chammas 
<nicholas.cham...@gmail.com<mailto:nicholas.cham...@gmail.com>> wrote:

To unsubscribe e-mail: 
user-unsubscr...@spark.apache.org<mailto:user-unsubscr...@spark.apache.org>

This is explained here: http://spark.apache.org/community.html#mailing-lists

On Thu, Dec 8, 2016 at 7:46 AM Ramon Rosa da Silva 
<ramon.si...@neogrid.com<mailto:ramon.si...@neogrid.com>> wrote:

This e-mail message, including any attachments, is for the sole use of the 
person to whom it has been sent and may contain information that is 
confidential or legally protected. If you are not the intended recipient or 
have received this message in error, you are not authorized to copy, 
distribute, or otherwise use it or its attachments. Please notify the sender 
immediately by return email and permanently delete this message and any 
attachments. NeoGrid makes no warranty that this email is error or virus free. 
NeoGrid Europe Limited is a company registered in the United Kingdom with the 
registration number 7717968. The registered office is 8-10 Upper Marlborough 
Road, St Albans AL1 3UR, Hertfordshire, UK. NeoGrid Netherlands B.V. is a 
company registered in the Netherlands with the registration number 3416.6499 
and registered office at Science Park 400, 1098 XH Amsterdam, NL. NeoGrid North 
America Limited is a company registered in the United States with the 
registration number 52-2242825. The registered office is 55 West Monroe Street, 
Suite 3590-60603, Chicago, IL, USA. NeoGrid Japan is located at New Otani 
Garden Court 7F, 4-1 Kioi-cho, Chiyoda-ku, Tokyo 102-0094, Japan. NeoGrid 
Software SA is a company registered in Brazil, with the registration number 
CNPJ: 03.553.145/0001-08 and located at Av. Santos Dumont, 935, 89.218-105, 
Joinville - SC – Brazil.

Esta mensagem pode conter informação confidencial ou privilegiada, sendo seu 
sigilo protegido por lei. Se você não for o destinatário ou a pessoa autorizada 
a receber esta mensagem, não pode usar, copiar ou divulgar as informações nela 
contidas ou tomar qualquer ação baseada nessas informações. Se você recebeu 
esta mensagem por engano, por favor, avise imediatamente ao remetente, 
respondendo o e-mail e em seguida apague-a. Agradecemos sua cooperação.


___

If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.
___
If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.  

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
d

Unsubscribe

2016-12-08 Thread Chen, Yan I


___
If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.  

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.


Unsubscribe

2016-12-08 Thread Chen, Yan I


___
If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.  

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.


RE: restarting of spark streaming

2016-06-15 Thread Chen, Yan I
Could anyone answer my question?

_
From: Chen, Yan I
Sent: 2016, June, 14 1:34 PM
To: 'user@spark.apache.org'
Subject: restarting of spark streaming


Hi,

I notice that in the process of restarting, spark streaming will try to 
recover/replay all the batches it missed. But in this process, will streams be 
checkpointed like the way they are checkpointed in the normal process?

Does anyone know?

Sometimes our cluster goes maintenance, and our streaming process is shutdown 
for e.g. 1 day and restarted. If replaying batches in this period of time 
without checkpointing, the RDD chain will be very big, and memory usage will 
keep going up until all missing batches are replayed.

[memory usage will keep going up until all missing batches are replayed]: this 
is what we observe now.

Thanks,
Yan Chen

___
If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.  

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.


restarting of spark streaming

2016-06-14 Thread Chen, Yan I
Hi,

I notice that in the process of restarting, spark streaming will try to 
recover/replay all the batches it missed. But in this process, will streams be 
checkpointed like the way they are checkpointed in the normal process?

Does anyone know?

Sometimes our cluster goes maintenance, and our streaming process is shutdown 
for e.g. 1 day and restarted. If replaying batches in this period of time 
without checkpointing, the RDD chain will be very big, and memory usage will 
keep going up until all missing batches are replayed.

[memory usage will keep going up until all missing batches are replayed]: this 
is what we observe now.

Thanks,
Yan Chen

___
If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.  

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.