Tumgik
#expectedend
kitajovan · 4 years
Photo
Tumblr media
#anotherblessedday #togodbetheglory #faith #hope #future #expectedend https://www.instagram.com/p/CJtZ7IEB_3v/?igshid=1wjf4zfd4oi1x
0 notes
disenoswag · 4 years
Photo
Tumblr media
About right here should do. Can U see it? #expectedend #hopeful #gift #gifts #blessings #goodandperfect #equipped (at Portsmouth, Virginia) https://www.instagram.com/p/CDY1zZOBxN1/?igshid=1dir5z1nhf4ny
0 notes
fashionedforhem · 7 years
Photo
Tumblr media
What he has for you is SO much greater, bigger, and better than what you could hope for yourself. He just wants the BEST for you and me! Jeremiah 29:11 (NLT) says “For I know the plans I have for you,” says the LORD. “They are plans for good and not for disaster, to give you a future and a hope." #throwbackthursday #expectedend #futurehope #Inspirational #hisplans #Encouragement #inspire #writersofinstagram #jeremiah2911 #blogger #shishandrawrites #shishandrad #writer #poetry #poet #inspiration #goodevening
3 notes · View notes
its-blush-blog · 5 years
Quote
This is what I know: That everything is going to be okay because God is the prophet of my life, and he never lies.
Tashie Ferguson
0 notes
desirants · 7 years
Photo
Tumblr media
#ORungreza - after 31 tumultuous weeks this #humtv serial ended with Sassi leaving her old self behind and opening a new chapter in her life. . . What did you all think of this ending? Do you agree with the broader implications of this story? Are you satisfied with this new direction of Sassi’s life? . . Penned by #SajiGul directed by #KashifNisar this serial featured brilliant performances by #sajalaly #bilalabbaskhan #naumanijaz #irsaghazal #sanafakhar #omairrana #hamzafirdous #soniamishal and even when the story dragged these performances had us tuning in week after week. . . My detailed overview on the serial and the final episode is now up on the blog desirantsnraves.com ( direct link in bio). Do read and share your views — would be great to hear what you all thought! Looking forward to your views! . . #desirantsnraves #dramareview #desiblogger #socialcritique #misogyny #patriarchy #expectedend #notimpressed #weekendpost
0 notes
brandonacox · 4 years
Text
I favorited a tweet...
The power within you is greater than the problem in front of you.
— Katie Souza (@ExpectedEnd) July 9, 2020
from http://twitter.com/ExpectedEnd
0 notes
jumbojrp-blog · 7 years
Text
Oozie SLA Monitoring
Introduction
Oozie workflow and coordinators allow SLA for
The maximum allowed time limit associated with when the job should start
By when the job should end
Duration of Run
Oozie can monitor the above states of a SLA-sensitive job and can send notification for SLA met or misses.
*Before oozie-4.x, client needs to query oozie SLA api, gets the data and has to calculate whether SLA met or misses.
Now, oozie provides 3 ways to get SLA information
SLA tab in oozie UI
JMS messages sent to a configured JMS provider for instantaneous tracking
RESTful API to query for SLA summary
Here we will discuss about RESTful API. Let's know a bit more about SLA, before going to implementation
So, there are 3 criteria of oozie SLA
Start Time
End Time
Duration
Depending on criteria, there can be 2 kinds of status , Event Status and SLA Status
Event Status
Start Time - START_MET, START_MISS
End Time - END_MET, END_MISS
Duration - DURATION_MET, DURATION_MISS
SLA Status
Not_Started <-- Job not yet begun
In_Process <-- Job started and is running, and SLAs are being tracked
Met <-- caused by an END_MET
Miss <-- caused by an END_MISS
Basically, SLA Status depends on END_MET or END_MISS as expected end-time is the most important criterion for majority of users.
For example:
For event status: START_MISS, END_MET, DURATION_MET
SLA Status would be END_MET
Here is the input in job.properties file: nominalTime=2017-07-09T16:47Z shouldStart=1 shouldEnd=5
Here is the response for such scenario and input
{ "slaSummaryList": [{ "nominalTime": 1499618820000, //GMT: Sunday, July 9, 2017 4:47:00 PM "jobStatus": "SUCCEEDED", "expectedEnd": 1499619120000, //GMT: Sunday, July 9, 2017 4:52:00 PM "appName": "simplejob", "actualEnd": 1499619043130, //GMT: Sunday, July 9, 2017 4:50:43.130 PM "actualDuration": 392, "expectedStart": 1499618880000, //GMT: Sunday, July 9, 2017 4:48:00 PM "expectedDuration": 240000, //4 min "durationDelay": -3, "slaStatus": "MET", "appType": "WORKFLOW_JOB", "slaAlertStatus": "Enabled", "eventStatus": "END_MET,DURATION_MET,START_MISS", "startDelay": 2, "id": "0000010-170708204706283-oozie-huse-W", "lastModified": 1499619052621, "user": "jrp", "actualStart": 1499619042738, //GMT: Sunday, July 9, 2017 4:50:42.738 PM "endDelay": -1 }] }
Also, when job doesn't end successfully i.e Failed/Error/Killed/Timeout, then also SLA Status would be Miss
Now you understood, when there will be SLA Met or Miss. To get this calculated SLA Status or to get notified in case of both SLA Met and Miss, we need to configure.
You can use JMS complient broker such as Apache ActiveMQ to send/receive messages. For more details, please check here https://oozie.apache.org/docs/4.1.0/AG_Install.html#Notifications_Configuration
Important
To utilize the service, you need to modify oozie-site.xml like below and restart oozie server
<property> <name>oozie.services.ext</name> <value> org.apache.oozie.service.EventHandlerService, org.apache.oozie.sla.service.SLAService </value> </property> <property> <name>oozie.service.EventHandlerService.event.listeners</name> <value> org.apache.oozie.sla.listener.SLAJobEventListener </value> </property>
*SLAJobEventListener - Processes job events and calculates SLA. Does not send any notifications (As I am targetting only getting calculated SLA, not notification)
Configuring SLA in application
To make your job SLA-sensitive job, you need to add sla tag in your workflow.xml.
for workflow schema before than "uri:oozie:workflow:0.5" ===> SLA schema version would be 0.1 i.e. xmlns:sla="uri:oozie:sla:0.1"
for new workflow schema i.e. xmlns="uri:oozie:workflow:0.5" ===> SLA schema version would be 0.2 i.e. xmlns:sla="uri:oozie:sla:0.2"
If you are using workflow version < 0.5 and sla schema version 0.2, you will get below error
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid content was found starting with element 'sla:info'. One of '{WC["uri:oozie:sla:0.1"]}' is expected.
So, in order to use new SLA schema, you will need to upgrade your workflow/coordinator schema to 0.5 i.e. 'uri:oozie:workflow:0.5'
To check schema for SLA 0.1 and 0.2, Please check here https://oozie.apache.org/docs/4.1.0/WorkflowFunctionalSpec.html#SLASchema
Sample Oozie Workflow.xml
<workflow-app xmlns="uri:oozie:workflow:0.4" xmlns:sla="uri:oozie:sla:0.1" name="simplejob"> <start to="hdfscommands"/> <action name="hdfscommands"> <fs> <delete path='${nameNode}/user/huser/oozie-simple/simplejob-dir'/> <mkdir path='${nameNode}/user/huser/oozie-simple/simplejob-dir'/> </fs> <ok to="end"/> <error to="fail"/> </action> <kill name="fail"> <message>Workflow failed, error message[${wf:errorMessage(wf:lastErrorNode())}] </message> </kill> <end name="end"/> <sla:info> <!-- sla 0.2 --> <!-- <sla:nominal-time>${nominalTime}</sla:nominal-time> <sla:should-start>${shouldStart}</sla:should-start> <sla:should-end>${shouldEnd}</sla:should-end> <sla:max-duration>5</sla:max-duration> <sla:alert-events>start_miss,end_miss,duration_miss</sla:alert-events> <sla:alert-contact>${alertContact}</sla:alert-contact> <sla:notification-msg>${notificationMsg}</sla:notification-msg> --> <!-- sla 0.1 --> <sla:app-name>simplejob</sla:app-name> <sla:nominal-time>${nominalTime}</sla:nominal-time> <sla:should-start>${shouldStart}</sla:should-start> <sla:should-end>${shouldEnd}</sla:should-end> <sla:notification-msg>${notificationMsg}</sla:notification-msg> <sla:alert-contact>${alertContact}</sla:alert-contact> <sla:dev-contact>${devContact}</sla:dev-contact> <sla:qa-contact>${qaContact}</sla:qa-contact> <sla:se-contact>${seContact}</sla:se-contact> </sla:info> </workflow-app>
Sample job.properties
nameNode=hdfs://localhost:9000 jobTracker=localhost:8032 master=local[*] queueName=default oozie.use.system.libpath=true oozie.wf.application.path=${nameNode}/user/${user.name}/simplejob/ nominalTime=2017-07-09T17:36Z shouldStart=1 shouldEnd=5 notificationMsg=Notification for SLA [email protected] [email protected] [email protected] [email protected]
Important Tags
nominal-time: As the name suggests, this is the time relative to which your jobs' SLAs will be calculated.
should-start: Relative to nominal-time this is the amount of time (along with time-unit - MINUTES, HOURS, DAYS) within which your job should start running to meet SLA. This is optional.
should-end: Relative to nominal-time this is the amount of time (along with time-unit - MINUTES, HOURS, DAYS) within which your job should finish to meet SLA.
max-duration: This is the maximum amount of time (along with time-unit - MINUTES, HOURS, DAYS) your job is expected to run. This is optional.
alert-events: Specify the types of events for which Email alerts should be sent. Allowable values in this comma-separated list are start_miss, end_miss and duration_miss. *_met events can generally be deemed low priority and hence email alerting for these is not neccessary. However, note that this setting is only for alerts via email alerts and not via JMS messages, where all events send out notifications, and user can filter them using desired selectors. This is optional and only applicable when alert-contact is configured.
alert-contact: Specify a comma separated list of email addresses where you wish your alerts to be sent. This is optional and need not be configured if you just want to view your job SLA history in the UI and do not want to receive email alerts.
Accessing SLA Information
As I mentioned at the beginning, here we are discussing only accessing via RESTful API to query for SLA summary.
The Oozie Web Services API is a HTTP REST JSON API. All responses are in UTF-8 .There are two ways of accessing RESTful API of oozie
Command Line tool
OozieClient
To get calculated SLA information. Command Line is deprecated and will not give expected result. It will only returns sla informations passed in workflow by using below command
oozie sla -filter jobid=<jobID>
The only way to get the calculated SLA information is by using OozieClient, but there is a twist.
The webservices endpoint for sla is /v2/sla
You need to extend OozieClient class and implement for V2 version. Here is the CustomOozieClient.java present in github
https://github.com/jrphub/mapreduce/blob/master/src/main/java/com/sample/hadoop/oozie/CustomOozieClient.java
To implement more functionalities, please refer the Apache OozieClient.java here
https://github.com/apache/oozie/blob/branch-4.1/client/src/main/java/org/apache/oozie/client/OozieClient.java
0 notes
writegigi · 9 years
Photo
Tumblr media
Follow your heart , everything may seem like it isn't going anywhere or that you're name isn't out there like you quiet imagined it to be but I'm here to encourage my family , friends, and associates to continue doing what you're doing and know that the finished product of your dream/goal is inevitable if you strive to achieve it . In all you do , acknowledge God and place Him first above all things . Amen . #EncourageSomeoneToday #WriteGigi #KeepDreaming #YouWillGetThere #ExpectedEnd
1 note · View note
disenoswag · 4 years
Photo
Tumblr media
I tried my way. That stuff hurt 🤕🤒😷🤢🤮🥵🥶😭😡🤬 #holyspirit #holyspiritpower #holyspiritcome #holyspiritfire #holyspiritfilled #equipped #led #guide #guided #expected #expectedgoals #expectedvsreality #expectedend #hope #destiny (at Portsmouth, Virginia) https://www.instagram.com/p/CDTuXeDDOKz/?igshid=170qbuenhn75f
0 notes
brandonacox · 4 years
Text
I favorited a tweet...
With everything that's happening in the world and with the access we have to the internet, it can be hard to quiet our mind and heart. Today, let's make some time to draw near to God, because in His presence there is rest. He promises, He will draw near to you! #drawneartoGod
— Katie Souza (@ExpectedEnd) May 12, 2020
from http://twitter.com/ExpectedEnd
0 notes
fashionedforhem · 7 years
Photo
Tumblr media
"Tie kindness around your neck as a reminder and store it in your heart." ❤️(Proverbs 3:3 NLT) Be Kind and allow it to exude from the love in your heart. For we don't know what others are facing yet, choose to be kind.S.D. #kind #showlove #inspiteof #bekind #shishandrawrites #shishandrad #inspirationalquotes #expectedend #Inspirational #hisplans #Encouragement #GodIsForYou #kindness #writersofinstagram #blogger #shishandrawrites #shishandrad #writer #poetry #poet #inspiration #kindness #goodnight
0 notes
fashionedforhem · 7 years
Photo
Tumblr media
Monday Inspiration: "You will keep in perfect peace all who trust in you, all whose thoughts are fixed on you!" Whatever it is trust that he is working everything out for your good and be at peace. #peaceful #trust #trustGod #foryourgood #everpresenthelp #shishandrad #shishandrawrites #goodfather #peace #mondaymotivation #mondayinspiration #writersofinstagram #thoughtsofgood #expectedend
0 notes
fashionedforhem · 7 years
Photo
Tumblr media
Tie kindness around your neck as a reminder and store it in your heart. (Proverbs 3:3 NLT) Be Kind and allow it to exude from the love in your heart. For we don't know what others are facing yet, choose to be kind. #kind #showlove #inspiteof #writersofinstagram #shishandrawrites #shishandrad #inspirationalquotes #expectedend #Inspirational #hisplans #Encouragement #GodIsForYou #writersofinstagram #blogger #shishandrawrites #shishandrad #writer #poetry #poet #inspiration #kindness #goodnight
0 notes
fashionedforhem · 7 years
Photo
Tumblr media
Just a friendly reminder don't rush it. It will all happen in God's timing. It's the best timing for you! "He has made everything beautiful in its time." Ecclesiastes 3:11a #patience #godstiming #godstimingisperfect #wait #waiting #perfect #perfecttime #perfecttiming #writersofinstagram #shishandrawrites #shishandrad #inspirationalquotes #expectedend #Inspirational #hisplans #Encouragement #GodIsForYou #writersofinstagram #blogger #shishandrawrites #shishandrad #writer #poetry #poet #inspiration #faith
0 notes
fashionedforhem · 7 years
Photo
Tumblr media
Listen it's Tuesday! Make sure your priorities are in order. Why? Because a very long time ago I use to care about what people would think! Thank God for Jesus because HE allowed me to see that it's not about what people think. The most important thoughts are his thoughts for me. His thoughts are good and not of evil, to give me a future and a hope. So I live to please him and be his servant! Life is SO much better when you are living for Christ and not man. #godapproved #ChristServant #HeIsConstant #HeNeverChanges #ExpectedEnd #jeremiah2911 #ChristPleaser #LoveHimIDo #speaklove #think #lovely #love #writersofinstagram #shishandrawrites #shishandrad #inspirationalquotes #loveothers #Inspirational #hislove #Encouragement #godislove #writersofinstagram #blogger #shishandrawrites #shishandrad #writer #poetry #poet #inspiration #faith #shepherd
0 notes